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: Doug Evans <dje at google dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: Eli Zaretskii <eliz at gnu dot org>, gdb-patches <gdb-patches at sourceware dot org>
- Date: Tue, 16 Apr 2013 17:55:53 -0700
- 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> <516DEDAD dot 8070902 at codesourcery dot com>
On Tue, Apr 16, 2013 at 5:32 PM, Yao Qi <yao@codesourcery.com> wrote:
> On 04/17/2013 04:36 AM, Doug Evans wrote:
>>
>> 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?
>
>
> When we cross compile GDB (build native arm-linux GDB on i686-pc-linux, for
> example), the location of libexpat or libbabeltrace on configuration time
> (on host) would be different with the location on run-time (on target). I
> am afraid it is not useful to print where libexpat or libbabeltrace were
> found in the configure and build step.
nit: For a canadian cross, s/(on host)/(on build)/ and s/(on target)/(on host)/.
It's certainly less useful, but since we're going down this path I
wanted to at least raise the question.
GCC prints this info.
Also, I wonder if we shouild print prefix and/or exec_prefix.
We print "(relocatable)" for relocatable directories but I'm left
guessing what the root of the relocatable tree is.
[We also don't explain what "relocatable" means AFAICS. I know, but I
can imagine a user wondering.]