This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] print '--with{,out}-babeltrace' in 'gdb --configuration'


On Sat, Jun 22, 2013 at 4:31 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Wed, 17 Apr 2013 10:25:23 -0700
>> From: Doug Evans <dje@google.com>
>> Cc: Yao Qi <yao@codesourcery.com>, gdb-patches <gdb-patches@sourceware.org>
>>
>> On Wed, Apr 17, 2013 at 10:01 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> >> Date: Wed, 17 Apr 2013 10:54:10 +0800
>> >> From: Yao Qi <yao@codesourcery.com>
>> >> CC: Eli Zaretskii <eliz@gnu.org>, gdb-patches <gdb-patches@sourceware.org>
>> >>
>> >> The "relocatable" is unclear to me unless I checked configure.ac and
>> >> previous discussions.
>> >
>> > I will add something to explain that, assuming I will find a way to
>> > say that concisely.
>>
>> [for completeness sake]
>> I'd be ok with just adding something to the manual.
>> It would be good to document the fact that a gdb install tree can be
>> moved and gdb will still find its relocatable ancillary files.
>> This goes along with the ability to do "make install DESTDIR=/foo"
>> which is a nice capability.
>
> Is the below OK?
>
> Index: gdb/top.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/top.c,v
> retrieving revision 1.236
> diff -u -p -r1.236 top.c
> --- gdb/top.c   30 May 2013 17:27:44 -0000      1.236
> +++ gdb/top.c   22 Jun 2013 11:30:47 -0000
> @@ -1252,6 +1252,9 @@ This GDB was configured as follows:\n\
>               --without-babeltrace\n\
>  "));
>  #endif
> +    fprintf_filtered (stream, _("\n\
> + (\"Relocatable\" means directory can be moved with the GDB installation tree.)\n\
> +"));
>  }

If you want to print something here, then I think you need to take
into account whether "relocatable" is printed at all.
There are lots of places where it may be printed, and each is
conditioned by a macro like FOO_RELOCATABLE.
Taking into account all those macros (and having to maintain the
result over time) seems problematic.

How about just a sentence or two in the manual near the description of
--configuration (or some such).


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]