shared libstdc++ is broken on alphaev56-dec-osf4.0d

[Jeffrey A Law]

  In message < 3783a0b1.350010406@mailer.gwdg.de >you write:
  > On Tue, 06 Jul 1999 23:31:46 -0600, Jeffrey A Law <law@cygnus.com>
  > wrote:
  > 
  > >This is a long-standing known issue (the need to control which symbols are
  > >exported from libgcc).
  > 
  > If binutils would work on every platform, I'd propose using symbol
  > versioning like glibc2 does. That would a) bring us versioned symbols
  > (not quite so important because libgcc is static) but b) would allow
  > for easy hiding.
  > 
  > Or is it more of a question of what to hide then of how ?
You can't assume binutils works on every platform.  You can't even assume that
if binutils works that people will be using it.

Even if binutils works on every platform, not every system uses an object file
format which has these kinds of capabilities.

So, you have to actually test for the features you need during the configure
process and if they are present, then you can use versioning or whatever scheme
to avoid undesirable exporting of symbols from libgcc.

jeff