public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: wharms@bfs.de To: gcc-gnats@gcc.gnu.org Subject: c/7664: gcc-3.2 build problem gengenrtl Date: Tue, 20 Aug 2002 12:46:00 -0000 [thread overview] Message-ID: <20020820193650.27614.qmail@sources.redhat.com> (raw) >Number: 7664 >Category: c >Synopsis: gcc-3.2 build problem gengenrtl >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Aug 20 12:46:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: wharms@bfs.de >Release: unknown-1.0 >Organization: >Environment: linux 2..2.12 (alpha) gcc 2.95.2 ./configure ./make bootstrap >Description: gengenrtl can not be created /usr/bin/ld: gengenrtl: Not enough room for program headers (allocated 6, need 7) /usr/bin/ld: final link failed: Bad value collect2: ld returned 1 exit status note: i have changed the asm optiuon in the specs file because the created option didnt work at all. (reported earlier) >How-To-Repeat: >Fix: compile without -g # stage1/xgcc -Bstage1/ -B/usr/local/alphaev56-unknown-linux-gnu/bin/ -c -DIN_GCC -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 ./gengenrtl.c -o gengenrtl.o # stage1/xgcc -Bstage1/ -B/usr/local/alphaev56-unknown-linux-gnu/bin/ -DIN_GCC -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -DGENERATOR_FILE -o gengenrtl gengenrtl.o ../libiberty/libiberty.a I suspect that -g is broken for ALPHA processors. I had already created a gcc-3.2 but did a rebuild with make bootstrap in place of make. The first version created not working debug hunks. >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-08-20 19:46 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=20020820193650.27614.qmail@sources.redhat.com \ --to=wharms@bfs.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).