This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] print '--with{,out}-babeltrace' in 'gdb --configuration'
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Doug Evans <dje at google dot com>
- Cc: yao at codesourcery dot com, gdb-patches at sourceware dot org
- Date: Wed, 17 Apr 2013 05:54:54 +0300
- Subject: Re: [PATCH] print '--with{,out}-babeltrace' in 'gdb --configuration'
- References: <1365761475-23845-1-git-send-email-yao at codesourcery dot com> <CADPb22RPtCiBOg8o6M1vKXJxGeDcTOriact4ujojygskBnrFFQ at mail dot gmail dot com> <83fvyr58c5 dot fsf at gnu dot org> <CADPb22R_D10GWjkpBMag2+kDXbzCrpxjmR8UF_AZ13J6tix84g at mail dot gmail dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Tue, 16 Apr 2013 13:36:54 -0700
> From: Doug Evans <dje@google.com>
> Cc: Yao Qi <yao@codesourcery.com>, gdb-patches <gdb-patches@sourceware.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 ...]
Sorry for my misunderstanding. In that case, it's probably a good
idea, if there are important things that we cannot catch otherwise.
> 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?
I'm not sure that place is of interest to anyone but the person who
configured GDB.