repost: libg++ won't build on alphaev56-dec-osf4.0d

[Alexandre Oliva]

On Dec 23, 1998, Jeffrey A Law <law@hurl.cygnus.com> wrote:

>   In message < or3e6bnyme.fsf@araguaia.dcc.unicamp.br >you write:
>> On Dec 19, 1998, Jeffrey A Law <law@upchuck.cygnus.com> wrote:

>> The point is that libstdc++ is a library we build together with egcs.
>> Users of DU4 won't be able to create shared libraries with g++ (or
>> with gcc, explicitly linking libstdc++ and libgcc in): they'll get a
>> symbol redefinition error :-(

> And with your solution, they can build libraries that don't work.  That is
> not a step forward.

In what sense wouldn't they work?

Whenever egcs and libstdc++ are reinstalled, any application linked
against an older libstdc++ has to be relinked, because its exception
handling mechanisms may be incompatible with the ones in the newer
release.  Therefore, there's not much point in trying to save a copy
of the exception-handling symbols in the libstdc++, at least until the
eh mechanisms get stable.  But then, when it does, we'll have a
problem.

That's why I think controlled symbol exporting is the way to go.  Even
if H.J.'s patch won't do the right thing now, it might be fixed,
right?

-- 
Alexandre Oliva  http://www.dcc.unicamp.br/~oliva  aoliva@{acm.org}
oliva@{dcc.unicamp.br,gnu.org,egcs.cygnus.com,samba.org}
Universidade Estadual de Campinas, SP, Brasil