public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/55083] failure while configuring libatomic is not cleaned up
Date: Sun, 09 Dec 2012 05:07:00 -0000 [thread overview]
Message-ID: <bug-55083-4-fsXvnivKmG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55083-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55083
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-12-09 05:06:54 UTC ---
(In reply to comment #4)
> I can't remember much about this. Things may have changed since I reported it.
Not in the toplevel Makefile or libatomic's configure.
>
> Is the Makefile created as the last step?
yes it is created after all of configure has finished.
> If not, then if something fails after the Makefile is created, then the next
> build will assume everything in that section completed successfully (which will
> be incorrect).
next prev parent reply other threads:[~2012-12-09 5:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 14:53 [Bug c/55083] New: " pedzsan at gmail dot com
2012-10-26 15:14 ` [Bug bootstrap/55083] " pinskia at gcc dot gnu.org
2012-10-26 15:31 ` pedzsan at gmail dot com
2012-12-09 2:24 ` pinskia at gcc dot gnu.org
2012-12-09 4:46 ` pedzsan at gmail dot com
2012-12-09 5:07 ` pinskia at gcc dot gnu.org [this message]
2012-12-09 5:40 ` pedzsan at gmail 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=bug-55083-4-fsXvnivKmG@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).