public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: p.c.m.chiu@rl.ac.uk To: gcc-gnats@gcc.gnu.org Subject: c/4743: upgrade gcc-2.96 to gcc3.02 failed Date: Tue, 30 Oct 2001 06:56:00 -0000 [thread overview] Message-ID: <20011030145155.32360.qmail@sourceware.cygnus.com> (raw) >Number: 4743 >Category: c >Synopsis: upgrade gcc-2.96 to gcc3.02 failed >Confidential: no >Severity: serious >Priority: high >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Oct 30 06:56:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Peter Chiu >Release: gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98) >Organization: >Environment: Red Hat 7.2 >Description: RedHat 7.2 is shipped with gcc 2.96. I attempted to upgrade this to gcc 3.0.2. Having unravelled the folliwing kits gcc-3.0.2.tar.bz2 gcc-objc-3.0.2.tar.bz2 gcc-g++-3.0.2.tar.bz2 gcc-g77-3.0.2.tar.bz2 MPlayer-0.50.tar.bz2 gcc-java-3.0.2.tar.bz2 into /usr/local, I invoked cd /usr/local/gcc-3.0.2 ./configure and then make bootstrap The following errors came up and the upgrade was terminated abnormally. This bug report is made as suggested by the error messages. ... (cd intl && make all) make[3]: Entering directory `/usr/local/gcc-3.0.2/gcc/intl' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/usr/local/gcc-3.0.2/gcc/intl' (cd po && make all) make[3]: Entering directory `/usr/local/gcc-3.0.2/gcc/po' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/usr/local/gcc-3.0.2/gcc/po' stage1/xgcc -Bstage1/ -B/usr/local/i686-pc-linux-gnu/bin/ -c -DIN_GCC -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -DGENERATOR_FILE -I. -I. -I. -I./. -I./config -I./../include \ ./gencheck.c stage1/xgcc -Bstage1/ -B/usr/local/i686-pc-linux-gnu/bin/ -DIN_GCC -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -DGENERATOR_FILE -o gencheck \ gencheck.o ` case "obstack.o" in ?*) echo obstack.o ;; esac ` ` case "" in ?*) echo ;; esac ` ` case "" in ?*) echo ;; esac ` ` case "" in ?*) echo ;; esac ` ` case "" in ?*) echo ;; esac ` ` case "" in ?*) echo ;; esac ` ./gencheck > tmp-check.h /bin/sh ./move-if-change tmp-check.h tree-check.h echo timestamp > s-check stage1/xgcc -Bstage1/ -B/usr/local/i686-pc-linux-gnu/bin/ -DIN_GCC -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -I. -I. -I. -I./. -I./config -I./../include -c ./c-parse.c /usr/lib/bison.simple: In function `yyparse_1': /usr/lib/bison.simple:761: 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[2]: *** [c-parse.o] Error 1 make[2]: Leaving directory `/usr/local/gcc-3.0.2/gcc' make[1]: *** [stage2_build] Error 2 make[1]: Leaving directory `/usr/local/gcc-3.0.2/gcc' make: *** [bootstrap] Error 2 [root@atsrlx2 gcc-3.0.2]# >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-10-30 6:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-10-30 6:56 p.c.m.chiu [this message] 2001-10-31 20:33 rodrigc
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=20011030145155.32360.qmail@sourceware.cygnus.com \ --to=p.c.m.chiu@rl.ac.uk \ --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).