From: "J.M.W. Kooijman" <jkooijman@comcast.net>
To: gcc@gcc.gnu.org
Subject: successful build gcc-3.4.0 on Red Hat 7.1.2.96-81
Date: Wed, 28 Apr 2004 16:20:00 -0000 [thread overview]
Message-ID: <408FBF32.5010902@comcast.net> (raw)
[-- 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 --]
next reply other threads:[~2004-04-28 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 16:20 J.M.W. Kooijman [this message]
2004-04-29 23:38 ` Jim Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=408FBF32.5010902@comcast.net \
--to=jkooijman@comcast.net \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).