From: Elena Zannoni <ezannoni@redhat.com>
To: Richard.Earnshaw@arm.com
Cc: Andrew Cagney <ac131313@ges.redhat.com>,
David Carlton <carlton@math.stanford.edu>,
gdb-patches@sources.redhat.com
Subject: Re: [RFA] convert blocks to dictionaries, phase 1, main part
Date: Thu, 19 Sep 2002 06:18:00 -0000 [thread overview]
Message-ID: <15753.52768.684592.910377@localhost.redhat.com> (raw)
In-Reply-To: <200209191014.g8JAE8B23011@pc960.cambridge.arm.com>
Richard Earnshaw writes:
> > >> There is some sed in MAINTAINERS for generating
> > >> the target list. Richard E, I believe, posted a script for doing all
> > >> the config's and builds.
> > >
> > >
> > > Maybe we should have a contrib directory where things like this are placed.
> >
> > There is src/contrib but who knows who is responsible for that.
> > src/gdb/contrib or src/gdb/scripts? I'm personally ok with
> > gdb/gdb_<scriptname=mbuild?>.sh
>
> gdb/gdb_mbuild.sh it is then.
>
> Installed. I've tweaked my original slightly so that it takes arguments
> rather than requiring tweaking for your local environment.
>
> New syntax is
>
> gdb/gdb_mbuild.sh <srcdir> <builddir> [<par_jobs>]
>
> Where par_jobs is an optional number of parallel jobs to run (defaults to
> 1)
>
> R.
Should we document these scripts somewhere? Maybe a README file of some
sort? Or would it be more appropriate to have a chapter/section in
the internal manual?
Elena
next prev parent reply other threads:[~2002-09-19 13:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 15:26 David Carlton
2002-09-16 15:30 ` David Carlton
2002-09-17 7:35 ` Daniel Jacobowitz
2002-09-17 9:03 ` Andrew Cagney
2002-09-17 10:43 ` David Carlton
2002-09-17 10:49 ` Daniel Jacobowitz
2002-09-17 11:34 ` David Carlton
2002-09-17 12:24 ` Andrew Cagney
2002-09-17 11:44 ` Andrew Cagney
2002-09-17 12:30 ` Daniel Jacobowitz
2002-09-17 12:49 ` Andrew Cagney
2002-09-17 13:32 ` Daniel Jacobowitz
2002-09-17 21:48 ` Daniel Berlin
2002-09-18 7:26 ` Andrew Cagney
2002-09-20 9:13 ` Jim Blandy
2002-09-17 12:59 ` Daniel Berlin
2002-09-17 13:13 ` Andrew Cagney
2002-09-17 9:29 ` Andrew Cagney
2002-09-17 11:04 ` David Carlton
2002-09-17 12:16 ` Andrew Cagney
2002-09-17 12:35 ` Daniel Jacobowitz
2002-09-17 12:46 ` David Carlton
2002-09-17 12:57 ` Andrew Cagney
2002-09-22 14:51 ` Jim Blandy
2002-09-17 12:54 ` Michael Snyder
2002-09-17 12:59 ` Daniel Berlin
2002-09-18 2:56 ` Richard Earnshaw
2002-09-18 14:07 ` Andrew Cagney
2002-09-19 3:14 ` Richard Earnshaw
2002-09-19 6:18 ` Elena Zannoni [this message]
2002-09-19 7:52 ` Richard Earnshaw
2002-09-19 7:51 ` Andrew Cagney
2002-09-22 14:41 ` Jim Blandy
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=15753.52768.684592.910377@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=Richard.Earnshaw@arm.com \
--cc=ac131313@ges.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