From: Tom Tromey <tom@tromey.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Use Solaris iconv
Date: Thu, 20 Aug 2026 10:33:24 -0600 [thread overview]
Message-ID: <87o6ewu4yz.fsf@tromey.com> (raw)
In-Reply-To: <yddwltmjo2q.fsf@CeBiTec.Uni-Bielefeld.DE> (Rainer Orth's message of "Wed, 19 Aug 2026 14:23:57 +0200")
>>>>> "Rainer" == Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
Rainer> However, Solaris 11.4 iconv is good enough to use: enabling its use
Rainer> fixes 300+ failures.
Rainer> Ok for trunk?
I think it's fine, but my question here is whether gdb intends to
support versions of Solaris where this might not work.
Rainer> - Finally, some systems do not have iconv, or are really broken
Rainer> - (e.g., Solaris, which almost has all of this working, but where
Rainer> - just enough is broken to make it too hard to use). Here we provide
Rainer> - a phony iconv which only handles a single character set, and we
Ages ago I wrote this text, and it was true at the time. IIRC, Solaris
back then used some undocumented, idiosyncratic, system-specific wchar_t
encoding and there was no way to convert from the regular encodings to
wchar_t via iconv, or something like that.
I don't know when Solaris changed to using Unicode.
Anyway I guess the question I have is whether this:
Rainer> - || (defined (_LIBICONV_VERSION) && _LIBICONV_VERSION >= 0x108))
Rainer> + || (defined (_LIBICONV_VERSION) && _LIBICONV_VERSION >= 0x108) \
Rainer> + || (defined (__sun__) && defined (__svr4__)))
... should check some kind of Solaris version.
If not, maybe adding some note to the commit message on this topic would
be nice to have.
thanks,
Tom
next prev parent reply other threads:[~2026-08-20 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 12:23 Rainer Orth
2026-08-20 16:33 ` Tom Tromey [this message]
2026-08-20 18:00 ` Rainer Orth
2026-08-20 18:27 ` Simon Marchi
2026-08-21 15:08 ` Tom Tromey
2026-08-22 20:19 ` Rainer Orth
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=87o6ewu4yz.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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