Mick wrote:
> On Thursday 17 Jul 2014 22:41:45 Dale wrote:
>> Howdy, different rig but similar issue. This is on my main rig now. It
>> is AMD64 multilib. I am doing a emerge -e world, which I do from time
>> to time. After that got to the point where it is almost done, I started
>> getting this:
>>
>> perl: warning: Setting locale failed.
>> perl: warning: Please check that your locale settings:
>> LANGUAGE = (unset),
>> LC_ALL = "en_US.UTF8",
>> LANG = "en_US.UTF8"
>> are supported and installed on your system.
>> perl: warning: Falling back to the standard locale ("C").
>> sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
>>
>> and like this:
>>
>> /bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
>>
>>>>> Regenerating /etc/ld.so.cache...
>> sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
>>
>> The error seems to vary depending on command run. This is my locale.gen
>> file:
>>
>> LANG="en_US.UTF8"
>> LC_CTYPE="en_US.UTF8"
>> LC_NUMERIC="en_US.UTF8"
>> LC_TIME="en_US.UTF8"
>> LC_COLLATE="en_US.UTF8"
>> LC_MONETARY="en_US.UTF8"
>> LC_MESSAGES="en_US.UTF8"
>> LC_PAPER="en_US.UTF8"
>> LC_NAME="en_US.UTF8"
>> LC_ADDRESS="en_US.UTF8"
>> LC_TELEPHONE="en_US.UTF8"
>> LC_MEASUREMENT="en_US.UTF8"
>>
>> I'm on sys-libs/glibc-2.17 right now.
>>
>> Now riddle me this, why is this popping up all of a sudden? Did
>> something change and I missed it? When I google, I find folks with
>> settings like mine and it works. Is this something new that just hasn't
>> hit everyone yet?
>>
>> Confused.
> /etc/locale.gen ought to show something like:
>
> en_US.UTF-8 UTF-8
>
> rather than what you show in your message. /etc/env.d/02locale can show what
> you have in your message above, but typically only this is necessary:
>
> LANG="en_US.UTF-8"
>
> (In mine I also have: LC_TIME="POSIX" and LC_COLLATE="C", but most users
> wouldn't).
>
I got that off a howto somewhere. I think it is a Gentoo one. Anyway,
commented all that out and left the one line, ran locale-gen and it
seems to have fixed it. Keep in mind, it's been that way for quite a
long time. No clue why it decides to moan about it now.
Thanks.
Dale
:-) :-)