From: paulf@metaip.checkpoint.com
To: gcc-help@gcc.gnu.org
Subject: stage1 seg fault on i586-ncr-sysv4.3.03
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <B5C5D2CDB8BCD2118E4800A0C9D8E4C76F6F40@cartman.metainfo.com> (raw)
Message-ID: <20000401000000.MkrNsRRUh5qVIKa3i2ogC2ihzI_0iQuD1zHioqXvZ5A@z> (raw)
Using binutils 2.9.1, --with-gnu-as and --with-gnu-ld, 2.95.2 fails make
bootstrap, just after gcc/stage1 is populated. This machine does not have a
decent debugger (gdb won't even build on it) so I can't tell you much more
than "it crashed". I have only changed gcc/auto-host.h to #define
HAVE_LIMITS_H to 1 (necessary for it to even get this far).
I have seen (unanswered) postings from other people having this exact
problem on other architectures..
./gencheck > tmp-check.h
Segmentation Fault - core dumped
make[2]: *** [s-check] Error 139
make[2]: Leaving directory `/a1/paulf/software/gcc-2.95.2/objdir/gcc'
make[1]: *** [bootstrap] Error 2
make[1]: Leaving directory `/a1/paulf/software/gcc-2.95.2/objdir/gcc'
make: *** [bootstrap] Error 2
next reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-25 18:46 paulf [this message]
2000-04-01 0:00 ` paulf
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=B5C5D2CDB8BCD2118E4800A0C9D8E4C76F6F40@cartman.metainfo.com \
--to=paulf@metaip.checkpoint.com \
--cc=gcc-help@gcc.gnu.org \
/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).