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

Alexandre Oliva oliva@dcc.unicamp.br
Wed Dec 16 01:40:00 GMT 1998


On Dec 15, 1998, Manfred Hollstein <manfred@s-direktnet.de> wrote:

> On nil, 14 December 1998, 11:45:38, oliva@dcc.unicamp.br wrote:

>> It clearly means there's something wrong with the way shared libraries 
>> are being built on DU, but I don't have the faintest idea on how to
>> fix it :-(

> Sorry, I must have missed your first posting.  Could you try to find
> out, which particular module in libstdc++.so is defining __throw?

No object from libstdc++/piclist is defining __throw directly.  The
problem appears to be that libstdc++.so is being linked with libgcc
and importing symbols from it, and then libg++ complains because it
tries to import the same symbol into the library, but then it finds it 
in libgcc.a and libstdc++.so :-(

-- 
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




More information about the Gcc-bugs mailing list