From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Doug Evans <dje@google.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [RFC] --with-iconv-path
Date: Fri, 06 May 2011 16:13:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1105061611441.8538@digraph.polyomino.org.uk> (raw)
In-Reply-To: <BANLkTikT53VF-UbvdzvxZQAe3u1hxPzrbQ@mail.gmail.com>
On Fri, 6 May 2011, Doug Evans wrote:
> For reference sake, the binary lives in the expected location given
> --with-libiconv-prefix (i.e., bin/iconv), but how do I effect the
> necessary change without breaking anything.
>
> If folks are happy with adding $WITH_LIBICONV_PREFIX/bin to the front
> of the search path instead (so no new configure option), I can do
> that.
> Seems reasonable, but I guess it *could* break someone's installation somewhere.
> OTOH, if people are passing --with-libiconv-prefix they may have
> iconvlist() in which case the iconv binary isn't used, so we're safe.
--with-libiconv-prefix gives a build-system path which may not be a
directory present on the host system when the gdb binary is used, so I
don't think it's suitable for this purpose (which should specify a host
system path - which I suppose should be relocated if under $exec_prefix).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2011-05-06 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 0:27 Doug Evans
2011-05-06 15:12 ` Joel Brobecker
2011-05-06 15:33 ` Doug Evans
2011-05-06 16:13 ` Joseph S. Myers [this message]
2011-05-06 17:57 ` 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=Pine.LNX.4.64.1105061611441.8538@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=brobecker@adacore.com \
--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