From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mark.kettenis@xs4all.nl, brobecker@adacore.com,
bauerman@br.ibm.com, andreolb@gmail.com,
gdb-patches@sourceware.org
Subject: Re: [PATCH] PR exp/9103
Date: Wed, 18 Mar 2009 17:11:00 -0000 [thread overview]
Message-ID: <m3hc1qiyfu.fsf@fleche.redhat.com> (raw)
In-Reply-To: <ud4cfqx7x.fsf@gnu.org> (Eli Zaretskii's message of "Wed\, 18 Mar 2009 06\:19\:30 +0200")
Eli> It's okay, but I have two comments:
How about this? I tried to address your comments.
Tom
2009-03-18 Tom Tromey <tromey@redhat.com>
* gdb.texinfo (Requirements): Mention iconv.
diff --git a/gdb/NEWS b/gdb/NEWS
index 3f084e7..a8ddd45 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -8,7 +8,9 @@ target. Strings whose character type is wchar_t, char16_t, or
char32_t are now correctly printed. GDB supports wide- and unicode-
literals in C, that is, L'x', L"string", u'x', u"string", U'x', and
U"string" syntax. And, GDB allows the "%ls" and "%lc" formats in
-`printf'.
+`printf'. This feature requires iconv to work properly; if your
+system does not have a working iconv, GDB can use GNU libiconv. See
+the installation instructions for more information.
* GDB now supports automatic retrieval of shared library files from
remote targets. To use this feature, specify a system root that begins
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 7a49aea..44f7b4d 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -24734,6 +24734,24 @@ The @samp{zlib} library is likely included with your operating system
distribution; if it is not, you can get the latest version from
@url{http://zlib.net}.
+@item iconv
+@value{GDBN}'s features related to character sets (@pxref{Character
+Sets}) require a functioning @code{iconv} implementation. If you are
+on a GNU system, then this is provided by the GNU C Library. Some
+other systems also provide a working @code{iconv}.
+
+On systems with @code{iconv}, you can install GNU Libiconv. If you
+have previously installed Libiconv, you can use the
+@option{--with-libiconv-prefix} option to configure.
+
+@value{GDBN}'s top-level @file{configure} and @file{Makefile} will
+arrange to build Libiconv if a directory named @file{libiconv} appears
+in the top-most source directory. If Libiconv is built this way, and
+if the operating system does not provide a suitable @code{iconv}
+implementation, then the just-built library will automatically be used
+by @value{GDBN}. One easy way to set this up is to download GNU
+Libiconv, unpack it, and then rename the directory holding the
+Libiconv source code to @samp{libiconv}.
@end table
@node Running Configure
next prev parent reply other threads:[~2009-03-18 16:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c3f94bcc0903101928g3d767b7ah60ac81e8b6f77de@mail.gmail.com>
2009-03-11 15:37 ` Andre Oliveira Loureiro do Baixo
2009-03-11 16:30 ` Daniel Jacobowitz
2009-03-11 17:09 ` Andre Oliveira Loureiro do Baixo
2009-03-11 17:13 ` Tom Tromey
2009-03-11 18:37 ` Andre Oliveira Loureiro do Baixo
2009-03-11 20:29 ` Thiago Jung Bauermann
2009-03-11 22:25 ` Tom Tromey
2009-03-12 1:11 ` Tom Tromey
2009-03-13 23:37 ` Joel Brobecker
2009-03-13 23:38 ` Joel Brobecker
2009-03-14 1:41 ` Tom Tromey
2009-03-14 0:10 ` Mark Kettenis
2009-03-17 20:06 ` Tom Tromey
2009-03-17 22:12 ` Eli Zaretskii
2009-03-18 3:07 ` Tom Tromey
2009-03-18 4:20 ` Eli Zaretskii
2009-03-18 17:11 ` Tom Tromey [this message]
2009-03-18 20:30 ` Eli Zaretskii
2009-03-18 0:46 ` Joel Brobecker
2009-03-18 1:14 ` 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=m3hc1qiyfu.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=andreolb@gmail.com \
--cc=bauerman@br.ibm.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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