Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: "Paul Koning" <Paul_Koning@Dell.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [RFC] Make string printing work on NetBSD (iconv issue)
Date: Wed, 19 May 2010 15:11:00 -0000	[thread overview]
Message-ID: <m3wrv09bi9.fsf@fleche.redhat.com> (raw)
In-Reply-To: <D8CEBB6AE9D43848BD2220619A43F3265BD0B3@M31.equallogic.com> (Paul	Koning's message of "Fri, 7 May 2010 13:25:50 -0400")

>>>>> "Paul" == Paul Koning <Paul_Koning@Dell.com> writes:

Paul> NetBSD clearly is using UCS-4 for wchar_t, but it does not define that
Paul> symbol.
 
I have been wondering about this again recently.

I dug through the NetBSD libc a little, looking for this, but I couldn't
find it.  Then I ran across this page today:

    http://www.gnu.org/software/libunistring/manual/libunistring.html#The-wchar_005ft-mess

This claims that, like Solaris, NetBSD uses a locale-dependent wchar_t
encoding.  If this is the case then disabling the wide character code is
probably the simplest approach that will do something sensible for you.

BTW, libunistring seems like a nice approach.  It is close to what I
wish wchar_t support actually looked like.  I am tempted to say we
should go that route, but of course that would mean adding another
dependency :-(

Tom


  parent reply	other threads:[~2010-05-19 15:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04 19:43 Paul Koning
2010-05-04 20:01 ` Andreas Schwab
2010-05-04 20:06   ` Paul Koning
2010-05-07 16:40 ` Tom Tromey
2010-05-07 17:26   ` Paul Koning
2010-05-07 22:46     ` Tom Tromey
2010-05-10 21:25       ` Paul Koning
2010-05-19 15:11     ` Tom Tromey [this message]
2010-05-19 15:25       ` Paul Koning
2010-05-19 15:30         ` Tom Tromey
2010-05-19 18:23           ` Paul Koning

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=m3wrv09bi9.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=Paul_Koning@Dell.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