Re: Bootstrap failure 2.95.3-test2 for i686-pc-linux-gnu

[Andris Pavenis <pavenis at latnet dot lv>]

I saw this in last 2 months when tried to build current CVS version
of gcc-2.95 branch (targets i[56]86-pc-linux-gnu and i586-pc-msdosdjgpp). I 
used simply 'cvs update ...' but not the script contrib/egcs_update (why it's 
still named so, but not as gcc_update as in HEAD branch?).

I think it shouldn't matter if I have all needed tools. The same approach
(simply 'cvs update ...' and after that configuring and 'make bootstrap') 
works OK for head branch. 

So I guess something is broken with gcc-2.95 branch. 

As far as I tested gcc-2.95.3-test[12].tar.gz was OK

Andris


On Thursday 18 January 2001 23:36, jlw@sco.com wrote:
> Having built the 2.95.2-release earlier this week on a Caldera eDesktop 2.4
> system, I downloaded the gcc 2.95.3-test2 CVS tree this morning.
>
> The bootstrap failed building libobjc with the following error:
>
>
> Configuring in i686-pc-linux-gnu/libobjc
> creating cache ./config.cache
> checking if compiler cc1obj has been built... yes
> checking for gcc... /home/jlw/GNUTools/BUILD/gcc-2.95.3/gcc/xgcc
> -B/home/jlw/GNUTools/BUILD/gcc-2.95.3/gcc/
> -B/usr/local/i686-pc-linux-gnu/bin/ checking whether the C compiler
> (/home/jlw/GNUTools/BUILD/gcc-2.95.3/gcc/xgcc
> -B/home/jlw/GNUTools/BUILD/gcc-2.95.3/gcc/
> -B/usr/local/i686-pc-linux-gnu/bin/ -g -O2 ) works... yes checking whether
> the C compiler (/home/jlw/GNUTools/BUILD/gcc-2.95.3/gcc/xgcc
> -B/home/jlw/GNUTools/BUILD/gcc-2.95.3/gcc/
> -B/usr/local/i686-pc-linux-gnu/bin/ -g -O2 ) is a cross-compiler... no
> checking whether we are using GNU C... yes
> checking whether /home/jlw/GNUTools/BUILD/gcc-2.95.3/gcc/xgcc
> -B/home/jlw/GNUTools/BUILD/gcc-2.95.3/gcc/
> -B/usr/local/i686-pc-linux-gnu/bin/ accepts -g... yes checking for a BSD
> compatible install... /bin/sh /home/jlw/GNUTools/SRC/gcc-2.95.3/install-sh
> -c checking how to run the C preprocessor...
> /home/jlw/GNUTools/BUILD/gcc-2.95.3/gcc/xgcc
> -B/home/jlw/GNUTools/BUILD/gcc-2.95.3/gcc/
> -B/usr/local/i686-pc-linux-gnu/bin/ -E checking for stdio.h... yes
> checking for ANSI C header files... yes
> checking for thread file... single
> updating cache ./config.cache
> creating ./config.status
> creating Makefile
> Adding multilib support to Makefile in ../../../../SRC/gcc-2.95.3/libobjc
> multidirs=
> with_multisubdir=
> make[2]: Entering directory
> `/home/jlw/GNUTools/BUILD/gcc-2.95.3/i686-pc-linux-gnu/libobjc'
>
>  ....
>
> /home/jlw/GNUTools/BUILD/gcc-2.95.3/gcc/xgcc
> -B/home/jlw/GNUTools/BUILD/gcc-2.95.3/gcc/
> -B/usr/local/i686-pc-linux-gnu/bin/ -c -I.
> -I../../../../SRC/gcc-2.95.3/libobjc   -g -O2 -DIN_GCC
> -I../../../../SRC/gcc-2.95.3/libobjc/objc 
> -I../../../../SRC/gcc-2.95.3/libobjc/../gcc
> -I../../../../SRC/gcc-2.95.3/libobjc/../gcc/config -I../../gcc
> -I../../../../SRC/gcc-2.95.3/libobjc/../include
> ../../../../SRC/gcc-2.95.3/libobjc/init.c
> /home/jlw/GNUTools/BUILD/gcc-2.95.3/gcc/xgcc
> -B/home/jlw/GNUTools/BUILD/gcc-2.95.3/gcc/
> -B/usr/local/i686-pc-linux-gnu/bin/ -fgnu-runtime -c -o linking.o -I.
> -I../../../../SRC/gcc-2.95.3/libobjc   -g -O2 -DIN_GCC
> -I../../../../SRC/gcc-2.95.3/libobjc/objc 
> -I../../../../SRC/gcc-2.95.3/libobjc/../gcc
> -I../../../../SRC/gcc-2.95.3/libobjc/../gcc/config -I../../gcc
> -I../../../../SRC/gcc-2.95.3/libobjc/../include
> ../../../../SRC/gcc-2.95.3/libobjc/linking.m In file included from
> ../../../../SRC/gcc-2.95.3/libobjc/objc/Object.h:30, from
> ../../../../SRC/gcc-2.95.3/libobjc/linking.m:28:
> ../../../../SRC/gcc-2.95.3/libobjc/objc/objc.h:51: parse error before
> `const' xgcc: Internal compiler error: program cc1obj got fatal signal 11
> make[2]: *** [linking.o] Error 1
> make[2]: Leaving directory
> `/home/jlw/GNUTools/BUILD/gcc-2.95.3/i686-pc-linux-gnu/libobjc' make[1]:
> *** [all-target-libobjc] Error 2
> make[1]: Leaving directory `/home/jlw/GNUTools/BUILD/gcc-2.95.3'
> make: *** [bootstrap] Error 2
>
>
> Not seeing any x86 Linux testresults since 2.95.3-test2 became available,
> I was wondering if anyone else has seen the problem?
>
> I am attempting to drop back to the 2.95.3-test1 branch to see if the
> problem occurs there, although I do not anticipate any problems since
> some 2.95.3 testresults have come in earlier.  At the present time
> I am having trouble contacting gcc.gnu.org
>
> As additional information, I have built 2.95.3-test2 on a UnixWare 7.1.1
> system with the native C compiler (UDK FS 7.1.1b)
>
>
> John Wolfe			SCO, Inc.		jlw@sco.com