> > I must admit that my first description of the problem was a bit > outdated, > > but I will give you some more information: I first tried the > > gcc-4.0-10012005 snapshot, together with the -fno-exceptions flag, and > > there was no dynamic linking of libgcc_s.so necessary. gcc-3.4.3 works > in > > the same way, no dynamic linking necessary. With the newest snapshot > > gcc-4.0-07032005 there is dynamic linking necessary. The code is written > in > > C++, but there is no exception handling. > > That's a bit odd. However we would need more information to properly > diagnose > the problem, if any. >
ok, it seems that it was my error, I recompile gcc-4.0-10012005 to verify the behaviour, but libgcc_s.so needs to be linked in any case. gcc-3.4 works because I changed the specs file, but then I thougth it was due to the compiler flags, which wasn't the case. But what I don't understand is why libgcc_s.so is needed. I have no exception handling in my souces, and furthermore I use -fno-exceptions. I understand that I should link libgcc_eh.so dynamically for exception handling. I did a nm on the resulting so, and there were no references to GCC_xx, only to SYSVABI_xx and SUNW_xx. What Information would you need for further investigation, or is it simple to say: On Solaris, libgcc_s.so is always linked to c++ programs? thanks for your help, regards, Roland Lengfeldner -- DSL Komplett von GMX +++ Supergünstig und stressfrei einsteigen! AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl
