From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: "Pierre Muller" <muller@ics.u-strasbg.fr>
Subject: Re: [RFA] testsuite: avoid compilation error on cygwin/mingw if -nostdlib option is used.
Date: Thu, 01 Oct 2009 23:29:00 -0000 [thread overview]
Message-ID: <200910020029.33291.pedro@codesourcery.com> (raw)
In-Reply-To: <001801ca42e7$94c15fe0$be441fa0$@u-strasbg.fr>
Seems reasonable. This is okay, with nits below.
On Thursday 01 October 2009 23:36:12, Pierre Muller wrote:
> + set add_unbuffered_object 1;
> + if {[lsearch -regexp $options ".*-nostdlib.*"] >= 0 } {
> + verbose "No set_unbuffered_mode for -nostdlib option";
> + set add_unbuffered_object 0;
> + }
The ';' are unnecessary. The '.*' are also unnecessary.
> if { $gdb_saved_set_unbuffered_mode_obj == "" } {
> verbose "compiling gdb_saved_set_unbuffered_obj"
> set unbuf_src ${srcdir}/lib/set_unbuffered_mode.c
> @@ -1824,7 +1881,9 @@ proc gdb_compile {source dest type optio
> # reverse link order. In that case, we can use ldflags to
> # avoid copying the object file to the host multiple
> # times.
> - lappend options "ldflags=$gdb_saved_set_unbuffered_mode_obj"
> + if { $add_unbuffered_object == 1 } {
Works too:
if { $add_unbuffered_object } {
Or, why not drop the extra variable, and just:
if {[lsearch -regexp $options "-nostdlib"] < 0 } {
lappend options "ldflags=$gdb_saved_set_unbuffered_mode_obj"
}
a suitable small comment would be nice too.
> + lappend options "ldflags=$gdb_saved_set_unbuffered_mode_obj"
> + }
> }
> }
--
Pedro Alves
next prev parent reply other threads:[~2009-10-01 23:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 22:36 Pierre Muller
2009-10-01 23:29 ` Pedro Alves [this message]
2009-10-02 7:15 ` [RFA-v2] " Pierre Muller
2009-10-02 16:58 ` Pedro Alves
2009-10-02 21:30 ` Pierre Muller
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=200910020029.33291.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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