From: Ritu Sabharwal <ritu@csa.iisc.ernet.in>
To: gcc@gcc.gnu.org
Subject: Segmentation fault in compiling gcc 3.0
Date: Tue, 08 Oct 2002 19:30:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0210090608510.2065-100000@opal.csa.iisc.ernet.in> (raw)
We tried to compile gcc-3.0, configuration went right but when we did
$ make bootstrap-lean we gotthe following error....
if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi
/xgcc -B./ -B/home/deepakbn/gcc-3.0//ia64-unknown-linux/bin/ -isystem
/home/deepakbn/gcc-3.0//ia64-unknown-linux/include -O2 -DIN_GCC -W
-Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem
/include -fPIC -g1 -DIN_LIBGCC2 -D
__GCC_FLOAT_NOT_NEEDED -I. -I. -I../gcc -I../gcc/. -I../gcc/config
-I../gcc/../include -DL_muldi3 -c ../gcc/libgcc2.c -o lib
gcc/./_muldi3.o
HERE
./gcc/libgcc2.c: In function `__multi3':
./gcc/libgcc2.c:368: Internal error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[1]: *** [libgcc/./_muldi3.o] Error 1
Any idea what is going wrong in this?
regards,
Ritu.
reply other threads:[~2002-10-09 0:39 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=Pine.LNX.4.44.0210090608510.2065-100000@opal.csa.iisc.ernet.in \
--to=ritu@csa.iisc.ernet.in \
--cc=gcc@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).