gcc 4.4.0 fails to build on IRIX 6.5 - No /gcc Makefile - More Information

Ralf Wildenhues Ralf.Wildenhues@gmx.de
Sat Aug 15 08:47:00 GMT 2009


Hello George,

* Tovrea, George W (US SSA) wrote on Tue, Jul 28, 2009 at 05:18:03PM CEST:
> On 7/28/09 9:43 AM, "Tovrea, George W (US SSA)" wrote:
> 
> > Config.log indicates that the configure command line in gcc is
> > incorrectly generated:
> > 
> > /home/users/tovrea/FFMPEG/gcc-4.4.0-RC-20090414/gcc/configure
> > --cache-file=./config.cache --prefix=/home/users/tovrea/FFMPE
> > 
> > This line should read (created manually using the intl config.log)
> > 
> > /home/users/tovrea/FFMPEG/gcc-4.4.0-RC-20090414/gcc/configure
> > --cache-file=./config.cache
> > --prefix=/home/users/tovrea/FFMPEG/gcc-4.4.0-prefix-sgi6
> > --enable-bootstrap --enable-version-specific-runtime-libs
> > --with-ppl=/home/users/tovrea/FFMPEG/gcc-4.4.0-ppl/ppl
> > --with-cloog=/home/users/tovrea/FFMPEG/gcc-4.4.0-ppl/cloog-ppl
> > --enable-languages=c,c++ --program-transform-name=s,y,y,
> > --build=mips-sgi-irix6.5 --host=mips-sgi-irix6.5
> > --target=mips-sgi-irix6.5
> > --srcdir=/home/users/tovrea/FFMPEG/gcc-4.4.0-RC-20090414/gcc
> > --disable-intermodule --enable-checking=yes,types --disable-coverage
> > --enable-languages=c
> > 
> > Using the line above manually results in correct construction of the gcc
> > directory.
> > 
> > Where is the configure command line generated?
> > Why would it be truncated in the gcc directory (and not in the intl
> > directory)?

> > make[3]: Entering directory
> > `/home/users/tovrea/FFMPEG/gcc-4.4.0-objdir-sgi6/gcc'
> > make[3]: *** No rule to make target `all'.  Stop.
> > make[3]: Leaving directory
> > `/home/users/tovrea/FFMPEG/gcc-4.4.0-objdir-sgi6/gcc'
> > 
> > There are some errors in config.log but I see the same errors in my
> > Solaris gcc directory, which built correctly.

The error must have happened at some point earlier.  Either the
gcc/configure script was not called correctly by the toplevel machinery,
or inside the $objdir/gcc directory, the invocation of config.status
went wrong or so.  Can you show the build log that led up to this?
Was gcc/config.h generated?

Thanks,
Ralf



More information about the Gcc-help mailing list