public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jbglaw@lug-owl.de To: gcc-gnats@gcc.gnu.org Subject: bootstrap/9741: ICE (segfault) while building a cross compiler Date: Tue, 18 Feb 2003 11:46:00 -0000 [thread overview] Message-ID: <20030218114318.3404.qmail@sources.redhat.com> (raw) >Number: 9741 >Category: bootstrap >Synopsis: ICE (segfault) while building a cross compiler >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Feb 18 11:46:01 UTC 2003 >Closed-Date: >Last-Modified: >Originator: jbglaw@lug-owl.de >Release: gcc-HEAD as of about 09:00 UTC 2003-02-18 >Organization: >Environment: Building current gcc HEAD on hppa-linux (current debian sid on a HP B132L) >Description: I tried to create a hppa-linux hosted C-only (for kernel) cross compiler for alpha-linux: ../gcc/configure --target=alpha-linux --prefix=/usr/local/ --disable-shared --disable-nls --enable-languages=c After 'make', this leads to: /home/jbglaw/build/gcc/xgcc -B/home/jbglaw/build/gcc/ -B/usr/local//alpha-linux/bin/ -B/ usr/local//alpha-linux/lib/ -isystem /usr/local//alpha-linux/include -O2 -DIN_GCC -DCRO SS_COMPILE -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -fPIC -mieee -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Di nhibit_libc -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include -DL_muldi3 -c ../../gcc/gcc/libgcc2.c -o libgcc/./_muldi3.o In file included from /usr/include/signal.h:33, from ../../gcc/gcc/config/alpha/linux.h:72, from tm.h:5, from ../../gcc/gcc/libgcc2.c:43: /usr/include/bits/sigset.h:30: error: size of array `__val' is too large /usr/include/bits/sigset.h:31: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. I do not include sources since you should have them:-) >How-To-Repeat: Simply start a compile. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-02-18 11:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-18 11:46 jbglaw [this message] 2003-05-14 18:36 Dara Hazeghi 2003-05-17 6:57 giovannibajo 2003-05-18 13:26 Jan-Benedict Glaw
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=20030218114318.3404.qmail@sources.redhat.com \ --to=jbglaw@lug-owl.de \ --cc=gcc-gnats@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: linkBe 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).