This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [doc RFA]: New option --with-iconv-bin
- From: Eli Zaretskii <eliz at gnu dot org>
- To: dje at google dot com (Doug Evans)
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 09 May 2011 22:08:40 +0300
- Subject: Re: [doc RFA]: New option --with-iconv-bin
- References: <20110509181947.6FF002461A8@ruffy.mtv.corp.google.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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."?