From: Eli Zaretskii <eliz@gnu.org>
To: Markus Deuling <deuling@de.ibm.com>
Cc: gdb-patches@sourceware.org, drow@false.org, uweigand@de.ibm.com,
muller@ics.u-strasbg.fr
Subject: Re: [Patch]: Build script gdb_buildall.sh
Date: Mon, 11 Feb 2008 20:01:00 -0000 [thread overview]
Message-ID: <uk5lbp8l4.fsf@gnu.org> (raw)
In-Reply-To: <47B00041.2030800@de.ibm.com> (message from Markus Deuling on Mon, 11 Feb 2008 08:58:57 +0100)
> Date: Mon, 11 Feb 2008 08:58:57 +0100
> From: Markus Deuling <deuling@de.ibm.com>
> CC: Eli Zaretskii <eliz@gnu.org>, Daniel Jacobowitz <drow@false.org>,
> Ulrich Weigand <uweigand@de.ibm.com>,
> Pierre Muller <muller@ics.u-strasbg.fr>
>
> this patch adds documentation to this patch: http://sourceware.org/ml/gdb-patches/2008-01/msg00671.html.
>
>
> ChangeLog:
>
>
> Add script to build and test GDB using enable-targets=all.
>
> * gdb_buildall.sh: New file.
>
>
>
> ChangeLog Doc:
>
> * gdbint.texinfo (Build Script): New section. Mention new build script
> gdb_buildall.sh.
>
>
> Eli, is the documentation ok? I added a section to "Hints" in gdbint.texinfo.
Yes, except for a few minor gotchas:
> +The script @code{gdb_buildall.sh} builds GDB with flag
gdb_buildall.sh is a file, so please use the @file markup, not @code.
> +@code{--enable-targets=all} set. This builds GDB with all supported targets
Options such as --enable-targets=all should have the @option markup.
> +activated. This helps testing GDB when doing changes that affect more than one
^^
Two spaces after a period that ends a sentence.
> +After building GDB the scripts checks which architectures are supported and
We use @value{GDBN} instead of a literal GDB, to allow changing the
name by editing a single line at the beginning of the manual.
Thanks.
next prev parent reply other threads:[~2008-02-11 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 8:01 Markus Deuling
2008-02-11 20:01 ` Eli Zaretskii [this message]
2008-02-12 6:02 ` Markus Deuling
2008-02-12 19:44 ` Eli Zaretskii
2008-02-12 19:45 ` Daniel Jacobowitz
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=uk5lbp8l4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=deuling@de.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
--cc=uweigand@de.ibm.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