From: Jim Wilson <wilson@specifixinc.com>
To: "J.M.W. Kooijman" <jkooijman@comcast.net>
Cc: gcc@gcc.gnu.org
Subject: Re: successful build gcc-3.4.0 on Red Hat 7.1.2.96-81
Date: Thu, 29 Apr 2004 23:38:00 -0000 [thread overview]
Message-ID: <4091880D.9000407@specifixinc.com> (raw)
In-Reply-To: <408FBF32.5010902@comcast.net>
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
prev parent reply other threads:[~2004-04-29 22:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 16:20 J.M.W. Kooijman
2004-04-29 23:38 ` Jim Wilson [this message]
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=4091880D.9000407@specifixinc.com \
--to=wilson@specifixinc.com \
--cc=gcc@gcc.gnu.org \
--cc=jkooijman@comcast.net \
/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).