From: Alan Grimes <alonzotg@verizon.net>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] SNAFU
Date: Thu, 2 Sep 2021 10:35:49 -0400 [thread overview]
Message-ID: <1b60ceef-6ec6-afeb-c519-d21f3fc42cc0@verizon.net> (raw)
In-Reply-To: 1b60ceef-6ec6-afeb-c519-d21f3fc42cc0.ref@verizon.net
Chromium has been a heaping pile of crash these days so I've been
running update every few days to try to get a working version.
Ok, apparently gcj is not a thing anymore and has broken libidn (iirc),
I got around that with a useflag...
As always, Gentoo finds new and more bizare ways to FAIL.
I noticed that udev wasn't building which is instantly a 3-alarm fire,
if not worse...
Library dl found: YES
../systemd-249/meson.build:910:0: ERROR: C shared or static library
'crypt' not found
A full log can be found at
/var/tmp/portage/sys-fs/udev-249-r2/work/systemd-249-abi_x86_32.x86/meson-logs/meson-log.txt
* ERROR: sys-fs/udev-249-r2::gentoo failed (configure phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 127: Called src_configure
* environment, line 4090: Called multilib-minimal_src_configure
* environment, line 2862: Called multilib_foreach_abi
'multilib-minimal_abi_src_configure'
* environment, line 3115: Called multibuild_foreach_variant
'_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
* environment, line 2792: Called _multibuild_run
'_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
* environment, line 2790: Called _multilib_multibuild_wrapper
'multilib-minimal_abi_src_configure'
* environment, line 710: Called multilib-minimal_abi_src_configure
* environment, line 2856: Called multilib_src_configure
* environment, line 3341: Called meson_src_configure
* environment, line 2726: Called die
* The specific snippet of code:
* "${mesonargs[@]}" ) || die
*
* If you need support, post the output of `emerge --info
'=sys-fs/udev-249-r2::gentoo'`,
* the complete build log and the output of `emerge -pqv
'=sys-fs/udev-249-r2::gentoo'`.
* The complete build log is located at
'/var/tmp/portage/sys-fs/udev-249-r2/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/sys-fs/udev-249-r2/temp/environment'.
* Working directory:
'/var/tmp/portage/sys-fs/udev-249-r2/work/systemd-249-abi_x86_32.x86'
* S: '/var/tmp/portage/sys-fs/udev-249-r2/work/systemd-249'
sys-fs/udev-249-r2/temp/build.log lines 156-206/206 (END)
Libxcrypt, I guess???
Ok, so what's wrong with libxcrypt...
make[2]: Leaving directory
'/var/tmp/portage/sys-libs/libxcrypt-4.4.25/work/libxcrypt-4.4.25-xcrypt_nocompat-abi_x86_64.amd64'
make[1]: Leaving directory
'/var/tmp/portage/sys-libs/libxcrypt-4.4.25/work/libxcrypt-4.4.25-xcrypt_nocompat-abi_x86_64.amd64'
>>> Completed installing sys-libs/libxcrypt-4.4.25 into
/var/tmp/portage/sys-libs/libxcrypt-4.4.25/image
* Final size of build directory: 11572 KiB (11.3 MiB)
* Final size of installed tree: 1808 KiB ( 1.7 MiB)
* checking 38 files for package collisions
* This package will overwrite one or more files that may belong to other
* packages (see list below). You can use a command such as `portageq
* owners / <filename>` to identify the installed package that owns a
* file. If portageq reports that only one package owns a file then do
* NOT file a bug report. A bug report is only useful if it identifies at
* least two or more packages that are known to install the same file(s).
* If a collision occurs and you can not explain where the file came from
* then you should simply ignore the collision since there is not enough
* information to determine if a real problem exists. Please do NOT file
* a bug report at https://bugs.gentoo.org/ unless you report exactly
* which two packages install the same file(s). See
* https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
* to solve the problem. And once again, please do NOT file a bug report
* unless you have completely understood the above message.
*
* Detected file collision(s):
*
* /usr/include/crypt.h
* /lib64/libcrypt.so.1
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* sys-libs/glibc-2.33-r7:2.2::gentoo
* /lib64/libcrypt.so.1
*
* Package 'sys-libs/libxcrypt-4.4.25' NOT merged due to file collisions.
* If necessary, refer to your elog messages for the whole content of the
* above message.
Obviously, anything associated with glibc is protected by the DO NOT
TOUCH ANYTHING ASSOCIATED WITH GLIBC FOR ANY REASON, EVER. rule...
So I'm roadblocked. =(
--
Beware of Zombies. =O
#EggCrisis #BlackWinter
White is the new Kulak.
Powers are not rights.
next parent reply other threads:[~2021-09-02 14:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1b60ceef-6ec6-afeb-c519-d21f3fc42cc0.ref@verizon.net>
2021-09-02 14:35 ` Alan Grimes [this message]
2021-09-02 15:38 ` [gentoo-user] SNAFU Neil Bothwick
[not found] ` <5435f4a8-1b44-c668-f539-36c287e0ed09@verizon.net>
2021-09-02 20:12 ` Neil Bothwick
2021-09-02 21:49 ` David Haller
2021-09-02 21:58 ` David Haller
2021-09-02 22:11 ` Neil Bothwick
2021-09-02 22:54 ` antlists
2021-09-03 8:44 ` [gentoo-user] Richard Blackburn
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=1b60ceef-6ec6-afeb-c519-d21f3fc42cc0@verizon.net \
--to=alonzotg@verizon.net \
--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