From: karipid@mae.cornell.edu (Daniel Karipides)
To: egcs@cygnus.com
Subject: bootstrap failure of egcs-19980508 on mips-sgi-irix5.3
Date: Mon, 11 May 1998 10:23:00 -0000 [thread overview]
Message-ID: <199805111616.MAA03530@scotch.mae.cornell.edu> (raw)
First off, thanks to everyone who gave prebuild advice. I'm
always impressed how helpful people on the egcs list are.
As I was warned, the current snapshot of egcs fails on irix5.3
if you use binutils-2.9.1. Here are the details:
config.guess: mips-sgi-irix5.3
configure options: --with-gnu-as
using: binutils-2.9.1
egcs-19980508
latest gnumake (3.76?)
initial compiler: egcs-1.0.2
Build directory was completely separate from the src directory.
The build fails in the comparison of the final stage compiler:
tail +16c stage$stage/$file > tmp-foo2 \
&& (cmp tmp-foo1 tmp-foo2 > /dev/null 2>&1 || echo $file differs >> .bad_compare) || true; \
done
case "compare" in compare | compare-lean ) stage=2 ;; * ) stage=`echo compare | sed -e 's,^compare\([0-9][0-9]*\).*,\1,'` ;; esac; \
for dir in tmp-foo cp f objc; do \
if [ "`echo $dir/*.o`" != "$dir/*.o" ] ; then \
for file in $dir/*.o; do \
tail +16c ./$file > tmp-foo1; \
tail +16c stage$stage/$file > tmp-foo2 \
&& (cmp tmp-foo1 tmp-foo2 > /dev/null 2>&1 || echo $file differs >> .bad_compare) || true; \
done; \
fi; \
done
rm -f tmp-foo*
case "compare" in compare | compare-lean ) stage=2 ;; * ) stage=`echo compare | sed -e 's,^compare\([0-9][0-9]*\).*,\1,'` ;; esac; \
if [ -f .bad_compare ]; then \
echo "Bootstrap comparison failure!"; \
cat .bad_compare; \
exit 1; \
else \
case "compare" in \
*-lean ) rm -rf stage$stage ;; \
*) ;; \
esac; true; \
fi
Bootstrap comparison failure!
mips.o differs
make[1]: *** [compare] Error 1
make[1]: Leaving directory `/scratch/egcsobjdir/gcc'
make: *** [bootstrap] Error 2
---------------------
Hope these details are helpful to someone.
-Dan
-----
karipid@mae.cornell.edu
reply other threads:[~1998-05-11 10:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199805111616.MAA03530@scotch.mae.cornell.edu \
--to=karipid@mae.cornell.edu \
--cc=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).