Re: gcc 4.7.2 fails to bootstrap in stage 1

[Ryan Johnson <ryan dot johnson at cs dot utoronto dot ca>]

On 21/11/2012 11:41 AM, Dennis Clarke wrote:
> ----- Original Message -----
> From: Eric Botcazou <ebotcazou@adacore.com>
> Date: Wednesday, November 21, 2012 3:07 am
> Subject: Re: gcc 4.7.2 fails to bootstrap in stage 1
> To: Dennis Clarke <dclarke@blastwave.org>
> Cc: gcc-help@gcc.gnu.org, ryan.johnson@cs.utoronto.ca, iant@google.com, jwakely.gcc@gmail.com
>
>
> > > Well I gave this a try :
> > >
> > > $ date
> > > Tue Nov 20 23:31:22 GMT 2012
> > > $
> > > $ gas --version
> > > GNU assembler (GNU Binutils) 2.23.1
> > > Copyright 2012 Free Software Foundation, Inc.
> > > This program is free software; you may redistribute it under the
> > terms of
> > > the GNU General Public License version 3 or later.
> > > This program has absolutely no warranty.
> > > This assembler was configured for a target of `sparc64-sun-solaris2.10'.
> > > $
> > > $ which ld
> > > /usr/ccs/bin/ld
> > > $
> > > $ CC='gcc -m64' CXX='g++ -m64' ../gcc-4.7.2/configure
> > > --build=sparc64-sun-solaris2.10 --prefix=/usr/local/gcc4 \
> > > > --with-gmp=/usr/local --with-mpfr=/usr/local --with-mpc=/usr/local
> > > > --disable-nls --enable-threads=posix \ --enable-shared
> > > > --libdir=/usr/local/gcc4/lib --with-local-prefix=/usr/local/gcc4
> > > > --without-gnu-ld \ --with-as=/usr/local/bin/gas
> > > > --with-ld=/usr/ccs/bin/ld \
> > > > --with-pkgversion=Blastwave.org\ Inc.\ Tue\ Nov\ 20\ 23\:31\:22\ GMT\
> > > > 2012 \ --enable-languages=c,c++,objc,fortran,ada --enable-bootstrap
> > > [..].
> > > That fails in the same way in the same place.
> > So what's the error in the end?  Your longish messages don't show it AFAICS.
> regardless this situation just keeps getting worse and worse.
>
> I can chose to use gas or as and either way the build fails in stage 1 either with
> a pile of noises about sed or with something even more interesting :
If it's complaining about sed, you've probably path issue (sed vs gsed) 
and messing with binutils won't help.

> .
> .
> .
>
> gmake[3]: Leaving directory `/usr/local/build/gcc-4.7.2_sparc64-sun-solaris2.10.003/gcc'
> mkdir sparc64-sun-solaris2.10/libgcc
> Checking multilib configuration for libgcc...
> Configuring stage 1 in sparc64-sun-solaris2.10/libgcc
> configure: creating cache ./config.cache
> checking build system type... sparc64-sun-solaris2.10
> checking host system type... sparc64-sun-solaris2.10
> checking for --enable-version-specific-runtime-libs... no
> checking for a BSD-compatible install... /usr/local/build/gcc-4.7.2/install-sh -c
> checking for gawk... gawk
> checking for sparc64-sun-solaris2.10-ar... ar
> checking for sparc64-sun-solaris2.10-lipo... lipo
> checking for sparc64-sun-solaris2.10-nm... /usr/local/build/gcc-4.7.2_sparc64-sun-solaris2.10.003/./gcc/nm
> checking for sparc64-sun-solaris2.10-ranlib... ranlib
> checking for sparc64-sun-solaris2.10-strip... strip
> checking whether ln -s works... yes
> checking for sparc64-sun-solaris2.10-gcc... /usr/local/build/gcc-4.7.2_sparc64-sun-solaris2.10.003/./gcc/xgcc -B/usr/local/build/gcc-4.7.2_sparc64-sun-solaris2.10.003/./gcc/ -B/usr/local/gcc4/sparc64-sun-solaris2.10/bin/ -B/usr/local/gcc4/sparc64-sun-solaris2.10/lib/ -isystem /usr/local/gcc4/sparc64-sun-solaris2.10/include -isystem /usr/local/gcc4/sparc64-sun-solaris2.10/sys-include
> checking for suffix of object files... configure: error: in `/usr/local/build/gcc-4.7.2_sparc64-sun-solaris2.10.003/sparc64-sun-solaris2.10/libgcc':
> configure: error: cannot compute suffix of object files: cannot compile
> See `config.log' for more details.
> gmake[2]: *** [configure-stage1-target-libgcc] Error 1
> gmake[2]: Leaving directory `/usr/local/build/gcc-4.7.2_sparc64-sun-solaris2.10.003'
> gmake[1]: *** [stage1-bubble] Error 2
> gmake[1]: Leaving directory `/usr/local/build/gcc-4.7.2_sparc64-sun-solaris2.10.003'
> gmake: *** [all] Error 2
>
> So I think the issue may be in the GNU stack that I have built, though I know not where.
You might try looking in config.log, which would contain the actual 
error message and could easily point to something mundane (like a broken 
sed or grep).

Ryan