successful build gcc-3.4.0 on Red Hat 7.1.2.96-81

successful build gcc-3.4.0 on Red Hat 7.1.2.96-81

[J.M.W. Kooijman]

[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]

Successful build of Gcc-3.4.0 on April 27, 2004
config.guess output: i686-pc-linux-gnu
gcc version 2.96 20000731 (Red Hat Linux 7,1,2,96-81)
Full installation (used configure without parameters, so everything default)
kernel version: 2.4.2-2 (i686 unknown - but it is a Celeron)
glibc-2.2.2-10

used: make CFLAGS='-O' LIBCFLAGS='-g -O2' LIBCXXFLAGS='-g -O2 
-fno-implicit-templates' bootstrap 2> errlist
(errlist attached)
used: make -k check > checklist
(checklist attached) Unfortunately, I didn't catch the errors here, and 
there were several problems with the compilation of subtests. Sorry

General remark: Though the compilation went generally effortlessly, 
there was one slight hitch. In my first run configure had apparently 
decided that my system didn't have stdlib.h and therefore set 
HAVE_STDLIB_H to no. This caused a trip up at line 55 of 
libiberty/cplus-dem.c, where "include <stdlib.h>" was erroneously passed 
over for a redefinition of malloc in a deprecated way. After I commented 
the if-statement out, so that stdlib.h was included, everything went 
fine. I think this is a problem with the configure script, not the code.

Joe Kooijman

[-- Attachment #2: errlist --]
[-- Type: application/x-java-vm, Size: 39211 bytes --]

[-- Attachment #3: checklist --]
[-- Type: application/x-java-vm, Size: 36951 bytes --]

Re: successful build gcc-3.4.0 on Red Hat 7.1.2.96-81

[Jim Wilson]

J.M.W. Kooijman wrote:
> General remark: Though the compilation went generally effortlessly, 
> there was one slight hitch. In my first run configure had apparently 
> decided that my system didn't have stdlib.h and therefore set 
> HAVE_STDLIB_H to no.

Check the config.log file in the appropriate directory to see why the 
stdlib.h test failed.  This might be either libiberty or 
i686-pc-linux-gnu/libiberty depending on whether this was the host or 
target libiberty build.  There might be a conflict between stdlib.h and 
some other header file that shows up with a newer gcc.

Or, if you want us to look at this, file a bug report into our bugzilla 
bug database.  See
     http://gcc.gnu.org/bugs.html
for more info on reporting bugs.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com