public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: iain@videonetworks.com To: gcc-gnats@gcc.gnu.org Subject: c/3454: cc1 segmentation fault when building gcc 3.0 cross compiler Date: Thu, 28 Jun 2001 02:26:00 -0000 [thread overview] Message-ID: <20010628092434.27304.qmail@sourceware.cygnus.com> (raw) >Number: 3454 >Category: c >Synopsis: cc1 segmentation fault when building gcc 3.0 cross compiler >Confidential: no >Severity: critical >Priority: high >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Jun 28 02:26:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: iain@videonetworks.com >Release: unknown-1.0 >Organization: >Environment: i686 redhat linux 6.1 >Description: I downloaded gcc 3.0. Built it with "make bootstrap" and installed it. I then used it to build a cross compiler using: configure --target=powerpc-eabi --with-cpu=403 and building with: make LANGUAGES="c c++" This all seems to work fine until half way through the build I get this: -- ... echo "int xxy_us_dummy;" >tmp-dum.c /home/iain/app/gcc-3.0-powerpc/gcc/xgcc -B/home/iain/app/gcc-3.0-powerpc/gcc/ -B/usr/local/powerpc-eabi/bin/ -B/usr/local/powerpc-eabi/lib/ -isystem /usr/local/powerpc-eabi/include -S tmp-dum.c cc1: Internal error: Segmentation fault Please submit a full bug report, etc... -- This is using: /home/iain/app/gcc-3.0-powerpc/gcc/cc1, not cc1 in any of the other paths. I don't reckon I've made any obvious errors, and cc1 certainly shouldn't just crash anyway. Please let me know if you need/want any more information, Cheers Iain. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-06-28 2:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-28 2:26 iain [this message] 2001-06-28 2:32 neil
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=20010628092434.27304.qmail@sourceware.cygnus.com \ --to=iain@videonetworks.com \ --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).