From: Paul Koning <pkoning@equallogic.com>
To: amodra@bigpond.net.au
Cc: drow@false.org, binutils@sources.redhat.com
Subject: Re: Unintellegible ld error messages
Date: Sun, 15 May 2005 19:44:00 -0000 [thread overview]
Message-ID: <17031.38996.793456.366778@gargle.gargle.HOWL> (raw)
In-Reply-To: <20050514015015.GC27573@bubble.grove.modra.org>
>>>>> "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
next prev parent reply other threads:[~2005-05-15 18:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 19:11 Paul Koning
2005-05-11 19:30 ` Daniel Jacobowitz
2005-05-13 19:50 ` Paul Koning
2005-05-13 20:08 ` Daniel Jacobowitz
2005-05-13 20:59 ` Paul Koning
2005-05-14 4:59 ` Alan Modra
2005-05-15 19:44 ` Paul Koning [this message]
2005-05-20 9:54 ` Alan Modra
2005-05-13 21:25 ` H. J. Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17031.38996.793456.366778@gargle.gargle.HOWL \
--to=pkoning@equallogic.com \
--cc=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=drow@false.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).