Vaugha Brewchuk <vaugha_brewchuk@xxxxxxxx> writes: > I just had a good look at both static libraries that were generated during the build process, libstdc++ and libsupc++. I found that libstdc++ has in it all the objects from libsupc++ with the exception of eh_aux_runtime.o and eh_personality.o. This explains why I get linker warnings with missing symbols __gxx_personality_sj0 and __cxa_call_unexpected. Can you please confirm that these objects need to be statically linked into libstdc++? I can then figure out why they have been omitted. Yes, those objects should be in the static libstdc++.a archive. They should also be in the static libsupc++.a archive. I don't know why they would be missing for you. Ian > > I apologize about all these basic questions, but I tried really hard to find some low level detailed information about how gcc, g++ and libstdc++ are configured and built and I was not very successful. I am obviously very inexperienced with this... > > Thank you > > On 2012-03-20, at 5:15 PM, Vaugha Brewchuk wrote: > >> Thank you very much for your suggestion sir - this gives me exactly what I need in terms of troubleshooting direction! >> >> >> On 2012-03-20, at 4:30 PM, Ian Lance Taylor wrote: >> >>> Vaugha Brewchuk <vaugha_brewchuk@xxxxxxxx> writes: >>> >>>> This would definitely suffice, but it is not happening on NEXTSTEP. Linking with g++ issues -lstdc++ but -lsupc++ is not getting brought-in. I have been trying to determine why this does not happen and how to fix it. I assumed (incorrectly) that it was related to some configuration files, but perhaps it has to do with libtool, collect2 or ld? Also please note that all these are static libraries because NEXTSTEP does not support building of shared libraries. >>> >>> >>> What I'm suggesting is that you need to investigate how libstdc++ is >>> built and whether it is being linked with -lsupc++. If it's a static >>> library then libstdc++.a should include the entire contents of >>> libsupc++.a. Presumably that is not happening for some reason; you will >>> need to look at how libstdc++ is built to find out why not. >>> >>> Unfortunately my first guess would some sort of libtool issue on >>> NEXTSTEP. That is unfortunate because libtool is a complex, difficult >>> to understand, shell script. >>> >>> Ian
