From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can't get the GUI to stay up for more than a minute or so before crashing
Date: Mon, 24 Jun 2024 17:00:10 +0100 [thread overview]
Message-ID: <9298683.CDJkKcVGEf@rogueboard> (raw)
In-Reply-To: <74d05acd-b8ba-4066-d697-732f7a6eff50@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2517 bytes --]
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".
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-06-24 16:00 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 19:02 [gentoo-user] Can't get the GUI to stay up for more than a minute or so before crashing Dale
2024-06-22 11:49 ` Michael
2024-06-22 13:32 ` Jude DaShiell
2024-06-22 16:12 ` Dale
2024-06-22 18:13 ` Dale
2024-06-22 18:54 ` Dale
2024-06-22 20:04 ` Michael
2024-06-23 1:21 ` Dale
2024-06-23 9:13 ` Michael
2024-06-23 7:20 ` Wols Lists
2024-06-23 0:13 ` Mark Knecht
2024-06-23 1:30 ` Dale
2024-06-23 7:53 ` Dale
2024-06-23 9:20 ` Michael
2024-06-23 12:19 ` Dale
2024-06-23 14:22 ` Michael
2024-06-23 22:37 ` Dale
2024-06-24 0:01 ` Michael
2024-06-24 1:55 ` Dale
2024-06-24 2:53 ` William Kenworthy
2024-06-24 5:19 ` Dale
2024-06-24 9:03 ` Michael
2024-06-24 13:25 ` Dale
2024-06-24 14:29 ` Dale
2024-06-24 14:57 ` Peter Humphrey
2024-06-24 16:00 ` Michael [this message]
2024-06-24 15:38 ` Michael
2024-06-24 16:54 ` Dale
2024-06-24 17:31 ` Michael
2024-06-24 19:47 ` Dale
2024-06-24 20:43 ` Michael
2024-06-24 21:03 ` Dale
2024-06-24 21:22 ` [gentoo-user] " Grant Edwards
2024-06-24 21:52 ` Dale
2024-06-24 23:00 ` Michael
2024-06-24 23:54 ` Dale
2024-06-24 22:48 ` [gentoo-user] " Michael
2024-06-24 23:47 ` Dale
2024-06-25 9:34 ` Michael
2024-06-25 10:18 ` Dale
2024-06-24 7:15 ` Wols Lists
2024-06-24 8:38 ` Michael
2024-06-25 14:27 ` Dale
2024-06-25 16:23 ` Michael
2024-06-25 18:54 ` Dale
2024-06-25 23:23 ` Michael
2024-06-26 0:28 ` [gentoo-user] SOLVED " Dale
2024-06-26 8:30 ` Michael
2024-06-26 20:32 ` [gentoo-user] " Dale
2024-06-27 6:54 ` Dale
2024-06-27 18:27 ` Michael
2024-06-27 19:09 ` Mark Knecht
2024-06-27 21:06 ` Dale
2024-06-27 21:45 ` Michael
2024-06-27 22:52 ` Dale
2024-06-28 11:01 ` Michael
2024-06-28 21:25 ` Dale
2024-06-29 13:24 ` [gentoo-user] " Grant Edwards
2024-06-29 7:36 ` [gentoo-user] " Dale
2024-06-29 20:30 ` Dale
2024-06-29 21:12 ` Jack
2024-06-29 22:28 ` Dale
2024-06-29 22:14 ` Michael
2024-06-29 23:20 ` Mark Knecht
2024-06-30 0:24 ` Dale
2024-06-30 9:35 ` Dale
2024-06-30 9:36 ` Dale
2024-06-30 10:51 ` Michael
2024-06-30 22:56 ` Dale
2024-07-01 13:24 ` Michael
2024-07-01 13:51 ` Dale
2024-06-27 22:18 ` Mark Knecht
2024-06-27 23:01 ` Dale
2024-06-27 23:27 ` Mark Knecht
2024-06-28 5:10 ` Dale
2024-06-28 13:39 ` Mark Knecht
2024-06-28 21:40 ` Dale
2024-06-28 21:50 ` Mark Knecht
2024-06-29 3:55 ` Dale
2024-06-27 4:10 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9298683.CDJkKcVGEf@rogueboard \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox