From: "Daniel Richard G." <skunk@iSKUNK.ORG>
To: "Bruno Haible" <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: z/OS, iconv, and charset aliases
Date: Fri, 20 Dec 2019 13:23:03 -0500 [thread overview]
Message-ID: <c919ea35-02be-4d89-8486-efe4d09ccac0@www.fastmail.com> (raw)
In-Reply-To: <15474984.Y7zEzsZrB6@omega>
On Fri, 2019 Dec 20 03:19-05:00, Bruno Haible wrote:
>
> Thanks. From this, I think we can equate the following vendor names
> with GNU canonical names:
Is there a good test to ensure that the conversions are as expected? I
wouldn't put it past IBM to use a strange variant of some of these otherwise-
familiar encodings...
> Omitting identical names on both sides (e.g. BIG5 BIG5), I arrive at
> the two attached patches.
Git 3f7d8da2 gives me this build error:
make[3]: Entering directory `/tmp/gnulib-build/gllib'
source='/tmp/testdir/gllib/iconv_open.c' object='iconv_open.o' libtool=no \
DEPDIR=.deps depmode=aix /bin/sh /tmp/testdir/build-aux/depcomp \
xlc-wrap -DHAVE_CONFIG_H -I. -I/tmp/testdir/gllib -I.. -DGNULIB_STRICT_CHECKING=1 -D_UNIX95_THREADS -D_XOPEN_SOURCE=600 -DNSIG=39 -qhaltonmsg=CCN3296 -g -q64 -qfloat=ieee -qlanglvl=extc99 -qenumsize=4 -c -o iconv_open.o /tmp/testdir/gllib/iconv_open.c
ERROR CCN3205 /tmp/testdir/gllib/iconv_open-zos.h:29 "gperf generated tables don't work with this execution character set. Please report a bug to <bug-gperf@gnu.org>."
CCN0793(I) Compilation failed for file /tmp/testdir/gllib/iconv_open.c. Object file not created.
make[3]: *** [iconv_open.o] Error 12
Normally, everything builds using EBCDIC on this system. (There are ways
of compiling ASCII source, but that's not the usual way of working.)
There isn't a way to compile gperf tables in an encoding-agnostic
manner?
--Daniel
--
Daniel Richard G. || skunk@iSKUNK.ORG
My ASCII-art .sig got a bad case of Times New Roman.
next prev parent reply other threads:[~2019-12-20 18:23 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 2:28 [PATCH] IBM z/OS + EBCDIC support Daniel Richard G.
2015-09-22 15:23 ` Eric Blake
2015-09-22 19:27 ` Daniel Richard G.
2015-09-22 20:00 ` Paul Eggert
2015-09-22 20:08 ` Eric Blake
2015-09-22 20:51 ` Daniel Richard G.
2015-09-22 19:32 ` Paul Eggert
2015-09-22 19:46 ` Paul Eggert
2015-09-22 20:37 ` Daniel Richard G.
2015-09-22 22:03 ` Paul Eggert
2015-09-22 23:44 ` Daniel Richard G.
2015-09-23 2:02 ` Paul Eggert
2015-09-23 6:58 ` Daniel Richard G.
2015-09-23 19:05 ` Paul Eggert
2015-09-23 19:29 ` Paul Eggert
2015-09-23 21:57 ` Daniel Richard G.
2015-09-25 7:29 ` Paul Eggert
2015-09-26 0:25 ` Daniel Richard G.
2015-09-26 2:49 ` Paul Eggert
2015-09-26 4:39 ` Daniel Richard G.
2015-09-26 16:08 ` Ben Pfaff
2015-09-27 6:31 ` Daniel Richard G.
2015-09-27 6:59 ` Paul Eggert
2015-09-28 2:09 ` Daniel Richard G.
2015-10-15 4:49 ` Daniel Richard G.
2016-08-18 0:47 ` Paul Eggert
2016-08-18 8:24 ` Daniel Richard G.
2016-08-18 8:53 ` Paul Eggert
2016-08-19 8:20 ` Daniel Richard G.
2016-08-19 11:03 ` Bruno Haible
2016-08-19 19:28 ` Paul Eggert
2016-08-19 20:38 ` Daniel Richard G.
2019-12-19 4:57 ` z/OS configure triple Bruno Haible
2019-12-20 0:22 ` Daniel Richard G.
2019-12-20 6:29 ` Bruno Haible
2019-12-19 5:16 ` z/OS, iconv, and charset aliases Bruno Haible
2019-12-19 5:21 ` Bruno Haible
2019-12-20 4:38 ` Daniel Richard G.
2019-12-20 8:19 ` Bruno Haible
2019-12-20 18:23 ` Daniel Richard G. [this message]
2019-12-21 5:49 ` z/OS, iconv, and gperf Bruno Haible
2020-01-09 5:48 ` Daniel Richard G.
2020-01-19 21:52 ` Bruno Haible
2020-01-19 21:59 ` Bruno Haible
2020-01-19 22:32 ` Daniel Richard G.
2020-01-20 0:13 ` Bruno Haible
2020-01-22 6:38 ` Daniel Richard G.
2015-09-22 19:50 ` [PATCH] IBM z/OS + EBCDIC support Paul Eggert
2015-09-22 20:47 ` Daniel Richard G.
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c919ea35-02be-4d89-8486-efe4d09ccac0@www.fastmail.com \
--to=skunk@iskunk.org \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).