Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: Iconv / Solaris
Date: Fri, 28 Aug 2009 01:24:00 -0000	[thread overview]
Message-ID: <m3hbvspx99.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090827203609.GA13388@caradoc.them.org> (Daniel Jacobowitz's 	message of "Thu, 27 Aug 2009 16:36:09 -0400")

>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:

Daniel> On Thu, Aug 27, 2009 at 02:30:30PM -0600, Tom Tromey wrote:
>> The initial problem here is that iconv will not accept "wchar_t" as an
>> encoding on this platform.  I see we only have one AC_TRY_RUN in gdb
>> ... am I right in assuming that these are not ok?

Daniel> They are not OK.  Please don't add another if you can avoid it.  I
Daniel> think the one that's there is for long long printf?  I used to have
Daniel> to override the cache variable... haven't checked lately.

Oops, I read your notes out-of-order.

Ok, no new AC_TRY_RUN.

The existing one is some obscure old Linux thing:

  dnl For Linux/i386, glibc 2.1.3 was released with a bogus
  dnl prfpregset_t type (it's a typedef for the pointer to a struct
  dnl instead of the struct itself).  We detect this here, and work
  dnl around it in gdb_proc_service.h.

>> If they are not ok, I think we can just add a new setting to
>> configure.host.  This is simpler to implement.

Daniel> I'm not sure how to do this without hardcoding it by platform.  If the
Daniel> user has external libiconv, do we still want a change?

What we want is to skip case #1 in gdb_wchar.h (the full support case)
and let configure choose between case #2 (iconv only) and case #3
(nothing) depending on whether iconv was found.

I can write a patch tomorrow.

Tom


  parent reply	other threads:[~2009-08-28  1:01 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
2009-08-27 22:03           ` Daniel Jacobowitz
2009-08-28  1:01           ` Tom Tromey
2009-08-28  1:24         ` Tom Tromey [this message]
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=m3hbvspx99.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --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