From: "Frank Ch. Eigler" <fche@redhat.com>
To: bemis <bemis@iol.unh.edu>
Cc: sid@sources.redhat.com, clp <clp@iol.unh.edu>
Subject: Re: 64 to 32 truncation problems on alpha
Date: Wed, 27 Nov 2002 07:15:00 -0000 [thread overview]
Message-ID: <20021127101546.A12287@redhat.com> (raw)
In-Reply-To: <3DE4CCA1.B9C6452D@iol.unh.edu>; from bemis@iol.unh.edu on Wed, Nov 27, 2002 at 08:46:09AM -0500
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
Hi -
On Wed, Nov 27, 2002 at 08:46:09AM -0500, bemis wrote:
> we are building sid because it is in the toolchain in the uberbaum
> toolchain.
It is in the uberbaum CVS repository, but not part of any CVS module
other than "sid". So if you check out (say) gcc, binutils, gdb modules
from uberbaum rather than the whole thing, you'll have a relevant subset
for a native toolchain. Unless you have an interest in sid, I recommend
simply removing it from your source tree.
> this build was on alphaev67 with the bootstrap-gcc_3.2 baseline.
> we had previous build errors, but those look like they have been fixed.
Right.
> now we are getting this new error on alpha.
> c++ [...]
> ../../component/cgen-cpu/.libs/libcgencpu.a(arm-sem.o)(.rodata+0x1ec):
> relocation truncated to fit: GPREL32 *UND*
> [...]
Sorry, I don't have much insight into this.
I would expect there to be some compiler or linker option
that makes such object files tolerable.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2002-11-27 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 5:46 bemis
2002-11-27 7:15 ` Frank Ch. Eigler [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=20021127101546.A12287@redhat.com \
--to=fche@redhat.com \
--cc=bemis@iol.unh.edu \
--cc=clp@iol.unh.edu \
--cc=sid@sources.redhat.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).