[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PERL broken -- here, anyway...
>
>> ..not really.. at least PERL isn't broken, but the "here" part might
>> be...
>> it is hard to tell...
>>
>> every time PERL is called (even for perl -v), it produces the following
>> message:
>> perl: warning: Setting locale failed.
>> perl: warning: Please check that your locale settings:
>> LANGUAGE = (unset),
>> LC_ALL = (unset),
>> LANG = "en_US"
>> are supported and installed on your system.
>> perl: warning: Falling back to the standard locale ("C").
>
>Oh yea! I had that too. But you only get it when running perl?
So far, yes. The next command I issue might do it, but so far, I've managed
to avoid it. maybe I'm lucky. Interesting this I'm going to track down is that
CGI scripts running on the same host do NOT clutter up the log with the above,
so the user "apache" is probably configured right.
>If you run a GNOME app (or something else that uses UNICODE) from the
>command line do you see the same thing?
Maybe, just haven't had the honor yet. I'm running KDE on the machine, and
doubt I've loaded up any GNOME apps (the machine is a recent install of
BSWare 7.0 #20, but done with the RGB Ruthless Minimal Custom Install [tm]
technique).
>Do you have LANG set before you run perl?
See the error message above...or... pick a shell and type:
env|grep LANG
LANG=en_US
>Maybe you deleted your locales directory?
Nah, there are locale directories in several places. Want to know where? In
any case, I haven't touched 'em.
Regards,
---> RGB <---