Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Yao Qi <yao@codesourcery.com>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] print '--with{,out}-babeltrace' in 'gdb --configuration'
Date: Wed, 17 Apr 2013 07:40:00 -0000	[thread overview]
Message-ID: <CADPb22R_D10GWjkpBMag2+kDXbzCrpxjmR8UF_AZ13J6tix84g@mail.gmail.com> (raw)
In-Reply-To: <83fvyr58c5.fsf@gnu.org>

On Mon, Apr 15, 2013 at 10:54 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> [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.

The intent is that it would be a supplement, not a replacement.
[Apologies if that wasn't clear ...]

Note that the current code doesn't print *where* libexpat,etc. were found.
Do we want to take the step of adding that to config.in so it's
available to gdb to print?
[that's an honest question, not a rhetorical one]
Which gets back to my earlier question:
Do we care about printing --with-libbabeltrace-prefix?


  reply	other threads:[~2013-04-16 20:36 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
2013-04-17  7:40     ` Doug Evans [this message]
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=CADPb22R_D10GWjkpBMag2+kDXbzCrpxjmR8UF_AZ13J6tix84g@mail.gmail.com \
    --to=dje@google.com \
    --cc=eliz@gnu.org \
    --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