Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Paul Koning" <Paul_Koning@Dell.com>
To: <tromey@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFC] Make string printing work on NetBSD (iconv issue)
Date: Mon, 10 May 2010 21:25:00 -0000	[thread overview]
Message-ID: <D8CEBB6AE9D43848BD2220619A43F3265BD195@M31.equallogic.com> (raw)
In-Reply-To: <m3sk63e3ee.fsf@fleche.redhat.com>

> Paul> It clearly can't make matters worse, because any platform that
> doesn't
> Paul> have the codeset name "wchar_t" currently doesn't work at all.
> 
> I think it is worse in one sense, which is that the results can be
> incorrect with no warning.  In particular I believe this could happen
> on
> Solaris in some locales.
> 
> I do see your point though.  Completely failing is terrible.
> 
> Paul> NetBSD clearly is using UCS-4 for wchar_t, but it does not
define
> that
> Paul> symbol.
> 
> Bummer.
> 
> Yet another idea would be host-specific overrides for
> INTERMEDIATE_ENCODING.

That would also have the advantage of working right in cross builds.  I
think I'll rewrite the patch to do that, and make it specifically
override for NetBSD where the right answer is known.  That way people
familiar with other hosts can supply the corresponding override for
those systems.

	paul


  reply	other threads:[~2010-05-10 21:25 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 [this message]
2010-05-19 15:11     ` Tom Tromey
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=D8CEBB6AE9D43848BD2220619A43F3265BD195@M31.equallogic.com \
    --to=paul_koning@dell.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.com \
    /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