Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Paul Koning'" <Paul_Koning@Dell.com>
Cc: <gdb@sourceware.org>
Subject: RE: iconv without "wchar_t" as a conversion name
Date: Tue, 04 May 2010 13:15:00 -0000	[thread overview]
Message-ID: <001b01caeb8b$cae29970$60a7cc50$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <D8CEBB6AE9D43848BD2220619A43F3265BCE9B@M31.equallogic.com>

  I already tried to propose a patch going in the direction you
indicate, but the replies were not very positive...

See
http://sourceware.org/ml/gdb-patches/2010-04/msg00719.html

Pierre Muller
Pascal language support maintainer for GDB


> -----Message d'origine-----
> De : gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] De la
> part de Paul Koning
> Envoyé : Tuesday, May 04, 2010 2:16 PM
> À : gdb@sourceware.org
> Objet : iconv without "wchar_t" as a conversion name
> 
> NetBSD has iconv support, essentially the same as in glibc, with one
> crucial difference that messes up GDB.
> 
> In gdb_wchar.h, INTERMEDIATE_ENCODING is hardcoded as "wchar_t" and in
> charset.c iconv_open() is called with INTERMEDIATE_ENCODING as the "to"
> format.
> 
> As it happens, the NetBSD implementation of iconf does not list
> "wchar_t" as a format it knows, though it does have a very long list of
> supported formats that looks otherwise quite similar to what iconv on,
> say, Linux supports.
> 
> I assume "wchar_t" means "whatever character format is the native
> encoding of a wchar_t data type".  If so, it looks like "ucs-4" would
> be
> a valid replacement, since wchar_t maps to int on NetBSD.  This suggest
> that INTERMEDIATE_ENCODING should be determined by configure instead of
> being hardcoded.
> 
> Does this make sense?  I can work on a patch, though hints on how to do
> this in configure would be welcome since I'm a beginner in that space.
> 
> 	paul


      reply	other threads:[~2010-05-04 13:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04 12:16 Paul Koning
2010-05-04 13:15 ` Pierre Muller [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='001b01caeb8b$cae29970$60a7cc50$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=Paul_Koning@Dell.com \
    --cc=gdb@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