Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: dje@google.com (Doug Evans)
Cc: gdb-patches@sourceware.org
Subject: Re: [doc RFA]: New option --with-iconv-bin
Date: Mon, 09 May 2011 19:09:00 -0000	[thread overview]
Message-ID: <83d3jritdz.fsf@gnu.org> (raw)
In-Reply-To: <20110509181947.6FF002461A8@ruffy.mtv.corp.google.com>

> Date: Mon,  9 May 2011 11:19:47 -0700 (PDT)
> From: dje@google.com (Doug Evans)
> 
>  *** Changes since GDB 7.3
>  
> +* New configure option --with-iconv-bin to specify where to find the
> +  iconv program.

Should we tell here what `iconv' is used for?  Users might not know
whether they should bother about this option.

> +If the GNU C Library you are using is installed in a non-standard place,
> +you will need to tell @value{GDBN} where to find the @code{iconv} program.
> +This is done with @option{--with-iconv-bin} which specifies the directory
> +that contains the @code{iconv} program.

I'm confused: what does `iconv's location have to do with the place
where glibc is installed?

Why not just say "if your @command{iconv} program is installed in a
non-standard place, you will need to tell @value{GDBN} where to find
it."?


  reply	other threads:[~2011-05-09 19:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09 18:20 Doug Evans
2011-05-09 19:09 ` Eli Zaretskii [this message]
2011-05-09 20:34   ` Doug Evans
     [not found]   ` <BANLkTikvtS3eSk_8e+40X5ky9h_HEX5VNQ@mail.gmail.com>
2011-05-09 20:36     ` Eli Zaretskii
2011-05-09 21:08       ` Doug Evans
2011-05-09 21:53         ` Doug Evans
2011-05-09 19:41 ` Tom Tromey

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=83d3jritdz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dje@google.com \
    --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