Ben Hutchings dixit: >the new Debian version crashes on s390x. It looks like this is due to >an address collision between the build ID in the shared library and >the code in the executables.
Helge Deller dixit: >[ 58.612345] 117 (fstype): Uhuuh, elf segment at 0000000000010000 requested >but the memory is mapped already Are these two maybe related? Perhaps marking the build ID as to not be read into memory, or adjusting the ldscript or the load offset of some regions, might help either? (Comparing objdump -x output of a working and a non-working both fstype binary and klibc.so might be useful.) Surprised the linker doesn’t catch this, //mirabilos -- When he found out that the m68k port was in a pretty bad shape, he did not, like many before him, shrug and move on; instead, he took it upon himself to start compiling things, just so he could compile his shell. How's that for dedication. -- Wouter, about my Debian/m68k revival
