From: David Carlton <carlton@math.stanford.edu>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Richard.Earnshaw@arm.com, gdb-patches@sources.redhat.com
Subject: Re: revamped gdb_mbuild.sh
Date: Wed, 27 Nov 2002 10:21:00 -0000 [thread overview]
Message-ID: <ro1wumy6fi6.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <3DE5096F.3080906@redhat.com>
On Wed, 27 Nov 2002 13:05:35 -0500, Andrew Cagney <ac131313@redhat.com> said:
>>> The new script, once it has successfully configured, built, and run
>>> a target, replaces the BUILDDIR/TARGET directory with a
>>> BUILDDIR/TARGET file (-f removes this, this is how the script knows
>>> to not try to re-do a build).
> At present both build and config logs, and the build directory get
> removed. Only architecture output is left.
> I think this is ok since, unlike before, the command is restartable.
> If the build fails, just restart it with a more verbose option.
Just checking: if the build fails, the logs aren't removed, right?
That's what you seem to be saying above, and that seems to be what the
script does if I'm reading it correctly, but given that I'm not sure I
understand your last paragraph.
Certainly I think it would be bad if the logs were deleted if the
build fails, but I don't mind if they're deleted if the build
succeeds.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2002-11-27 18:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 10:51 Andrew Cagney
2002-11-26 1:53 ` Richard Earnshaw
2002-11-26 7:11 ` Andrew Cagney
2002-11-26 7:41 ` Richard Earnshaw
2002-11-26 7:50 ` Andrew Cagney
2002-11-26 9:30 ` Richard Earnshaw
2002-11-26 10:53 ` Andrew Cagney
2002-11-26 11:15 ` Richard Earnshaw
2002-11-27 8:30 ` Andrew Cagney
2002-11-27 9:41 ` Andrew Cagney
2002-11-27 9:51 ` Richard Earnshaw
2002-11-27 10:05 ` Andrew Cagney
2002-11-27 10:21 ` David Carlton [this message]
2002-11-27 10:37 ` Andrew Cagney
2002-11-27 9:49 ` Richard Earnshaw
2002-11-26 8:50 ` David Carlton
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=ro1wumy6fi6.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=Richard.Earnshaw@arm.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/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