public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "davek at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/40984] Build failure in oscons stage not detected.
Date: Sat, 03 Oct 2009 12:23:00 -0000	[thread overview]
Message-ID: <20091003122324.22521.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40984-14373@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from davek at gcc dot gnu dot org  2009-10-03 12:23 -------
(In reply to comment #1)
> Wouldn't it be enough to replace ";" by "&&" between the various steps?
> 

Hello Sam, the problem with just doing that is that xoscons can fail but still
leave fragmentary output, and then next time you build make sees that the
output file exists and doesn't try rebuilding it.  Using && would cause make to
fail at the error, but we still need to guarantee the partial output file is
deleted, otherwise the next build will not try rebuilding the xoscons outputs
and will error some time later when it reuses the fragmentary output while
attempting to compile the runtime library.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40984


      parent reply	other threads:[~2009-10-03 12:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06 11:17 [Bug ada/40984] New: " davek at gcc dot gnu dot org
2009-10-03 11:33 ` [Bug ada/40984] " sam at gcc dot gnu dot org
2009-10-03 12:23 ` davek at gcc dot gnu dot org [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=20091003122324.22521.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).