I might be wrong, but I think this is a Debian (and derived) thing. I did a search before commenting, and apparently there is no C.UTF-8 in upstream glibc. I see several discussions about possibly adding it, some dating as late as August 2015, but haven't found any sign that it was added to glibc. One example is https://sourceware.org/bugzilla/show_bug.cgi?id=16621#c4
I know that there had been resistance in Fedora to a patch to add C.UTF-8, and a preference to wait until upstream glibc got it. I don't currently have access to my non-debian-derived test environments, so don't take my word for it... On Fri, Jan 15, 2016 at 9:09 PM, Samuel Holland <sam...@sholland.org> wrote: > On 01/15/2016 02:28 PM, Rob Landley wrote: > >> In theory, this means I set LC_ALL=c in scripts/test.sh the same way >> I do in scripts/make.sh, but I don't want to accidentally disable >> UTF8 support in the host version I'm testing against. >> > > Then set LC_ALL=C.UTF-8 > > This works on both glibc and musl for enabling UTF8 support in the GNU > tools, while keeping C locale semantics. > > -- > Regards, > Samuel Holland <sam...@sholland.org> > > _______________________________________________ > Toybox mailing list > Toybox@lists.landley.net > http://lists.landley.net/listinfo.cgi/toybox-landley.net >
_______________________________________________ Toybox mailing list Toybox@lists.landley.net http://lists.landley.net/listinfo.cgi/toybox-landley.net
