John Marino <gnugcc@xxxxxxxxx> writes: > Ian Lance Taylor wrote: >> It's decidedly odd that gcc is linking against the system libgcc.a at >> build time. That should not happen. gcc should always link against the >> appropriate libgcc.a. >> > > Agreed. That's why it took me so long to recognize what was > happening. I wasn't looking for this possibility. Is there another > explanation that the software builds after eliminating > /usr/lib/libgcc*.a ? No, I can't think of one. But this is clearly the thing to investigate. If you run gcc -v while doing a link, it will show you the library search path. The libgcc.a appropriate to that version of gcc should be on the path before /usr/lib. Ian
