From: Daniel Jacobowitz <drow@false.org>
To: Paul Koning <pkoning@equallogic.com>
Cc: binutils@sources.redhat.com
Subject: Re: Unintellegible ld error messages
Date: Wed, 11 May 2005 19:30:00 -0000 [thread overview]
Message-ID: <20050511191110.GA470@nevyn.them.org> (raw)
In-Reply-To: <17026.22346.789514.57742@gargle.gargle.HOWL>
On Wed, May 11, 2005 at 03:04:42PM -0400, Paul Koning wrote:
> I got these messages from ld (version 2.16):
>
> /usr/local/EQLGCC_v7/mipsel/lib/gcc/mipsel-netbsdelf/4.0.0/../../../../mipsel-netbsdelf/bin/ld: Cli: hidden symbol `_Unwind_GetIP' in /usr/local/EQLGCC_v7/mipsel/lib/gcc/mipsel-netbsdelf/4.0.0/libgcc.a(unwind-dw2.o) is referenced by DSO
> /usr/local/EQLGCC_v7/mipsel/lib/gcc/mipsel-netbsdelf/4.0.0/../../../../mipsel-netbsdelf/bin/ld: final link failed: Nonrepresentable section on output
>
> I haven't a clue what these mean. What'a DSO? What's a
> "nonrepresentable section"? More importantly, what should I do to
> find out what is wrong here?
Dynamic Shared Object. This is a standard term. It's not mentioned in
the ld manual; feel free to contribute a patch.
The hidden symbol `_Unwind_GetIP' is being referenced by a shared
library. Figure out which one it is (I don't remember the reason why
we don't print that here; I believe it's pretty hard to recover from
our data structures at that point). Then rebuild that library using
'gcc' to link and the symbol should no longer be undefined.
> I even tried looking at the source code. That tells me that "DSO"
> apparently has something to do with shared libraries, but other than
> that it doesn't get me any closer to a solution.
Google would have been happy to tell you that "DSO" and "shared
library" are basically synonyms.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-11 19:11 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 [this message]
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
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=20050511191110.GA470@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sources.redhat.com \
--cc=pkoning@equallogic.com \
/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).