Re: [musl] Building Bison 3.7 with musl (was Re: portability issues with unicodeio)

* Bruno Haible: > Yes and no. The code is not making assumptions about a particular iconv() > implementation. But it needs to distinguish two categories of replacements > done by iconv(): > - those that are harmless (for example when replacing a Unicode TAG > character U+E00xx with an empty

Re: [musl] Building Bison 3.7 with musl (was Re: portability issues with unicodeio)

[CCing bug-gnulib] Rich Felker wrote: > 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. Correct. > I would guess the code in bison and coreutils printf is assuming the > non-conforming gl

Re: Building Bison 3.7 with musl (was Re: portability issues with unicodeio)

[CCing bug-gnulib. Dropping musl list from CC.] A. Wilcox wrote in : > 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 i