On Mon, Nov 07, 2005 at 07:40:51AM -0800, Ulrich Drepper wrote: > Daniel Jacobowitz wrote: > > The only real problem with this is that it mandates use of shared > > libgcc for the routines in question... always. If they ever go into > > libgcc.a, we can't make sure we got the right copy. > > This is what lies ahead of us anyway. Solaris apparently official > denounced static linking for the system libs completely and you can find > many comments to the same effect from me, too. We have to get away from > the limitations static linking is imposing. > > For those who really really need static linking, use the least common > denominator. It's those people who have to pay the price, not the > (sane) rest of us.
Works for me. I'll let someone else figure out how to handle this on targets without shared libgcc. -- Daniel Jacobowitz CodeSourcery, LLC
