New issue
Advanced search Search tips

Issue 899377 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug
Build-Toolchain

Blocking:
issue 834385



Sign in to add a comment

locale-gen warning message shen entering chroot with glibc 2.27

Project Member Reported by yunlian@chromium.org, Oct 26

Issue description

With glibc 2.27, when entering chroot, I can see
 * Adding locales to archive ...
stat of "//usr/lib64/locale/*" failed: No such file or directory: ignored
rm: cannot remove '//usr/lib64/locale/*': No such file or directory 

These message was not shown with glibc 2.23

The message comes from locale-gen

When running
 env LC_ALL=C /usr/sbin/locale-gen -q -u -j 1 -G "en_US ISO-8859-1 en_US.UTF-8 UTF-8"

It shows
 * Adding locales to archive ...
//usr/lib64/locale/*/
/usr/bin/localedef --add-to-archive //usr/lib64/locale/locale-archive --replace --prefix /
cannot open locale archive "//usr/lib64/locale/locale-archive": Permission denied
 * en_US.UTF-8:

I plan to remove this part of code from locale-gen 2.27 because they are not shown in glibc 2.23
 
Summary: locale-gen warning message shen entering chroot with glibc 2.27 (was: warning message shen entering chroot with glibc 2.27)
a couple of topics here.

(1) you can't remove generate_locales from sdk_lib/enter_chroot.sh.  the code isn't there just for en_US.UTF-8, it's there to make sure whatever locale settings the user has work.  we do not require everyone to use en_US.UTF-8 to build CrOS.
(2) the command you ran by hand lacked `sudo`, so you of course will get a permission denied error.  if you look at the enter_chroot logic you'll see that it's implicitly being run as root.
(3) all that said, i don't know why the locale-gen code is not working for you (the "No such file or directory" errors).  it should work, even if the locale directory doesn't exist at all.  maybe locale-gen has a bug in it.

Sign in to add a comment