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
this is for centos3 64bit
What options are you supplying to configure? How are you invoking make?
Subject: Re: gcc doesn't compile on centos3 64bit no option at all, being in a new directory out of the tree /tmp/gcc/gcc44 I do /tmp/gcc/gcc-4.4.0/gcc/configure and then make that's it pinskia at gcc dot gnu dot org wrote: > ------- Comment #2 from pinskia at gcc dot gnu dot org 2009-07-09 23:18 ------- > What options are you supplying to configure? How are you invoking make? > > >
> build/genmodes -h> tmp-modes.h > /bin/sh: line 1: build/genmodes: No such file or directory > make: *** [s-modes-h] Error 127 This is the error you can get when a program interpreter does not exist. More recent linux versions will print a better error message, but old ones do give this ambiguous message for this problem. For an ELF binary linked against glibc, the program interpreter is ld.so. Maybe you are missing some library files? build/genmodes is incidentally the first binary we will run that was compiled by the just built gcc, so a configure error sometimes shows up as a build/genmodes failure. Try running "ldd build/genmodes". You might also try "objdump --full-contents --section .interp build/genmodes". If either of these list non-existent files in the output, then that is the problem.
> make: *** [s-modes-h] Error 127 it looks it segfaults. What is your host compiler version?
No feedback in over 2 year so closing.