> Op 3 nov. 2017, om 00:15 heeft DJ Lucas <blfs-...@lucasit.com> het volgende > geschreven: > (…) > I don't build PPC, but that link should be /lib/ld-lsb-ppc32.so.3 for PPC32 > or /lib64/ld-lsb-ppc64.so.3 for PPC64. > > See: > > http://refspecs.linuxfoundation.org/LSB_5.0.0/LSB-Core-PPC32/LSB-Core-PPC32/requirements.html#RLIBRARIES > > and > > http://refspecs.linuxfoundation.org/LSB_5.0.0/LSB-Core-PPC64/LSB-Core-PPC64/requirements.html#RLIBRARIES > > —DJ
I changed the link as suggested by DJ but it didn’t solve the problem. To be sure that no leftover form the previous build is still contaminating the system, I even restarted from zero. It is maybe good to know that, already during the build of glibc, the system is spitting out tons of messages “ld.so.1: unhandled signal 11 at …”, but without stopping the command script. The script only stops when executing zic. coredumpctl reports hundreds of lines like: zo 2017-11-05 12:40:44 CET 21343 -775979576 -775979576 11 * /mnt/build_dir/sources/glibc-2.26/build/elf/ld.so pvg
-- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
