I am using lfs-7.5-systemd to build lfs-7.6-systemd. It's my third lfs build but the first time I have used a systemd host.
During the gcc make check in 6.17, the kernel went into a loop, printing out over and over "systemd-coredump. Failed to send coredump. No space left on device". I don't know what device was being referred to but it certainly wasn't the new lfs partition, which had plenty of space and plenty of inodes too. I think the kernel was choking on a core which it couldn't dump because there was no such program as systemd-coredump in the chroot environment. I found on my host system a file called /usr/lib/sysctl.d/50-coredump.conf which contains the line: kernel.core_pattern=|/lib/systemd/systemd-coredump %p %u %g %s %t %e. I think this is installed as part of the systemd package. I bypassed it by creating a link to /dev/null at /etc/sysctl.d/50-coredump.conf. When I booted up the next day, I was able to carry out the gcc tests successfully. Perhaps it might be worth making a note of this. -- Hazel Russman <[email protected]> -- 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
