On 12/17/06, Greg Schafer <[EMAIL PROTECTED]> wrote: > > Reporter: [EMAIL PROTECTED] > > > However, I don't know if the original reasoning for setting LC_ALL=C > > during the whole build still holds. > > 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.
I'd just like to toss out a specific problem I had with this the other day. Normally when I install packages through my scripts, LANG=C is set. But the other day I was messing around with dash and just built it in my home directory with my typical locale settings. I ended up running into this bizarre problem where the : builtin wasn't giving not found errors. I eventually traced it down to the fact that the builtins are contained in a struct that gets generated from a script. Part of the script is calling sort because the struct needs to be sorted to work in a binary tree search. Well, without LANG=C, ":" comes before "." and ":" would never be found in the binary search. So, I think the moral of the story is that if your _building_ C programs, it's probably a good idea to set your locale as C. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-book FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
