Created attachment 548568 [details] build.log Can't Determine Endianness
Created attachment 548570 [details] emerge --info
I can reproduce on hppa.
I'm guessing these are fixed upstream by commit ce92e974b8ecff19cf430b7b58a09b8190645b5c Author: David Howells <dhowells@redhat.com> Date: Fri Feb 26 10:07:00 2016 +0000 TEST: Fix endianness determination Endianness determination was broken sometime after Fedora 20 when executables switched to being DYN objects rather than EXEC objects. This caused the output of file to change. Signed-off-by: David Howells <dhowells@redhat.com> commit f0d9a8c15f1525d0404077f32fddccb606a61bac Author: Tyler Hicks <tyhicks@canonical.com> Date: Mon Feb 24 18:52:41 2014 -0600 TEST: Make endianness detection work with file 5.14 The 5.14 release of file outputs an extra space after [LM]SB: $ ./src/file -m magic/magic.mgc -L /proc/$$/exe /proc/12755/exe: ELF 64-bit LSB executable, ... This was due to the elf magic file containing some trailing spaces in the 5.14 release. Signed-off-by: Tyler Hicks <tyhicks@canonical.com> Signed-off-by: David Howells <dhowells@redhat.com> They are in the 1.5.10 release. Can we cherry-pick these patches to 1.5.9-rX or alternatively stabilize 1.5.11?
v1.6.1 is stable.