During preparation to move to new 17.0 profile I've observed I can't re-compile the GCC. It stops with error messages try to link 64-bit *.so to 32-bit binaries. It was also not possible to re-build packages with 'ABI_X86="64 32"' The 32-bit build stops because it could not find a working 32-bit compiler. After several hours comparing that system with another where compiling the GCC is working I realized, that the installed files of the GLIBC are different. On the broken system, the complete '/usr/lib32' folder is missing. Digging deeper it shows that right before I start to recompile the GCC the GLIBC was upgraded to 'sys-libs/glibc-2.25-r9' on the broken system. The working system has the same GLIBC version, but an older portage-tree. Using this tree-revision (629f0962875) on the broken system I could build a GLIBC version which includes all files in '/usr/lib32'. Build the GLIBC with the current HEAD (83245d6274656) the files are missing again. Something has changed in the tree which causes an incomplete GLIBC installation. Guess it has something to do with following error message while installing the files: ERROR: preinst Installation of a symlink is blocked by a directory: '/usr/lib/locale' This symlink will be merged with a different name: '/usr/lib/locale.backup.0001' LOG: preinst Defaulting /etc/host.conf:multi to on
Created attachment 509574 [details] /usr/lib32 content of working GLIBC /usr/lib32 content of working GLIBC
Created attachment 509576 [details] 'emerge --info' working GLIBC 'emerge --info' working GLIBC
Created attachment 509578 [details] "lib32" content of broken GLIBC "lib32" content of broken GLIBC
Created attachment 509580 [details] 'emerge --info' broken GLIBC 'emerge --info' broken GLIBC
Created attachment 509582 [details] error log installing broken GLIBC error log installing broken GLIBC
Same problem here, multilib 32bit is broken for glibc. Not sure but is it some foo todo with 'SYMLINK_LIB=yes setup to a 'lib32' subprofile'? https://github.com/gentoo/gentoo/commit/6564751b2aefe115338eceaaeff1ea4505879395#diff-928058c0ccdfea0aff7eb6c937fb77be
Yup, confirmed that commit is the problem. Reverting the commit and re-emerging glibc fixes 32bit building for multilib.
The same result for unstable sys-libs/glibc-2.26-r3. Reverting the commit and re-emerging glibc helps.
CCing author. I don't think breaking existing profiles was intended.
Yes, I've double-checked that existing profiles are not affected. Are you using pure Gentoo profiles? Are you doing anything custom wrt your profile?
In Theorie not. Tried with pure amd64/13.0 and amd64/17.0 profiles
For completeness, could you paste (from the broken profile): $ portageq envvar SYMLINK_LIB LIBDIR_x86 ?
$ portageq envvar SYMLINK_LIB LIBDIR_x86 yes lib32 I can't reproduce the issue even with restoring the tree to the mentioned commitment. It's strange.
Everyone who is still affected by this, could you please attach your emerge --info ?!
(In reply to Andreas K. Hüttel from comment #14) > Everyone who is still affected by this, could you please attach your emerge > --info ?! No response... RESOLVED HEISENBUG
