Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: Iconv / Solaris
Date: Thu, 27 Aug 2009 20:50:00 -0000	[thread overview]
Message-ID: <20090827204258.GB13388@caradoc.them.org> (raw)
In-Reply-To: <20090827203609.GA13388@caradoc.them.org>

On Thu, Aug 27, 2009 at 04:36:09PM -0400, Daniel Jacobowitz wrote:
> > If they are not ok, I think we can just add a new setting to
> > configure.host.  This is simpler to implement.
> 
> I'm not sure how to do this without hardcoding it by platform.  If the
> user has external libiconv, do we still want a change?

Maybe I'm thinking about this wrong... can we determine the encoding
of wchar_t somehow that works on Solaris?  Something like what we do
now with nl_langinfo?  Or is it not guaranteed to have any known
encoding?

I'm lost in the configure maze, but if we don't define PHONY_ICONV,
then INTERMEDIATE_CHARSET ought to be host_charset anyway.  So the
fact that your patch made a difference implies that PHONY_ICONV is
defined.  So what's failing?  Isn't it our *dummy* iconv_open?

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2009-08-27 20:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-27  2:22 Daniel Jacobowitz
2009-08-27 17:09 ` Tom Tromey
2009-08-27 17:45   ` Daniel Jacobowitz
2009-08-27 20:36     ` Tom Tromey
2009-08-27 20:38       ` Daniel Jacobowitz
2009-08-27 20:50         ` Daniel Jacobowitz [this message]
2009-08-27 22:03           ` Daniel Jacobowitz
2009-08-28  1:01           ` Tom Tromey
2009-08-28  1:24         ` Tom Tromey
2009-08-28 17:00           ` 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=20090827204258.GB13388@caradoc.them.org \
    --to=drow@false.org \
    --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