From: Rich Felker <dalias@libc.org>
To: "A. Wilcox" <awilfox@adelielinux.org>
Cc: bruno@clisp.org, bug-bison@gnu.org, musl@lists.openwall.com
Subject: Re: [musl] Building Bison 3.7 with musl (was Re: portability issues with unicodeio)
Date: Wed, 29 Jul 2020 20:05:28 -0400 [thread overview]
Message-ID: <20200730000527.GS6949@brightrain.aerifal.cx> (raw)
In-Reply-To: <e01f541b-6255-27c5-d149-80fc7c223784@adelielinux.org>
On Wed, Jul 29, 2020 at 06:23:19PM -0500, A. Wilcox wrote:
> Seeing some weird behaviour here building Bison 3.7 on musl libc.
>
> Something seems to be "intelligent" enough to know that \u2022 is a
> bullet character, and is replacing it with "*" instead of ".", causing
> all the tests to fail:
>
> awilcox on gwyn [17] bison: LC_ALL=C /bin/printf '\u2022\n' | od -t x1
> 0000000 2a 0a
> 0000002
I don't think the '*' has anything to do with it being a bullet
character. It's just the implementation-defined replacement character
musl's iconv uses.
I would guess the code in bison and coreutils printf is assuming the
non-conforming glibc behavior for iconv of returning an error if a
character from the input is not exactly representable in the output,
rather than making replacements and returning the number of inexact
conversions made.
Rich
next prev parent reply other threads:[~2020-07-30 0:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 23:23 A. Wilcox
2020-07-29 23:48 ` A. Wilcox
2020-07-30 0:05 ` Rich Felker [this message]
2020-07-30 0:12 ` A. Wilcox
2020-07-30 1:43 ` Bruno Haible
2020-07-30 9:02 ` Florian Weimer
2020-07-30 9:39 ` [musl] Re: iconv replacements Bruno Haible
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=20200730000527.GS6949@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=awilfox@adelielinux.org \
--cc=bruno@clisp.org \
--cc=bug-bison@gnu.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).