On 25/06/2019 17:20, DJ Lucas via blfs-dev wrote: > On June 25, 2019 7:44:54 AM CDT, Pierre Labastie via blfs-dev > <[email protected]> wrote: >> I've been building a full BLFS using the elogind branch for the last >> few days. >> Almost everything built OK. The first issue came with the ~840th >> package: >> smartmontools-7.0. During configure: >> ---- >> [...] >> checking for cap-ng.h... no >> checking systemd/sd-daemon.h usability... yes >> checking systemd/sd-daemon.h presence... yes >> checking for systemd/sd-daemon.h... yes >> checking for sd_notify in -lsystemd... no >> configure: error: libsystemd headers found but library is missing >> ---- >> Indeed, there is no libsystemd in either /lib or /usr/lib. But there is >> a >> /usr/lib/pkgconfig/libsystemd.pc, pointing to "-lelogind". the >> configure >> script does not use libsystemd.pc, but I have been able to build the >> package with: >> sed -e 's/\[systemd\]/[elogind]/' \ >> -e 's/-lsystemd/-lelogind/' \ >> -i configure.ac && >> autoreconf -fiv && >> ./configure ... >> >> I'm new to elogind, so there is maybe a better alternative. > > Bruce covered the easier way, but optionally, we could create a symlink for > libsystemd. A couple of distros do exactly that, but I was really trying to > avoid it (of course, I'd have preferred to avoid the PC symlink as well, but > that brought too many patches). Really the test should be fixed, I'll look > into upstreaming a test case for elogind at some point, but not sure about > timeframe for it to get into a release, same for Xorg (though the PC symlink > works for it). > >> >> Otherwise, there is a bunch of files installed in >> /usr/lib/systemd/user: >> ------- >> at-spi-dbus-bus.service >> emacs.service >> evolution-addressbook-factory.service >> evolution-calendar-factory.service >> evolution-source-registry.service >> evolution-user-prompter.service >> gnome-shell.service >> gnome-shell-wayland.target >> gnome-shell-x11.target >> thunar.service >> xfce4-notifyd.service >> ------- >> I guess those are missing some --with-systemduserunitdir switch or so. > > Yes, that is the correct fix (with =no). > > --DJ >
The build is finished now. No other issues during build. But I have not run tests (jhalfs does not do a good job at running them), I've found some issues with docs, which I am almost sure have nothing to do with elogind, and I'll have to test that everything runs... I have a question though. I've seen that consolekit is still in the elogind branch. Is it needed? If not, I suggest removing/archiving it (I've not built it). For the run tests, I'm not sure what to test. I may launch lightdm and try to run DE's from it, but even the systemd book has issues with some DE's, so I expect this one to have issues too (and also the present sysv book). Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
