* Ralf Wildenhues wrote on Sat, Jan 30, 2010 at 12:45:33AM CET: > Current Cygwin fails the test with or without the patch below, but for > another reason: > > +allowed-chars Zardos differ: char 168, line 2 > > I'm not sure whether it is a regression. I've tried to debug it; it > looks like an issue in Cygwin sed or the shell. The config.status > script in that test directory looks weird: the text which is to be > substituted for @zardoz@ is mangled in a way that part of the last line > of the string also appears on an earlier line. I fail to see any > connection with newline encoding here, however.
It's a locale issue. configure scripts default their environment to C locale, but C doesn't have to mean ASCII. On my Cygwin, C means UTF-8. I suppose though that's just because Cygwin changed recently. Setting LC_ALL=C.ASCII makes the test pass. Now, I'm not sure what that means for real-life configure scripts. IOW, should _AS_SHELL_SANITIZE be fixed, or only this torture test? Then, is C.ASCII even a portable setting for LC_ALL (and LANGUAGE)? Thanks, Ralf
