> Date: Sat, 1 Mar 2014 20:18:34 +0000 > From: Ken Moffat <zarniwh...@ntlworld.com> > To: blfs-dev@linuxfromscratch.org > Subject: [blfs-dev] Policy on locale for building ? (ticket #4745) > . . > > If I configure gegl in my normal UTF-8 locale, there is no problem > even with ruby already installed. But if I pass LC_ALL=C to > configure, I get the reported problem during 'make' : > > ../tools/create-reference.rb:331:in `block (2 levels) in <main>': > invalid byte sequence in US-ASCII (ArgumentError) . . >
Hmmm. Does it _really_ require utf8 or similar to build? Seems like a poor idea to _require_ it. > What I don't recall is whether we ever recommend building packages > in BLFS using the C or POSIX locales ? My belief is that everyone > ought to be using UTF-8 locales by now, but from support posts over > the years I guess that some of our users are behind the curve in > this, and see no reason to change from legacy encodings (or perhaps > they have too much data to make that feasible). > Root (at least) here is always still non-utf8 . > . . > rgds, akh -- -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page