public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "junk at ysengrin dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/40706] New: gcc doesn't compile on centos3 64bit Date: Thu, 09 Jul 2009 23:16:00 -0000 [thread overview] Message-ID: <bug-40706-17933@http.gcc.gnu.org/bugzilla/> (raw) this is true for 4.2.4, 4.3.3 and 4.4.0 (note that 3.4.6 builds normally): performed a clean install, then configured in a fully separate directory, the configure is performing without error. still in a fully separate directory, run make (I've tried version 3.79.1 and the latest 3.81): TARGET_CPU_DEFAULT="" \ HEADERS="auto-host.h ansidecl.h" DEFINES="" \ /bin/sh /tmp/gcc/gcc-4.2.4/gcc/mkconfig.sh config.h TARGET_CPU_DEFAULT="" \ HEADERS="options.h config/i386/biarch64.h config/i386/i386.h config/i386/unix.h config/i386/att.h config/dbxelf.h config/elfos.h config/svr4.h config/linux.h config/i386/x86-64.h config/i386/linux64.h defaults.h" DEFINES="UCLIBC_DEFAULT=0" \ /bin/sh /tmp/gcc/gcc-4.2.4/gcc/mkconfig.sh tm.h gawk -f /tmp/gcc/gcc-4.2.4/gcc/opt-gather.awk /tmp/gcc/gcc-4.2.4/gcc/ada/lang.opt /tmp/gcc/gcc-4.2.4/gcc/fortran/lang.opt /tmp/gcc/gcc-4.2.4/gcc/java/lang.opt /tmp/gcc/gcc-4.2.4/gcc/treelang/lang.opt /tmp/gcc/gcc-4.2.4/gcc/c.opt /tmp/gcc/gcc-4.2.4/gcc/common.opt /tmp/gcc/gcc-4.2.4/gcc/config/i386/i386.opt /tmp/gcc/gcc-4.2.4/gcc/config/linux.opt > tmp-optionlist /bin/sh /tmp/gcc/gcc-4.2.4/gcc/../move-if-change tmp-optionlist optionlist echo timestamp > s-options gawk -f /tmp/gcc/gcc-4.2.4/gcc/opt-functions.awk -f /tmp/gcc/gcc-4.2.4/gcc/opth-gen.awk \ < optionlist > tmp-options.h /bin/sh /tmp/gcc/gcc-4.2.4/gcc/../move-if-change tmp-options.h options.h echo timestamp > s-options-h TARGET_CPU_DEFAULT="" \ HEADERS="auto-host.h ansidecl.h" DEFINES="" \ /bin/sh /tmp/gcc/gcc-4.2.4/gcc/mkconfig.sh bconfig.h gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute -DHAVE_CONFIG_H -DGENERATOR_FILE -I. -Ibuild -I/tmp/gcc/gcc-4.2.4/gcc -I/tmp/gcc/gcc-4.2.4/gcc/build -I/tmp/gcc/gcc-4.2.4/gcc/../include -I/tmp/gcc/gcc-4.2.4/gcc/../libcpp/include -I/tmp/gcc/gcc-4.2.4/gcc/../libdecnumber -I../libdecnumber -o build/errors.o /tmp/gcc/gcc-4.2.4/gcc/errors.c build/genmodes -h > tmp-modes.h /bin/sh: line 1: build/genmodes: No such file or directory make: *** [s-modes-h] Error 127 -- Summary: gcc doesn't compile on centos3 64bit Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: junk at ysengrin dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40706
next reply other threads:[~2009-07-09 23:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-07-09 23:16 junk at ysengrin dot com [this message] 2009-07-09 23:17 ` [Bug c/40706] " junk at ysengrin dot com 2009-07-09 23:18 ` [Bug bootstrap/40706] " pinskia at gcc dot gnu dot org 2009-07-09 23:21 ` junk at ysengrin dot com 2009-07-18 20:06 ` wilson at gcc dot gnu dot org 2009-07-18 20:29 ` rguenth at gcc dot gnu dot org
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=bug-40706-17933@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).