From: Richard Earnshaw <rearnsha@arm.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com,
Richard Earnshaw <rearnsha@arm.com>,
David Carlton <carlton@math.stanford.edu>
Subject: Re: revamped gdb_mbuild.sh
Date: Wed, 27 Nov 2002 09:51:00 -0000 [thread overview]
Message-ID: <200211271750.gARHox401110@pc960.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Wed, 27 Nov 2002 12:41:07 EST." <3DE503B3.7040302@redhat.com>
> PS: Something I forgot to mention.
>
> 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).
>
> Anyway, the significant thing here is that the file contains the output
> from the TARGET's ``(gdb) maint print architecture'' command. Having
> that output for each architectures available [suddenly] makes it
> possible to examine/compare all the settings and, consequently, change
> those settings to something more logical.
>
> enjoy,
> Andrew
>
What happens to the build logs? Do we keep those?
R.
next prev parent reply other threads:[~2002-11-27 17:51 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 [this message]
2002-11-27 10:05 ` Andrew Cagney
2002-11-27 10:21 ` David Carlton
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=200211271750.gARHox401110@pc960.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=ac131313@redhat.com \
--cc=carlton@math.stanford.edu \
--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