From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] "unsupported reloc" error with ld
Date: Thu, 16 Nov 2000 20:43:54 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205736@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205735@msgid-missing>
>Can a compiler person out there provide some insight
>on the following error I get with some C++ code when
>doing a final bind with ld:
>fs/fs.o(.IA_64.unwind+0x98b8): unsupported reloc
>(... a bunch of these ...)
The fs.o object file contains a relocation that GNU ld does not support
in the context where it appeared. It is not possible to say anything more
about this problem without further info. If you debug the linker, you
can find out the number of the relocation and the context where it is being
used. Or if you provide object files to me, I can do this.
Are you using gcc? If you are using some other compiler, then the other
compiler could be emitting relocs that GNU ld doesn't support yet.
The dwarf error messages can be ignored. The linker is trying to pretty
print error messages by using the debug info to determine the function name
and line number where the problem occured. This pretty printing code is
failing because the debug info hasn't been relocated yet, and hence isn't
valid as is. Someday this will be fixed by extending this code to relocate
the debug info before trying to use it if possible.
Neither old message seems relevant to me.
Jim
prev parent reply other threads:[~2000-11-16 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-16 20:18 [Linux-ia64] "unsupported reloc" error with ld gjertsen
2000-11-16 20:43 ` Jim Wilson [this message]
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=marc-linux-ia64-105590678205736@msgid-missing \
--to=wilson@cygnus.com \
--cc=linux-ia64@vger.kernel.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