public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rwild at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/42566] Bootstrap fails in stage3 building the libstdc++ PCH
Date: Sat, 15 Jan 2011 09:55:00 -0000 [thread overview]
Message-ID: <bug-42566-4-lXDoW7v32S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-42566-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42566
Ralf Wildenhues <rwild at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2011.01.15 07:07:08
Ever Confirmed|0 |1
--- Comment #11 from Ralf Wildenhues <rwild at gcc dot gnu.org> 2011-01-15 07:07:08 UTC ---
Setting state to WAITING, as this PR lacks feedback for this:
> This looks like <http://gcc.gnu.org/ml/gcc-patches/2009-12/msg00650.html>.
> To confirm, please throw away your build tree once, build, then proceed as
> described in above mail (adjusting $target etc).
next parent reply other threads:[~2011-01-15 7:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-42566-4@http.gcc.gnu.org/bugzilla/>
2011-01-15 9:55 ` rwild at gcc dot gnu.org [this message]
2011-03-14 2:18 ` 3dw4rd at verizon dot net
2011-03-14 9:18 ` fxcoudert at gcc dot gnu.org
2023-02-06 6:34 ` vital.had at gmail dot com
2023-03-03 21:59 ` egallager at gcc dot gnu.org
2009-12-31 15:35 [Bug bootstrap/42566] New: " 3dw4rd at verizon dot net
2010-01-01 10:27 ` [Bug bootstrap/42566] " fxcoudert at gcc dot gnu dot org
2010-01-01 15:15 ` 3dw4rd at verizon dot net
2010-01-02 20:03 ` fxcoudert at gcc dot gnu dot org
2010-01-02 20:32 ` 3dw4rd at verizon dot net
2010-01-02 20:34 ` 3dw4rd at verizon dot net
2010-01-02 20:37 ` 3dw4rd at verizon dot net
2010-01-02 20:38 ` 3dw4rd at verizon dot net
2010-01-02 20:48 ` fxcoudert at gcc dot gnu dot org
2010-01-02 21:10 ` 3dw4rd at verizon dot net
2010-01-04 13:18 ` rwild 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=bug-42566-4-lXDoW7v32S@http.gcc.gnu.org/bugzilla/ \
--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).