From: "David S. Miller" <davem@redhat.com>
To: amodra@bigpond.net.au
Cc: Eric_Dana@bmc.com, binutils@sources.redhat.com, gcc-bugs@gcc.gnu.org
Subject: Re: Using binutils-2.12.1 on sparc64-sun-solaris2.8 to build gcc-3.1 results in relocation errors
Date: Tue, 16 Jul 2002 00:14:00 -0000 [thread overview]
Message-ID: <20020715.194414.38696473.davem@redhat.com> (raw)
In-Reply-To: <20020716024012.GE30362@bubble.sa.bigpond.net.au>
From: Alan Modra <amodra@bigpond.net.au>
Date: Tue, 16 Jul 2002 12:10:12 +0930
On Mon, Jul 15, 2002 at 12:45:33PM -0500, Dana, Eric wrote:
> When building some of our 64-bit libraries in C++, we are seeing
> R_SPARC_DISP32 errors:
Please try current binutils CVS. If the problem isn't fixed there,
now would be the time to shout about it. We're about to release 2.13.
Actually this looks like some kind of code-model error.
There should not be any R_SPARC_DISP32 relocations generated
as no "call" instruction based function invocations should
be emitted with Solaris's default code model.
"Call" is the only way R_SPARC_DISP32 relocations can be
emitted.
I really doubt this is a binutils bug. It is either some user
configuration error, or the libtool machinery is causing the
wrong code model to be used when generating the c++ libraries
and/or binaries.
If these folks are specifying the code-model explicitly on the
command line, and linking with libstdc++ this could cause errors
like the above as well.
next prev parent reply other threads:[~2002-07-16 2:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-15 10:46 Dana, Eric
2002-07-15 19:56 ` Alan Modra
2002-07-16 0:14 ` David S. Miller [this message]
2002-07-17 10:54 ` Teemu Torma
2002-07-17 18:32 ` Alan Modra
2002-07-17 20:20 ` David S. Miller
2002-07-18 8:17 ` Teemu Torma
2002-07-18 0:45 ` Jakub Jelinek
-- strict thread matches above, loose matches on Subject: below --
2002-07-15 8:24 Dana, Eric
2002-05-28 7:50 Brad Spencer
2002-07-29 20:53 ` Daniel Jacobowitz
2002-07-30 5:22 ` Brad Spencer
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=20020715.194414.38696473.davem@redhat.com \
--to=davem@redhat.com \
--cc=Eric_Dana@bmc.com \
--cc=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=gcc-bugs@gcc.gnu.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).