This will install dbus.service and dbus.socket into
/usr/lib/systemd/user. In a base LFS installation the systemd per-user
daemon is not usable at all, so they may seem useless. But if we
install them, we can start to use them once systemd is rebuilt with PAM
in BLFS (without rebuilding dbus).
Well, the analyzer failures are introduced by literally *my* Glibc
change [1] and I'll sort them out for GCC 14...
And the ASAN failures seem caused by the introduction of
__isoc23_strtol (the libsanitizer does not know to intercept it). I'll
test with LLVM once I reach it in BLFS (LLVM is the upstream of
libsanitizer) and make a bug report.
limits-exprparen.c also fails to me, it needs "ulimit -s 65536" instead
of "ulimit -s 32768" in my build but maybe it's caused by my custom
*FLAGS.
[1]:https://sourceware.org/git/?p=glibc.git;a=commit;h=71d9e0fe766a
Import kernel-config infrastructure from BLFS and use it for kernel
configuration. Note that kernel-config.py is slightly different from
BLFS: we need role="nodump" for <screen> here.
A couple of the newer kernel options overflow past 80 columns on
the kernel page. It's not optimal, but insert newlines for these
options.
Also reorder the options to to same ordeer as they appear in
menuconfig and add some blank lines between major setions for
clarity.
Well, I forgot to create the man pages tarball as root, so if we don't
use --no-same-owner the man pages will be owned by UID 1000 :(.
Instead of regenerating the tarball again let's just fix this in the
book.
Update udev-lfs tarball to remove obsolete
cdrom rules and references to ISDN devices.
Update to wheel-0.41.0 (Python Module).
Update to tar-1.35.
Update to systemd-254.
Update to meson-1.2.0.
Update to linux-6.4.7.
Update to gcc-13.2.0.
Update to file-5.45.
I've seen two cases of invalid upstream "bug" reports this month because
the user has (mis)built LFS. Let's stop this before irritating the
upstream maintainers.
This partially reverts commit 1053282e5f.
There is actually only one test suite in LFS build even with -k, but on
my complete system there are many test failures with "-k". I guess some
tests depend on non-LFS packages.
The text change is reverted, but the command change is preserved as
generally we should use -k for any make check command known to fail.
This makes udevd send log entries to kmsg buffer and sysklogd will
pick them up.
Ideally we should use "syslog" here, but at the time udevd starts,
sysklogd has not started yet and /dev/log does not exist. So udevd
cannot open /dev/log and it will still use stderr as a fallback. We
cannot make udevd depending on sysklogd either, because it would cause a
circular dependency...
The Udev build dependencies are directly copied from systemd. Though
they might be unneeded for a Udev-only build, meson will check them
anyway. And I'm sure Jinja2 is really used.
In systemd dependencies Attr is dropped because Attr is not used
directly, it's just Acl needs Attr. OpenSSL is added because udevadm
links to libcrypto.
As "S" and "U" are closer, create a "systemd-udev" entity to simplify
the <phrase> choices.
In Util-linux, lsblk and findmnt links to libudev so it depends on
&systemd-udev;.
