From: Tom Tromey <tromey@redhat.com>
To: dje@google.com (Doug Evans)
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] --with-iconv-path
Date: Fri, 06 May 2011 17:57:00 -0000 [thread overview]
Message-ID: <m37ha3ww3f.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110506002720.DE3BF2461B1@ruffy.mtv.corp.google.com> (Doug Evans's message of "Thu, 5 May 2011 17:27:20 -0700 (PDT)")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> We have one environment where the iconv binary comes from a
Doug> non-standard location. This patch lets one tell gdb where to find
Doug> it.
Doug> Before I write docs/NEWS, can anyone think of any problems with
Doug> this approach?
It seems reasonable to me.
I don't have an opinion on the option name.
Doug> [Ideally one could query some iconv_*() function at runtime: It
Doug> knows where its going to find its .so files, and iconv is
Doug> typically at a fixed path relative to that. But I couldn't find
Doug> such an interface.
This is:
http://sourceware.org/bugzilla/show_bug.cgi?id=12234
Tom
prev parent reply other threads:[~2011-05-06 17:57 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
2011-05-06 17:57 ` Tom Tromey [this message]
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=m37ha3ww3f.fsf@fleche.redhat.com \
--to=tromey@redhat.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