Greg Schafer wrote: > >> Bash-3.2 uses LANG=en_US.UTF-8 in the run-intl test. However, we set >> LC_ALL=C in the environment, and that overrides $LANG in the test, leading >> to the failure. >> >> The minimal solution is: >> >> sed -i 's/LANG/LC_ALL/' tests/intl.tests >> > > Even more minimal: > > make tests LC_ALL= >
Indeed, this also works, thanks :) > LC_ALL=C is just a sane and common sense thing to do while building > software IMHO. Theoretically, it should be safe to build in any locale.. > but over the years various problems have cropped up occasionally. > Therefore it would seem path of least resistance is to build everything > under LC_ALL=C. > Well, this seems to be correct for majority of software. The et_EE locale caused a lot of breakage in the past because "z" is in the middle in their alphabet (and thus "a-z" doesn't have the same meaning as usual). The default info dir file depends on the build locale. Thus C or English locale is the safest choice in the overwhelming majority of cases. But in Debian, there are (or were?) some exceptions (e.g., gimp-print). My point about "make menuconfig" and other ncurses programs, however, still stands - the book needs some change there. This certainly is not an issue for DIY, though, because DIY doesn't tell the user how to build the kernel. -- Alexander E. Patrakov -- http://linuxfromscratch.org/mailman/listinfo/lfs-book FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
