On Monday, 24 June 2024 15:29:21 BST Dale wrote:
> Dale wrote:

> If a person is trying to copy another install and runs into a failure in
> a package to compile, skip ahead and deal with the locale section first
> then come back.  This failure is between syncing the tree and during the
> Optional: Updating the @world set section.  I moved the USE line over
> from my old system with some changes so I expected quite a few updates. 
> I ran into libdrm failing, no matter what USE flags I try.  It failed
> with this: 
> 
> 
> ninja: build stopped: subcommand failed.
>  * ERROR: x11-libs/libdrm-2.4.120::gentoo failed (compile phase):
>  *   ninja -v -j16 -l10 failed
[snip ...]

>  * Working directory:
> '/var/tmp/portage/x11-libs/libdrm-2.4.120/work/libdrm-2.4.120-abi_x86_64.amd
> 64' * S: '/var/tmp/portage/x11-libs/libdrm-2.4.120/work/libdrm-2.4.120'
> /var/tmp/portage/x11-libs/libdrm-2.4.120/temp/environment: line 87:
> warning: setlocale: LC_MESSAGES: cannot change locale (en_US.UTF8): No such
> file or directory
> /var/tmp/portage/x11-libs/libdrm-2.4.120/temp/environment: line 90:
> warning: setlocale: LC_NUMERIC: cannot change locale (en_US.UTF8): No
> such file or directory
> /var/tmp/portage/x11-libs/libdrm-2.4.120/temp/environment: line 93:
> warning: setlocale: LC_TIME: cannot change locale (en_US.UTF8): No such
> file or directory
>  *
>  * The following package has failed to build, install, or execute postinst:
>  *
>  *  (x11-libs/libdrm-2.4.120:0/0::gentoo, ebuild scheduled for merge),
> Log file:
>  *   '/var/log/portage/x11-libs:libdrm-2.4.120:20240624-140627.log'
> 
> 
> The key part is that part about 8 lines or so up.  If the locale is not
> set, it will fail.  Once it is set, it compiles just fine. 

You mentioned this in your previous install and I suggested you checked your 
locale.  You had specified (well, you had copied over from you old system) a 
non-empty LC_ALL in that case.


> I don't know if the docs should be changed or not.  It could be that in
> most cases, doing it early could cause other problems.

The handbook is written for all sort of different profiles, inc. users of the 
musl libc - see note under the section "Configure locales".

However, I think setting an appropriate locale earlier should not be a problem 
and as you have identified it would actually avoid any failures when updating 
a relatively full @world set like yours. You can raise a bug in BGO to this 
effect.  Select /product/ "Documentation" and then /component/ "Handbook".