You are not logged in.
Pages: 1
Hello,
My locale keeps getting set to en-US instead of C.UTF-8. This leaves errors like this one:
/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en-US)
Here is the output of my locale-gen:
% sudo locale-gen
/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en-US)
Generating locales...
en_US.UTF-8... done
Generation complete.
Here is the output for my /etc/locale.conf:
% cat /etc/locale.conf
LANG=C.UTF-8
I have also tried setting my locale in /etc/environment:
#
# This file is parsed by pam_env module
#
# Syntax: simple "KEY=VAL" pairs on separate lines
#
LC_ALL=C.UTF-8
The errors still persist. Any idea what I'm doing wrong?
Thank you.
Last edited by Toad39 (2020-11-21 23:43:52)
Offline
What does
Locale
show?
And make sure you've read https://wiki.archlinux.org/index.php/lo … leshooting
"curl -F 'sprunge=<-' http://sprunge.us < path-to-file" is holy
Offline
Generating locales...
en_US.UTF-8... done
Generation complete.
The only locale generated was for en_US.UTF-8.
Did you patch glibc to add C.UTF-8 support as Fedora do [1]?
[1] https://src.fedoraproject.org/rpms/glib … cale.patch
Edit:Toad39 was not using Arch:
https://bbs.archlinux.org/viewtopic.php?id=260884
Last edited by loqs (2020-11-18 03:23:14)
Offline
Edit:
Toad39 was not using Arch:
https://bbs.archlinux.org/viewtopic.php?id=260884
The post you mentioned was not me. What makes you think that?
Offline
loqs wrote:Edit:
Toad39 was not using Arch:
https://bbs.archlinux.org/viewtopic.php?id=260884The post you mentioned was not me. What makes you think that?
I have no idea how I thought the two names were the same.
Edit:
Fixed that, I do apologise. What about the rest of the post? How have you added C.UTF-8 support?
Last edited by loqs (2020-11-18 03:26:06)
Offline
C.UTF-8 does not exist, so of course setting LC_ALL to it causes a problem. LC_ALL should not be set in general at all.
Offline
It turns out that my terminal was changing things; using a different terminal helped. Sorry for the hassle.
(I changed back to en_US.UTF-8, didn't realize that C.UTF-8 wasn't supported.)
Last edited by Toad39 (2020-11-21 23:43:40)
Offline
Pages: 1