It's only been a couple of weeks since I updated this system, so I don't know why it fails with a glibc update, while other systems have no problem:
>>> Emerging (1 of 62) sys-libs/glibc-2.36-r7::gentoo * glibc-2.36.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ] * glibc-2.36-patches-9.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ] * locale-gen-2.22.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ] * Checking whether python3_11 is suitable ... * >=dev-lang/python-3.11.1-r1:3.11 ... [ ok ] * Using python3.11 to build (via PYTHON_COMPAT iteration) >>> Unpacking source... * Checking general environment sanity. make -j5 -l6 glibc-test x86_64-pc-linux-gnu-gcc -m64 -march=native -pipe -O2 -fcf-protection=none - Wl,-O1 -Wl,--as-needed -march=native -pipe -O2 -fcf-protection=none -Wl,-O1 -Wl,--as-needed glibc-test.c -o glibc-test * Checking that IA32 emulation is enabled in the running kernel ... /var/tmp/portage/sys-libs/glibc-2.36-r7/temp/check-ia32-emulation.elf32: error [ !! ]oading shared libraries: /lib/libdl.so.2: cannot read file data: Input/ output error * ERROR: sys-libs/glibc-2.36-r7::gentoo failed (unpack phase): * CONFIG_IA32_EMULATION must be enabled in the kernel to compile a multilib glibc. * * Call stack: * ebuild.sh, line 136: Called src_unpack * environment, line 3766: Called sanity_prechecks * environment, line 3486: Called die * The specific snippet of code: * [[ $STAT -eq 0 ]] || die "CONFIG_IA32_EMULATION must be enabled in the kernel to compile a multilib glibc."; * The kernel has IA32_EMULATION compiled in: # grep IA32_EMULATION /usr/src/linux/.config CONFIG_IA32_EMULATION=y and /lib/libdl.so.2 appears to be present and correct: $ ls -l /lib/libdl.so.2 -rwxr-xr-x 1 root root 13660 Nov 20 13:59 /lib/libdl.so.2 So, why does it fail and more importantly ... how can I get past it? ;-)
signature.asc
Description: This is a digitally signed message part.
