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

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

[Phil Edwards]

On Sun, May 18, 2003 at 11:46:36PM +0930, John Sincock wrote:
> 
> The point is though, that 2.2.4 does look ok, at least some versions of it
> anyway.

Modified versions might be.  The stock version is not.

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams

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

[John Sincock]

sorry,

the 2nd example of a glibc 2.2.4 build success which i gave in my last 
post, was a mis-paste.. as it actually used 2.2.93

I think this is the one i intended to paste in had:

Red Hat Linux release 7.2
Linux 2.4.18-17.7.x #1 Tue Oct 8 13:33:14 EDT 2002 i686 unknown
glibc-2.2.4-31

The point is though, that 2.2.4 does look ok, at least some versions of it
anyway.

John

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

[John Sincock]

sorry,

the 2nd example of a glibc 2.2.4 build success which i gave in my last 
post, was a mis-paste.. as it actually used 2.2.93

I think this is the one i intended to paste in had:

Red Hat Linux release 7.2
Linux 2.4.18-17.7.x #1 Tue Oct 8 13:33:14 EDT 2002 i686 unknown
glibc-2.2.4-31

The point is though, that 2.2.4 does look ok, at least some versions of it
anyway.

John

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

[John Sincock]

Hi Phil,

thanks for your response

On Sunday 18 May 2003 12:17 pm, you wrote:
> > 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.
> You have 2.11.  2.11 is newer than 2.9.  You should be fine there.

Ah thanks, sorry, i read the 2.9.1 as 2.91, so it thought my 2.11 
might be out of date.

> >  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
>
> Reread the install instructions, where we strongly recommend building in
> a different directory than the source dir.

I have been building in different dir than source dir. That snippet was from
someone elses build... I pasted in that section to show that someone 
else with mandrake 8.2 has somehow managed to compile 3.2.2. Sorry 
re confusion there.

> > 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.
> You need it for C++ at the very least.

This confuses me a bit.. :(

I did read:  http://gcc.gnu.org/install/specific.html#*-*-linux-gnu
Where it says:
>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

BUT!!! If you look at the list of successful builds at:
http://gcc.gnu.org/gcc-3.2/buildstat.html
There are a variety of successful builds with glibc 2.2.4
The test reports also show that they have built g++, and it
has passed almost all tests, with only a few unexpected failures.

eg these builds of 3.2.2 were ok
-------------------------------------------------------------------
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
-----------------------------------------------------------------
...Reading specs from    
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2.2/specs
Configured with: ./configure
Thread model: posix
gcc version 3.2.2
3. RedHat 8.0 
4. uname -a 
Linux 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686
i686 i386 GNU/Linux
5. rpm -q glibc
glibc-2.2.93-5
--------------------------------------------------------------------

And there were quite a few others.  I havent found any successful 
builds with the exact same version of glibc as me though - which 
is glibc-2.2.4-25mdk

I think I am about to give up trying to compile a new gcc for now. 
Though i will have another try sometime soon, when i have upgraded 
my glibc to 2.2.5 or so. I dont think i have enough enthusiasm to do 
that this weekend.

I think ive found a few 3.2 rpms, which should install on my system as 
well, so I may just install them next weekend, and then have another go 
at compiing 3.3 with that, just to see how i go.

Arrrghhh defeated by a simple compile of gcc!! Nothing else, in gigabytes
of software compiled, has managed to humiliate me to this extent!!

Enlightenment 0.17 has probably come close... but at least i can blame 
a failure to compile that mess on their demented software.... with gcc,
i think i will have to assume that I have messed up my system in some 
way, or my different versions of gcc are getting in each others way,
or something.

Oh well, 

and thanks again,

John

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

[John Sincock]

Hi Phil,

thanks for your response

On Sunday 18 May 2003 12:17 pm, you wrote:
> > 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.
> You have 2.11.  2.11 is newer than 2.9.  You should be fine there.

Ah thanks, sorry, i read the 2.9.1 as 2.91, so it thought my 2.11 
might be out of date.

> >  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
>
> Reread the install instructions, where we strongly recommend building in
> a different directory than the source dir.

I have been building in different dir than source dir. That snippet was from
someone elses build... I pasted in that section to show that someone 
else with mandrake 8.2 has somehow managed to compile 3.2.2. Sorry 
re confusion there.

> > 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.
> You need it for C++ at the very least.

This confuses me a bit.. :(

I did read:  http://gcc.gnu.org/install/specific.html#*-*-linux-gnu
Where it says:
>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

BUT!!! If you look at the list of successful builds at:
http://gcc.gnu.org/gcc-3.2/buildstat.html
There are a variety of successful builds with glibc 2.2.4
The test reports also show that they have built g++, and it
has passed almost all tests, with only a few unexpected failures.

eg these builds of 3.2.2 were ok
-------------------------------------------------------------------
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
-----------------------------------------------------------------
...Reading specs from    
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2.2/specs
Configured with: ./configure
Thread model: posix
gcc version 3.2.2
3. RedHat 8.0 
4. uname -a 
Linux 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686
i686 i386 GNU/Linux
5. rpm -q glibc
glibc-2.2.93-5
--------------------------------------------------------------------

And there were quite a few others.  I havent found any successful 
builds with the exact same version of glibc as me though - which 
is glibc-2.2.4-25mdk

I think I am about to give up trying to compile a new gcc for now. 
Though i will have another try sometime soon, when i have upgraded 
my glibc to 2.2.5 or so. I dont think i have enough enthusiasm to do 
that this weekend.

I think ive found a few 3.2 rpms, which should install on my system as 
well, so I may just install them next weekend, and then have another go 
at compiing 3.3 with that, just to see how i go.

Arrrghhh defeated by a simple compile of gcc!! Nothing else, in gigabytes
of software compiled, has managed to humiliate me to this extent!!

Enlightenment 0.17 has probably come close... but at least i can blame 
a failure to compile that mess on their demented software.... with gcc,
i think i will have to assume that I have messed up my system in some 
way, or my different versions of gcc are getting in each others way,
or something.

Oh well, 

and thanks again,

John

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

[Phil Edwards]

On Sun, May 18, 2003 at 03:08:03AM +0930, John Sincock wrote:
> 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...

No.  Only use -k with make check.


> 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.

You have 2.11.  2.11 is newer than 2.9.  You should be fine there.


>  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

Reread the install instructions, where we strongly recommend building in
a different directory than the source dir.


> 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.

You need it for C++ at the very least.

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams

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

[John Sincock]

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

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

[John Sincock]

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