From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: yao@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] print '--with{,out}-babeltrace' in 'gdb --configuration'
Date: Tue, 16 Apr 2013 10:11:00 -0000 [thread overview]
Message-ID: <83fvyr58c5.fsf@gnu.org> (raw)
In-Reply-To: <CADPb22RPtCiBOg8o6M1vKXJxGeDcTOriact4ujojygskBnrFFQ@mail.gmail.com>
> Date: Mon, 15 Apr 2013 11:50:51 -0700
> From: Doug Evans <dje@google.com>
> Cc: gdb-patches <gdb-patches@sourceware.org>
>
> Do we care about printing --with-libbabeltrace-prefix?
> I don't have a strong preference, but if we're going to go down this
> path I think we should.
Any configure-time option that is known to GDB at run time should be
included in the configuration description.
> [An alternative would be to punt on details at this level and instead
> record the complete string passed to configure and print that.]
That has its limitations, in that it only shows options explicitly
mentioned on the configure command line, omitting the options that
were automatically chosen by configure as result of probing the
system. E.g., --with-expat.
next prev parent reply other threads:[~2013-04-16 5:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 14:48 Yao Qi
2013-04-12 15:45 ` Eli Zaretskii
2013-04-17 11:02 ` Yao Qi
2013-04-16 1:56 ` Doug Evans
2013-04-16 10:11 ` Eli Zaretskii [this message]
2013-04-17 7:40 ` Doug Evans
2013-04-17 9:40 ` Yao Qi
2013-04-17 10:02 ` Doug Evans
2013-04-17 12:54 ` Yao Qi
2013-04-17 22:44 ` Eli Zaretskii
2013-04-18 4:32 ` Doug Evans
2013-06-22 20:03 ` Eli Zaretskii
2013-06-22 22:21 ` Sergio Durigan Junior
2013-06-23 2:21 ` Eli Zaretskii
2013-06-23 2:23 ` Sergio Durigan Junior
2013-06-24 18:43 ` Doug Evans
2013-06-24 19:03 ` Eli Zaretskii
2013-06-24 19:04 ` Doug Evans
2013-06-24 19:28 ` Eli Zaretskii
2013-06-24 19:33 ` Doug Evans
2013-07-06 7:36 ` Eli Zaretskii
2013-04-17 14:21 ` Eli Zaretskii
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=83fvyr58c5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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