Gentoo Archives: gentoo-user

From: Neil Bothwick <neil@××××××××××.uk>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] SNAFU
Date: Thu, 02 Sep 2021 15:39:15
Message-Id: 20210902163856.6b388abc@phoucgh
In Reply to: [gentoo-user] SNAFU by Alan Grimes
1 On Thu, 2 Sep 2021 10:35:49 -0400, Alan Grimes wrote:
2
3 > Chromium has been a heaping pile of crash these days so I've been
4 > running update every few days to try to get a working version.
5 >
6 >
7 > Ok, apparently gcj is not a thing anymore and has broken libidn (iirc), 
8 >
9 > I got around that with a useflag...
10 >
11 > As always, Gentoo finds new and more bizare ways to FAIL.
12 >
13 > I noticed that udev wasn't building which is instantly a 3-alarm fire,
14 > if not worse...
15 >
16 > Library dl found: YES
17 >
18 > ../systemd-249/meson.build:910:0: ERROR: C shared or static library
19 > 'crypt' not found
20 >
21 > A full log can be found at
22 > /var/tmp/portage/sys-fs/udev-249-r2/work/systemd-249-abi_x86_32.x86/meson-logs/meson-log.txt
23 >  * ERROR: sys-fs/udev-249-r2::gentoo failed (configure phase):
24 >  *   (no error message)
25 >  *
26 >  * Call stack:
27 >  *     ebuild.sh, line  127:  Called src_configure
28 >  *   environment, line 4090:  Called multilib-minimal_src_configure
29 >  *   environment, line 2862:  Called multilib_foreach_abi
30 > 'multilib-minimal_abi_src_configure'
31 >  *   environment, line 3115:  Called multibuild_foreach_variant
32 > '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
33 >  *   environment, line 2792:  Called _multibuild_run
34 > '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
35 >  *   environment, line 2790:  Called _multilib_multibuild_wrapper
36 > 'multilib-minimal_abi_src_configure'
37 >  *   environment, line  710:  Called multilib-minimal_abi_src_configure
38 >  *   environment, line 2856:  Called multilib_src_configure
39 >  *   environment, line 3341:  Called meson_src_configure
40 >  *   environment, line 2726:  Called die
41 >  * The specific snippet of code:
42 >  *       "${mesonargs[@]}" ) || die
43 >  *
44 >  * If you need support, post the output of `emerge --info
45 > '=sys-fs/udev-249-r2::gentoo'`,
46 >  * the complete build log and the output of `emerge -pqv
47 > '=sys-fs/udev-249-r2::gentoo'`.
48 >  * The complete build log is located at
49 > '/var/tmp/portage/sys-fs/udev-249-r2/temp/build.log'.
50 >  * The ebuild environment file is located at
51 > '/var/tmp/portage/sys-fs/udev-249-r2/temp/environment'.
52 >  * Working directory:
53 > '/var/tmp/portage/sys-fs/udev-249-r2/work/systemd-249-abi_x86_32.x86'
54 >  * S: '/var/tmp/portage/sys-fs/udev-249-r2/work/systemd-249'
55 > sys-fs/udev-249-r2/temp/build.log lines 156-206/206 (END)
56 >
57 >
58 > Libxcrypt, I guess???
59 >
60 >
61 > Ok, so what's wrong with libxcrypt...
62 >
63 > make[2]: Leaving directory
64 > '/var/tmp/portage/sys-libs/libxcrypt-4.4.25/work/libxcrypt-4.4.25-xcrypt_nocompat-abi_x86_64.amd64'
65 > make[1]: Leaving directory
66 > '/var/tmp/portage/sys-libs/libxcrypt-4.4.25/work/libxcrypt-4.4.25-xcrypt_nocompat-abi_x86_64.amd64'
67 > >>> Completed installing sys-libs/libxcrypt-4.4.25 into
68 > /var/tmp/portage/sys-libs/libxcrypt-4.4.25/image
69 >
70 >  * Final size of build directory: 11572 KiB (11.3 MiB)
71 >  * Final size of installed tree:   1808 KiB ( 1.7 MiB)
72 >
73 >  * checking 38 files for package collisions
74 >  * This package will overwrite one or more files that may belong to
75 > other
76 >  * packages (see list below). You can use a command such as `portageq
77 >  * owners / <filename>` to identify the installed package that owns a
78 >  * file. If portageq reports that only one package owns a file then do
79 >  * NOT file a bug report. A bug report is only useful if it identifies
80 > at
81 >  * least two or more packages that are known to install the same
82 > file(s).
83 >  * If a collision occurs and you can not explain where the file came
84 > from
85 >  * then you should simply ignore the collision since there is not enough
86 >  * information to determine if a real problem exists. Please do NOT file
87 >  * a bug report at https://bugs.gentoo.org/ unless you report exactly
88 >  * which two packages install the same file(s). See
89 >  * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
90 >  * to solve the problem. And once again, please do NOT file a bug report
91 >  * unless you have completely understood the above message.
92 >  *
93 >  * Detected file collision(s):
94 >  *
95 >  *      /usr/include/crypt.h
96 >  *      /lib64/libcrypt.so.1
97 >  *
98 >  * Searching all installed packages for file collisions...
99 >  *
100 >  * Press Ctrl-C to Stop
101 >  *
102 >  * sys-libs/glibc-2.33-r7:2.2::gentoo
103 >  *      /lib64/libcrypt.so.1
104 >  *
105 >  * Package 'sys-libs/libxcrypt-4.4.25' NOT merged due to file
106 > collisions.
107 >  * If necessary, refer to your elog messages for the whole content of
108 > the
109 >  * above message.
110 >
111 >
112 > Obviously, anything associated with glibc is protected by the DO NOT
113 > TOUCH ANYTHING ASSOCIATED WITH GLIBC FOR ANY REASON, EVER. rule...
114 >
115 > So I'm roadblocked. =(
116 >
117 Did you read the news item from 23/7/21? It will have popped up when you
118 synced.
119
120 https://www.gentoo.org/support/news-items/2021-07-23-libxcrypt-migration.html
121
122
123 --
124 Neil Bothwick
125
126 You couldn't get a job as a firing squad target.