Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: yao@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] print '--with{,out}-babeltrace' in 'gdb --configuration'
Date: Mon, 24 Jun 2013 19:03:00 -0000	[thread overview]
Message-ID: <834ncnjqmg.fsf@gnu.org> (raw)
In-Reply-To: <CADPb22T+_CC13O9PSR-STBTuCzbf7QE2BHXUPB=9KiFwDKGVvA@mail.gmail.com>

> Date: Mon, 24 Jun 2013 11:35:31 -0700
> From: Doug Evans <dje@google.com>
> Cc: Yao Qi <yao@codesourcery.com>, gdb-patches <gdb-patches@sourceware.org>
> 
> > 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.

I don't think it's a real danger.  One must invest a non-trivial
effort to have GDB configured without a single relocatable directory.

The requirement was to explain this succinctly.  If the above is not
deemed good enough, I'd rather not say anything at all.

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

I tried that, but found no good place to say that.  Just saying
something where --configuration is described will get this lost in the
humongous manual, and users will not necessarily know where to look.

Again, if the above is not good enough, let's forget about the whole
thing.


  reply	other threads:[~2013-06-24 18:44 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
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 [this message]
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=834ncnjqmg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dje@google.com \
    --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