public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aaronavay62 at aaronwl dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/17832] [4.0 Regression] Bootstrap broken by fixincludes failures
Date: Tue, 26 Oct 2004 21:51:00 -0000 [thread overview]
Message-ID: <20041026215143.8748.qmail@sourceware.org> (raw)
In-Reply-To: <20041005021813.17832.aaronavay62@aaronwl.com>
------- Additional Comments From aaronavay62 at aaronwl dot com 2004-10-26 21:51 -------
Sorry, I missed putting the PR tag in the commit log. However, no, this bug
really should not be closed yet. That patch just disabled building fixincludes.
The real patch that needs to be committed is in #8, which will make fixincludes
build appropriately when its needed, such as in *-mingw32's case, when
crosscompiling. It needs to be reviewed by Bruce Korb, I think.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17832
next prev parent reply other threads:[~2004-10-26 21:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 2:18 [Bug bootstrap/17832] New: " aaronavay62 at aaronwl dot com
2004-10-05 2:19 ` [Bug bootstrap/17832] " aaronavay62 at aaronwl dot com
2004-10-05 2:24 ` pinskia at gcc dot gnu dot org
2004-10-05 2:46 ` aaronavay62 at aaronwl dot com
2004-10-14 8:16 ` bonzini at gcc dot gnu dot org
2004-10-14 8:58 ` bonzini at gcc dot gnu dot org
2004-10-14 9:17 ` aaronavay62 at aaronwl dot com
2004-10-14 16:21 ` ericw at evcohs dot com
2004-10-20 8:21 ` cvs-commit at gcc dot gnu dot org
2004-10-20 8:39 ` aaronavay62 at aaronwl dot com
2004-10-21 9:52 ` bonzini at gcc dot gnu dot org
2004-10-21 21:28 ` aaronavay62 at aaronwl dot com
2004-10-22 5:18 ` aaronavay62 at aaronwl dot com
2004-10-22 5:21 ` aaronavay62 at aaronwl dot com
2004-10-26 21:40 ` pinskia at gcc dot gnu dot org
2004-10-26 21:51 ` aaronavay62 at aaronwl dot com [this message]
2004-10-27 14:44 ` bonzini at gcc dot gnu dot org
2004-10-27 20:14 ` cvs-commit at gcc dot gnu dot org
2004-10-27 20:18 ` aaronavay62 at aaronwl dot com
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=20041026215143.8748.qmail@sourceware.org \
--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).