From: Pedro Alves <palves@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Display configuration details in --help
Date: Thu, 21 Mar 2013 18:25:00 -0000 [thread overview]
Message-ID: <514B4AC3.1090103@redhat.com> (raw)
In-Reply-To: <CADPb22R4o4gkQk8oeqGvmWZerVf7gdkw8XOKz9mYxD6ubFPRig@mail.gmail.com>
On 03/21/2013 05:54 PM, Doug Evans wrote:
> Hi. I like the idea, but the implementation imposes a future
> maintenance burden.
> Would it be sufficient to just store the original string somewhere and
> print that?
> I believe that's what gcc does (at least it's configure.ac that
> computes a string and saves that in a global, and gcc just prints that
> global, instead of a series of #if/#ifdefs).
Speaking of gcc, gcc also doesn't put it in --help, but rather in -v.
While I like the idea too, it looks to me that this
>> This GDB is configured as follows:
>> configure --host=i686-pc-mingw32 --target=i686-pc-mingw32
>> --with-auto-load-dir=$debugdir:$datadir/auto-load
>> --with-auto-load-safe-path=$debugdir:$datadir/auto-load
>> --with-expat
>> --with-gdb-datadir=d:/usr/share/gdb (relocatable)
>> --with-jit-reader-dir=d:/usr/lib/gdb (relocatable)
>> --without-libunwind-ia64
>> --with-lzma
>> --with-python=d:/usr/Python26 (relocatable)
>> --with-separate-debug-dir=d:/usr/lib/debug (relocatable)
>> --with-system-gdbinit=d:/usr/etc/gdbinit (relocatable)
>> --with-zlib
>>
>>
is a significant amount of clutter for gdb's --help.
What do you think about putting this elsewhere? "gdb --configuration"
or some such, perhaps?
--
Pedro Alves
next prev parent reply other threads:[~2013-03-21 18:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 17:46 Eli Zaretskii
2013-03-21 18:00 ` Doug Evans
2013-03-21 18:25 ` Pedro Alves [this message]
2013-03-21 18:29 ` Joel Brobecker
2013-03-21 18:44 ` Eli Zaretskii
2013-03-21 19:11 ` Joel Brobecker
2013-03-21 20:39 ` Eli Zaretskii
2013-03-21 20:55 ` Joel Brobecker
2013-03-21 21:17 ` Tom Tromey
2013-03-21 22:23 ` Eli Zaretskii
2013-04-09 19:31 ` Eli Zaretskii
2013-04-09 19:46 ` Doug Evans
2013-04-09 20:04 ` Eli Zaretskii
2013-04-09 23:33 ` Doug Evans
2013-04-10 0:12 ` Pedro Alves
2013-04-10 0:48 ` Eli Zaretskii
2013-04-10 2:51 ` Doug Evans
2013-04-10 4:41 ` Eli Zaretskii
2013-04-11 2:41 ` Doug Evans
2013-04-11 1:20 ` Tom Tromey
2013-04-11 1:24 ` Pedro Alves
2013-04-11 2:43 ` Tom Tromey
2013-04-12 12:50 ` Eli Zaretskii
2013-04-12 14:43 ` Eli Zaretskii
2013-04-12 16:39 ` regroup --help text (was: Re: [PATCH] Display configuration details in --help) Pedro Alves
2013-06-22 11:31 ` regroup --help text " Eli Zaretskii
2013-06-25 19:30 ` Pedro Alves
2013-07-06 7:35 ` Eli Zaretskii
2013-04-12 20:50 ` [PATCH] Display configuration details in --help Tom Tromey
2013-04-14 14:17 ` Joel Brobecker
2013-04-16 1:34 ` Doug Evans
2013-04-16 9:46 ` regroup --help text Eli Zaretskii
2013-04-17 8:10 ` Doug Evans
2013-04-17 12:28 ` Eli Zaretskii
2013-04-14 14:16 ` [PATCH] Display configuration details in --help Doug Evans
2013-04-10 0:38 ` Eli Zaretskii
2013-04-10 3:06 ` Doug Evans
2013-04-10 4:44 ` Eli Zaretskii
2013-03-21 18:53 ` 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=514B4AC3.1090103@redhat.com \
--to=palves@redhat.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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