Re: Unintellegible ld error messages

[Paul Koning <pkoning at equallogic dot com>]

>>>>> "Alan" == Alan Modra <amodra@bigpond.net.au> writes:

 Alan> On Fri, May 13, 2005 at 04:07:56PM -0400, Paul Koning wrote:
 >> It turns out that libgcc.so has _Unwind_GetIP as a regular symbol,
 >> but libgcc.a has it as a hidden symbol.  One of my builds only has
 >> the .a version of libgcc, so that's why that link fails (while
 >> others for another target work fine).

 Alan> _Unwind_GetIP as a hidden symbol in libgcc.a is not the
 Alan> problem.  If you built libstdc++.so linked against libgcc_s.so,
 Alan> then when linking using libstdc++.so you need to have
 Alan> libgcc_s.so available, and, importantly, libgcc_s.so must be
 Alan> linked before libgcc.a if both are specified.

 Alan> If you built libstdc++.so only linked against libgcc.a, then
 Alan> you can use libstdc++.so like that too.

Interesting.  objdump says that libstdc++ requires libm, but not
libgcc_s.  And libm doesn't require anything.

	   paul