public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "giovannibajo at libero dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/13334] Bootstrap failure: libiberty/fibheap.c: LONG_MIN undeclared
Date: Sun, 07 Dec 2003 01:36:00 -0000 [thread overview]
Message-ID: <20031207013627.17225.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031206135657.13334.giovannibajo@libero.it>
------- Additional Comments From giovannibajo at libero dot it 2003-12-07 01:36 -------
It turned out to be a problem with non-standard CFLAGS/CXXFLAGS set.
I think the website (http://gcc.gnu.org/install/build.html) does not document
properly that CFLAGS/CXXFLAGS are used for bootstrap of target components
(libiberty, v3, libjava, etc.). I think it should be updated to include
something like:
"Notice that CFLAGS and CXXFLAGS are used during the last part of GCC bootstrap
(for target libraries like libjava or libstdc++). If bootstrap fails at that
point, you might try to remove those variables from your environment and try
again. In this case, remove your builddir and restart from scratch."
The last sentence has been added because I tried a 'make cleanstrap' after
having removed the flags and it was not sufficient (the makefiles were already
generated probably). Maybe there is a better and faster to accomplish this.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Component|c++ |web
Ever Confirmed| |1
Last reconfirmed|0000-00-00 00:00:00 |2003-12-07 01:36:27
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13334
next prev parent reply other threads:[~2003-12-07 1:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-06 13:57 [Bug c++/13334] New: " giovannibajo at libero dot it
2003-12-06 13:57 ` [Bug c++/13334] " giovannibajo at libero dot it
2003-12-06 13:59 ` giovannibajo at libero dot it
2003-12-06 21:17 ` pinskia at gcc dot gnu dot org
2003-12-07 1:36 ` giovannibajo at libero dot it [this message]
2003-12-07 1:44 ` [Bug bootstrap/13334] " pinskia at gcc dot gnu dot org
2003-12-07 1:55 ` pinskia at gcc dot gnu dot org
2004-01-29 21:37 ` meapague at hotmail dot com
2004-02-19 12:01 ` giovannibajo at libero dot it
2004-05-28 22:58 ` pinskia at gcc dot gnu dot org
2004-06-18 16:19 ` giovannibajo at libero dot it
2004-06-20 15:11 ` gerald at pfeifer dot com
2004-06-26 20:40 ` cvs-commit at gcc dot gnu dot org
2004-06-26 20:42 ` pinskia at gcc dot gnu dot org
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=20031207013627.17225.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).