Hello Henning, On Sat, 05 Jul 2008 10:01:14 +0200, Henning Nielsen Lund wrote: [...] > Here is my patch to create and use libgcc.so in stead of libgcc_s.so Thanks for the patch. I just applied it here locally and it seems to work and now a libgcc.so is build instead of libgcc_s.so However, I am still having issues when building some software where it complains about missing symbols (e.g. _Unwind_SjLj_Resume) which point out to be symbols of the exception handling. After some investigation I found out that I can fix that by explicitly specifying "-shared" or "-static" on the link command line. Just with "-use-dynld" doesn't seem to be enough as otherwise the new libgcc_eh.a is not added in the link line. So right now I am a bit confused. Shouldn't be the default "-static"? Why do I have to explicitly add either -static or -shared to get the link working when compiling C++ projects. And what is this "-use-dynld" all about? I thought that the commandline option I need to specify when linking shared. So why do I have to use "-shared"? Anyone has any idea and can explain the current confusion with -shared, -static and -use-dynld? cheers, jens -- Jens Langner, Dresden/Germany http://www.jens-langner.de/ BBS : Mechanism to allow the socially autistic to masquerade as real people and communicate with one another by posting clever near-random commentary on a remote computer. ______________________________________________________________________________ Amiga Development tools ML - //www.freelists.org/list/adtools Homepage...................: http://www.sourceforge.net/projects/adtools Listserver help............: mailto:adtools-request@xxxxxxxxxxxxx?Subject=HELP