From: Richard Henderson <rth@cygnus.com>
To: pancho@galaxy.lca.uevora.pt
Cc: egcs@cygnus.com
Subject: Re: error in alpha ev56
Date: Fri, 02 Jan 1998 16:09:00 -0000 [thread overview]
Message-ID: <19980102160709.14510@dot.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.3.96.980102201818.22056B-100000@galaxy.lca.uevora.pt>
On Fri, Jan 02, 1998 at 08:19:18PM +0000, pancho@galaxy.lca.uevora.pt wrote:
> here is the list of errors during compilation of egcs in a alpha ev56
>
> xgcc: Internal compiler error: program cc1 got fatal signal 6
There are some deficiencies wrt ev56 support in the binutils 2.8.1.0.1
that was shipped with RH5.0. I would suggest first bootstrapping EGCS
as --target=alphaev5-unknown-linux-gnu (rather than alphaev56) just to
be sure that things are sane.
After that, we can see about possibly upgrading binutils and rebuilding
EGCS to take advantage of the byte/word extension on the ev56.
r~
next prev parent reply other threads:[~1998-01-02 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-02 12:19 pancho
1998-01-02 16:09 ` Richard Henderson [this message]
1998-01-02 16:09 ` pancho
1998-01-02 16:44 ` pancho
1998-01-02 16:44 ` pancho
1998-01-05 9:23 ` Slow processing with g77 in egcs pancho
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=19980102160709.14510@dot.cygnus.com \
--to=rth@cygnus.com \
--cc=egcs@cygnus.com \
--cc=pancho@galaxy.lca.uevora.pt \
/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).