From: bemis <bemis@iol.unh.edu>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: "sid@sources.redhat.com" <sid@sources.redhat.com>,
clp <clp@iol.unh.edu>, George France <france@handhelds.org>
Subject: Re: relocation truncated to fit: GPREL32 *UND*
Date: Sat, 07 Dec 2002 11:38:00 -0000 [thread overview]
Message-ID: <3DF24E0F.CC6E11DB@iol.unh.edu> (raw)
In-Reply-To: <20021207190545.GA31718@redhat.com>
I have removed SID from our main toolchain build, but I have also created
a toolchain_sid build.
We try to make Alpha linux a viable linux solution for people with
alphas. When something may be needed such as sid it would be nice to know
that it works on alphas with the newest compilers. I will look into "g++
--help -v".
thanks again.
to see the toolchain_sid build on a daily basis
http://www.handhelds.org/projects/toolchain/autobuild/
and click on results or stats to see if the build succeeded.
"Frank Ch. Eigler" wrote:
> Hi -
>
> On Sat, Dec 07, 2002 at 11:49:21AM -0500, bemis wrote:
> > Sid will not compile on Alpha. On a intel SID compiles without a
> > problem. Is there something missing from the configuration of sid on
> > alpha. the machine code is trying to put 64 bits into 32 bits.
> > any suggestions on where to look for the problem would be appreciated
> > [...]
>
> I thought I answered this already. Actually, I did:
> http://sources.redhat.com/ml/sid/2002-q4/msg00033.html
>
> There might be some compiler or linker option to use for
> building alpha programs above some threshold of unusual size.
> I don't know what options your toolchain has: try "g++ --help -v"
> and see if anything looks promising.
>
> - FChE
prev parent reply other threads:[~2002-12-07 19:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-07 8:49 bemis
2002-12-07 11:05 ` Frank Ch. Eigler
2002-12-07 11:38 ` bemis [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=3DF24E0F.CC6E11DB@iol.unh.edu \
--to=bemis@iol.unh.edu \
--cc=clp@iol.unh.edu \
--cc=fche@redhat.com \
--cc=france@handhelds.org \
--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).