RE: [RFC] Make string printing work on NetBSD (iconv issue)

["Paul Koning" <Paul_Koning@Dell.com>]

That gnu.org webpage talks about FreeBSD which is a different OS, and
what it says may or may not apply to NetBSD.  I guess I will have to ask
about this, since looking at the newlib sources (which is what libc is
in NetBSD) only got me lost.

	paul

> -----Original Message-----
> From: Tom Tromey [mailto:tromey@redhat.com]
> Sent: Wednesday, May 19, 2010 11:07 AM
> To: Paul Koning
> Cc: gdb-patches@sourceware.org
> Subject: Re: [RFC] Make string printing work on NetBSD (iconv issue)
> 
> >>>>> "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