disappointing build problems with gcc 3.2.2 and 3.3 on i686-pc-linux-gnu :(

[John Sincock <jss at au dot mensa dot org>]

Hello again,

Ive worked out i did a silly thing trying to patch the gcc 3.2.2 tarfile 
with the 3.2.2-3.2.3 diff ... looks like i shouldve untarred it and run 
patch on the resulting directory... oops. So that explains why
i couldnt patch the 3.3.3 to give a 3.2.3 - but it doesnt explain why 
i had problems building 3.2.2 and 3.3 from official release tarballs.

And, a properly patched 3.2.3 gives the same failure as 3.2.2

---------------------------------
gcc 3.2.2 compiled with 3.0.4:
configured with --enable-shared --enable-threads 
make bootstrap

./xgcc -B./ -B/usr/local/gcc/gcc-3.2.3-20030518/i686-pc-linux-gnu/bin/ 
-isystem /usr/local/gcc/gcc-3.2.3-20030518/i686-pc-linux-gnu/include -isystem 
/usr/local/gcc/gcc-3.2.3-20030518/i686-pc-linux-gnu/sys-include -dumpspecs > 
tmp-specs
mv tmp-specs specs
echo "int xxy_us_dummy;" >tmp-dum.c
./xgcc -B./ -B/usr/local/gcc/gcc-3.2.3-20030518/i686-pc-linux-gnu/bin/ 
-isystem /usr/local/gcc/gcc-3.2.3-20030518/i686-pc-linux-gnu/include -isystem 
/usr/local/gcc/gcc-3.2.3-20030518/i686-pc-linux-gnu/sys-include -S tmp-dum.c
echo '/*WARNING: This file is automatically generated!*/' >tmp-under.c
if grep _xxy_us_dummy tmp-dum.s > /dev/null ; then \
  echo "int prepends_underscore = 1;" >>tmp-under.c; \
else \
  echo "int prepends_underscore = 0;" >>tmp-under.c; \
fi
/bin/sh /mnt/scsi/src/gcc-3.2.3/gcc/move-if-change tmp-under.c underscore.c
rm -f tmp-dum.c tmp-dum.s
echo timestamp > s-under
gcc -c -DIN_GCC    -g  -W -Wall -Wwrite-strings -Wstrict-prototypes 
-Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long  -DHAVE_CONFIG_H  
  -I. -I. -I/mnt/scsi/src/gcc-3.2.3/gcc -I/mnt/scsi/src/gcc-3.2.3/gcc/. 
-I/mnt/scsi/src/gcc-3.2.3/gcc/config -I/mnt/scsi/src/gcc-3.2.3/gcc/../include 
underscore.c -o underscore.o
gcc -DIN_GCC    -g  -W -Wall -Wwrite-strings -Wstrict-prototypes 
-Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long  -DHAVE_CONFIG_H  
-o Tcollect2 \
	collect2.o tlink.o hash.o intl.o underscore.o version.o   
../libiberty/libiberty.a 
/usr/bin/ld: cannot find -lgcc_eh
collect2: ld returned 1 exit status
make[2]: *** [collect2] Error 1
make[2]: Leaving directory `/mnt/scsi/src/configured/gcc-3.2.3/gcc'
make[1]: *** [stage1_build] Error 2
make[1]: Leaving directory `/mnt/scsi/src/configured/gcc-3.2.3/gcc'
make: *** [bootstrap] Error 2
--------------------------------------------------------------------------------



Further info re my system:
make-3.79.1-6mdk
binutils-2.11.92.0.12-6mdk

Also, I noticed this in http://gcc.gnu.org/install/build.html :
>Some commands executed when making the compiler may fail (return a nonzero 
>status) and be ignored by make. These failures, which are often due to files 
>that were not found, are expected, and can safely be ignored.

so ... perhaps i should be using make -k bootstrap... though im sure there
will still be severe problems if libgcc_eh isnt being built properly...


Also, I just noticed this from http://gcc.gnu.org/install/specific.html
----------------
*-*-linux-gnu

Versions of libstdc++-v3 starting with 3.2.1 require bugfixes present in 
glibc 2.2.5 and later. More information is available in the libstdc++-v3 
documentation.

If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install out-of-the-box. 
You'll get compile errors while building libstdc++. The patch 
glibc-2.2.patch, that is to be applied in the GCC source tree, fixes the 
compatibility problems.

Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync since 
the latest exception handling changes for GCC. Compiling glibc with GCC 3.0 
will give a binary incompatible glibc and therefore cause lots of problems 
and might make your system completely unusable. This will definitely need 
fixes in glibc but might also need fixes in GCC. We strongly advise to wait 
for glibc 2.2.4 and to read the release notes of glibc 2.2.4 whether patches 
for GCC 3.0 are needed. You can use glibc 2.2.3 with GCC 3.0, just do not try 
to recompile it.

i?86-*-linux*
You will need binutils 2.9.1.0.15 or newer for exception handling to work.
------------------------------------------------------------------------------------

I hope that binutils bit doesnt apply to my system.


And this, from http://gcc.gnu.org/ml/gcc/2003-04/msg00966.html
----------------
It took a total of 11hours start to finish to build this on a 
intel233mmx machine. 

gcc-3.2.2]$ ./config.guess: i586-pc-linux-gnu

 gcc-3.2.2]$ gcc -v: Reading specs from 
/usr/local/lib/gcc-lib/i586-pc-linux-gnu/3.2.2/specs
Configured with: ./configure 
Thread model: posix
gcc version 3.2.2

/etc/issue: Mandrake Linux release 8.2 (Bluebird) for i586
Kernel 2.4.18-6mdk on an i586

uname -a: Linux localhost.localdomain 2.4.18-6mdk #1 Fri Mar 15 
02:59:08 CET 2002 i586 unknown

gcc-3.2.2]$ rpm -q glibc: glibc-2.2.4-26.2mdk
--------------------------------------------------------------


That report contradicts the statement from
http://gcc.gnu.org/install/specific.html which says glibc 2.2.5 is required 
for gcc 3.2.1 or greater.

Does anyone think these problems might be due to my glibc-2.2.4-25mdk
-- when glibc-2.2.4-26.2mdk seems to work?

thanks again for any suggestions or help

John