Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Paul Koning" <Paul_Koning@Dell.com>
To: "Andreas Schwab" <schwab@linux-m68k.org>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFC] Make string printing work on NetBSD (iconv issue)
Date: Tue, 04 May 2010 20:06:00 -0000	[thread overview]
Message-ID: <D8CEBB6AE9D43848BD2220619A43F3265BCF0C@M31.equallogic.com> (raw)
In-Reply-To: <m2sk674etc.fsf@igel.home>

> Paul Koning <Paul_Koning@dell.com> writes:
> 
> > +dnl Check if iconv handles wchar_t, and if not, what to use
instead.
> > +if test "x$am_cv_func_iconv" = "xyes"; then
> > +  AC_MSG_CHECKING(iconv codeset for wchar_t)
> > +  if iconv -f ascii -t wchar_t /dev/null; then
> > +    AC_MSG_RESULT(wchar_t)
> > +    AC_DEFINE([ICONV_INTERMEDIATE_ENCODING],["wchar_t"],
> > +              [Codeset name that corresponds to wchar_t encoding.])
> 
> That tests iconv on the build system, but gdb uses iconv on the host
> system.

True.  Is there a way to test the host iconv?  I can make the check
conditional on "not a cross build".  Then what about cross builds?  If
there isn't a test that gives the answer, I could do something based on
host OS type.  Or that plus libiconv present/absent?

	paul


  reply	other threads:[~2010-05-04 20: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 [this message]
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
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=D8CEBB6AE9D43848BD2220619A43F3265BCF0C@M31.equallogic.com \
    --to=paul_koning@dell.com \
    --cc=gdb-patches@sourceware.org \
    --cc=schwab@linux-m68k.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