This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: gcc-4.6.2 build problem related to xgcc not liking '-V' option on i686-pc-linux-gnu
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: "Sinkler, Wharton" <Wharton dot Sinkler at uop dot com>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Fri, 4 Nov 2011 23:41:36 +0000
- Subject: Re: gcc-4.6.2 build problem related to xgcc not liking '-V' option on i686-pc-linux-gnu
- References: <321B372151FBEC4F99C75A6E40DB2D6E038EE368@DE08EV1001.global.ds.honeywell.com>
On 4 November 2011 18:25, Sinkler, Wharton wrote:
> I have been trying unsuccessfully to install gcc-4.6.2, on a Redhat Linux VM.? The configure step seems to work fine.? I'm using the following configure options (installing 4.6.2 from a 'gcc_build' directory as suggested on the website; I already installed the required dependencies under /usr/local as indicated):
>
> ../gcc-4.6.2/configure --with-gmp=/usr/local --with-mpfr=/usr/local --with-mpc=/usr/local --with-ppl=/usr/local --with-cloog=/usr/local \
> ???? LDFLAGS="-L/usr/local/lib -Xlinker -R/usr/local/lib" CONFIG_SHELL=/bin/bash -enable-languages=c,c++,fortran
>
> Under 'make' I am getting the following error:
>
> checking for suffix of object files... configure: error: in `/home/E341484/gnu-install/gcc_build/i686-pc-linux-gnu/libgcc':
> configure: error: cannot compute suffix of object files: cannot compile
> See `config.log' for more details.
>
> I found more detail on the make failure in the file ./i686-pc-linux-gnu/libgcc/config.log, which shows an error occurring at this statement:
>
> configure:3028: /home/E341484/gnu-install/gcc_build/./gcc/xgcc -B/home/E341484/gnu-install/gcc_build/./gcc/ -B/usr/local/i686-pc-linux-gnu/bin/ -B/usr/local/i686-pc-linux-gnu/lib/ -isystem /usr/local/i686-pc-linux-gnu/include -isystem /usr/local/i686-pc-linux-gnu/sys-include??? -V >&5
> xgcc: error: unrecognized option '-V'
> xgcc: fatal error: no input files
> compilation terminated.
>
> I think this is really the cause of the problem.
No it isn't, 'configure' is supposed to fail at various points, that's
how it determines what your platform supports and what it doesn't.
That error is non-fatal and is not why your build failed, this is why
it failed:
http://gcc.gnu.org/wiki/FAQ#configure_suffix
This is the simplest way to build gcc:
http://advogato.org/person/redi/diary/253.html