Dale wrote:
> Michael wrote:
>> On Monday, 24 June 2024 06:19:10 BST Dale wrote:
>>> William Kenworthy wrote:
>>>> ...
>>>>
>>>>> Now to ponder what comes next.
>>>>>
>>>>> Dale
>>>>>
>>>>> :-) :-)
>>>> Hi Dale, did I see in one of your early emails you created an
>>>> xorg.conf for nvidia? Have you followed the gentoo Xorg guide where
>>>> it says to try first without that file? I doubt the knoppix etc use a
>>>> conf file and so must depend on the auto detection.
>>>>
>>>> Based on my own experience I can say using an xorg.conf (though it was
>>>> a radeon card) is an easy way to shoot yourself in the foot!
>>>>
>>>> BillK
>>> At first I did not have a xorg.conf file. When it didn't work right, I
>>> tried creating one to see if it would work. It didn't work with or
>>> without one.
>> Yes, but at first you were trying to launch a Wayland session.
>>
>> Did you also try to launch an X11 session without an xorg.conf file? Any
>> changes you need to include non-default settings should be added under /etc/
>> X11/xorg.conf.d/.
>>
>> https://wiki.gentoo.org/wiki/Xorg/Guide#Configuration
>>
>> You should at least try to launch a X11 session using a console and see what
>> is printed out on the CLI after you exit (or if it crashes).
>>
>> ~ $ exec dbus-launch --exit-with-session startplasma-x11
>
> I tried every combination I could think of. It seems the more I tried,
> the worse the failure got.
>
> Anyway, I've started a fresh install. I fixed my partition boo boo. I
> didn't need much of anything except to just get a fresh start so I used
> the zap feature of gdisk. After that, I used cgdisk to set up
> everything else, making sure the efi partition was ef00 and had the old
> fat type partition on it. Or was it vfat? Whatever the docs said. I
> copy and paste some of it except for the partition info.
>
> I did notice one thing, I copied some USE flags over from my current
> rig. I found some that might not should have been copied over before.
> I wonder if that could have caused a problem or two. I realized I chose
> the merged /usr stage3 but had split-usr USE flag in make.conf. That
> was one I remembered. There was a couple others as well.
>
> Right now, I'm warming up that thermal paste some more. ROFL
>
> Dale
>
> :-) :-)
>
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
*
* Call stack:
* ebuild.sh, line 136: Called src_compile
* environment, line 3348: Called meson-multilib_src_compile
* environment, line 2023: Called multilib-minimal_src_compile
* environment, line 2217: Called multilib_foreach_abi
'multilib-minimal_abi_src_compile'
* environment, line 2484: Called multibuild_foreach_variant
'_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile'
* environment, line 2177: Called _multibuild_run
'_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile'
* environment, line 2175: Called _multilib_multibuild_wrapper
'multilib-minimal_abi_src_compile'
* environment, line 634: Called multilib-minimal_abi_src_compile
* environment, line 2211: Called multilib_src_compile
* environment, line 2704: Called meson_src_compile
* environment, line 2090: Called eninja
* environment, line 1470: Called die
* The specific snippet of code:
* "$@" || die -n "${*} failed"
*
* If you need support, post the output of `emerge --info
'=x11-libs/libdrm-2.4.120::gentoo'`,
* the complete build log and the output of `emerge -pqv
'=x11-libs/libdrm-2.4.120::gentoo'`.
* The complete build log is located at
'/var/log/portage/x11-libs:libdrm-2.4.120:20240624-140627.log'.
* For convenience, a symlink to the build log is located at
'/var/tmp/portage/x11-libs/libdrm-2.4.120/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/x11-libs/libdrm-2.4.120/temp/environment'.
* Working directory:
'/var/tmp/portage/x11-libs/libdrm-2.4.120/work/libdrm-2.4.120-abi_x86_64.amd64'
* 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.
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. If someone is
reading this still and thinks the docs should be changed or at least a
alert/warning added, then please alert the right people. I have no idea
how to get the docs updated.
I might add, on my first install, I had a different package that failed
until I set the locale up correctly. The error was a little more
obvious tho. I kept searching for 'error 1' and there is none here.
I hope this helps someone else googling for this or maybe gets the docs
updated, if needed.
Dale
:-) :-)
