Created attachment 504244 [details] stripped build.log for sys-libs/glibc-2.26-r3 I'm forced to upgrade to sys-libs/glibc-2.26-r3 (bug 637388, comment 1) but this fails at install phase due to “cannot execute binary file” for “/var/tmp/portage/sys-libs/glibc-2.26-r3/work/build-x86-x86_64-pc-linux-gnu-nptl/elf/sln” Comparison of available sln: $ [work]> file build-x86-x86_64-pc-linux-gnu-nptl/elf/sln build-x86-x86_64-pc-linux-gnu-nptl/elf/sln: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, for GNU/Linux 3.2.0, not stripped $ [work]> file build-amd64-x86_64-pc-linux-gnu-nptl/elf/sln build-amd64-x86_64-pc-linux-gnu-nptl/elf/sln: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 3.2.0, not stripped $ file /sbin/sln /sbin/sln: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 2.6.32, stripped
Please provide emerge --info.
Created attachment 504246 [details] glibc-2.26-r3_emerge.info Sorry I forgot.
First, just try to manually emerge libnsl in addition to world, to give portage a hint what to do. emerge -uDNav libnsl world (libnsl-0 doesnt require new glibc and is stable.) If that doesnt help, check if your Kernel is able to run 32bit binaries! You are compiling a multilib glibc, and for that you need a kernel that can run 32bit files...
(In reply to Andreas K. Hüttel from comment #3) > > […], check if your Kernel is able to run 32bit binaries! You are compiling a > multilib glibc, and for that you need a kernel that can run 32bit files... You make my day – it was the latter. Several weeks ago I've modified my kernel configuration (too aggressive) to reduce the kernel image and must have been dropped ‘CONFIG_IA32_EMULATION=y’. Thank you very much for your work, advice and sorry for the noise.
