From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: egcs@egcs.cygnus.com
Subject: bootstrapping with `cc -n32' on IRIX 6.3 fails compare
Date: Sun, 21 Mar 1999 10:01:00 -0000 [thread overview]
Message-ID: <orhfrevi9i.fsf@dcc.unicamp.br> (raw)
Can anyone else confirm that it's not just my cc for IRIX 6.3 that's
broken? I've never been able to bootstrap egcs with `cc -n32' (the
-n32 is needed for libiberty); it always fails `make compare' for all
object files (I haven't really checked if some are missing, but the
list of failures is huge). Then, if a proceed with `bootstrap2', it
moves the stage3 compiler into stage2, builds a new stage3 and then
compare succeeds. Does this sound familiar to anyone? Is this
expected? Do we care about fixing it, or should we just document it
and put the blame on SGI? :-)
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva IC-Unicamp, Brasil
{oliva,Alexandre.Oliva}@dcc.unicamp.br aoliva@{acm.org,computer.org}
oliva@{gnu.org,kaffe.org,egcs.cygnus.com,samba.org}
*** E-mail about software projects will be forwarded to mailing lists
WARNING: multiple messages have this Message-ID
From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: egcs@egcs.cygnus.com
Subject: bootstrapping with `cc -n32' on IRIX 6.3 fails compare
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <orhfrevi9i.fsf@dcc.unicamp.br> (raw)
Message-ID: <19990331234600.ppT0G4XYg5nJiRH7aGx04D7xxgh84Xmf6n3ZCOqRP3Q@z> (raw)
Can anyone else confirm that it's not just my cc for IRIX 6.3 that's
broken? I've never been able to bootstrap egcs with `cc -n32' (the
-n32 is needed for libiberty); it always fails `make compare' for all
object files (I haven't really checked if some are missing, but the
list of failures is huge). Then, if a proceed with `bootstrap2', it
moves the stage3 compiler into stage2, builds a new stage3 and then
compare succeeds. Does this sound familiar to anyone? Is this
expected? Do we care about fixing it, or should we just document it
and put the blame on SGI? :-)
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva IC-Unicamp, Brasil
{oliva,Alexandre.Oliva}@dcc.unicamp.br aoliva@{acm.org,computer.org}
oliva@{gnu.org,kaffe.org,egcs.cygnus.com,samba.org}
*** E-mail about software projects will be forwarded to mailing lists
next reply other threads:[~1999-03-21 10:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-21 10:01 Alexandre Oliva [this message]
1999-03-31 23:46 ` Alexandre Oliva
1999-03-23 9:35 Kaveh R. Ghazi
1999-03-24 0:04 ` Alexandre Oliva
[not found] ` <tprvhfruwva.fsf@cs.ucsb.edu>
1999-03-24 0:32 ` Alexandre Oliva
[not found] ` <tprsoavuvw0.fsf@cs.ucsb.edu>
1999-03-24 0:45 ` Alexandre Oliva
1999-03-31 23:46 ` Alexandre Oliva
1999-03-31 23:46 ` Alexandre Oliva
1999-03-31 23:46 ` Alexandre Oliva
[not found] ` <oriubr70o5.fsf.cygnus.egcs@dcc.unicamp.br>
1999-03-24 12:41 ` Jim Wilson
1999-03-31 23:46 ` Jim Wilson
1999-03-31 23:46 ` Kaveh R. Ghazi
1999-03-24 5:10 Kaveh R. Ghazi
1999-03-31 23:46 ` Kaveh R. Ghazi
1999-03-24 5:13 Kaveh R. Ghazi
1999-03-24 5:20 ` Alexandre Oliva
1999-03-31 23:46 ` Alexandre Oliva
1999-03-31 23:46 ` Kaveh R. Ghazi
1999-03-24 6:16 N8TM
1999-03-31 23:46 ` N8TM
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=orhfrevi9i.fsf@dcc.unicamp.br \
--to=oliva@dcc.unicamp.br \
--cc=egcs@egcs.cygnus.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).