On Mon, Jun 29, 2015 at 07:49:24PM -0400, Chet Ramey wrote:
> That't not what he's saying. He's saying -- correctly -- that different
> locales produce different localized error messages (e.g., "command not
> found") and that produces output. The majority of those tests can set
> LC_ALL=C without
On 6/29/15 7:44 PM, Eduardo A. Bustamante López wrote:
> Using LC_ALL=C here is just like hiding your head in the dirt and pretending
> nothing is wrong. If the tests break with non-C locales, it means that bash
> doesn't compile correctly under that system, and that's worth investigating.
That't
Using LC_ALL=C here is just like hiding your head in the dirt and pretending
nothing is wrong. If the tests break with non-C locales, it means that bash
doesn't compile correctly under that system, and that's worth investigating.
--
Eduardo Bustamante
https://dualbus.me/
Configuration Information:
Machine: x86_64
OS: cygwin
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='x86_64-unknown-cygwin'
-DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash'
-DSHELL -DHAVE_CONFIG_H -
