From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2401 invoked by alias); 18 Jul 2009 20:06:01 -0000 Received: (qmail 2358 invoked by uid 48); 18 Jul 2009 20:05:46 -0000 Date: Sat, 18 Jul 2009 20:06:00 -0000 Message-ID: <20090718200546.2357.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug bootstrap/40706] gcc doesn't compile on centos3 64bit In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "wilson at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-07/txt/msg01515.txt.bz2 ------- Comment #4 from wilson at gcc dot gnu dot org 2009-07-18 20:05 ------- > 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. -- wilson at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wilson at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40706