Project

General

Profile

Housekeeping #2969

Updated by bill-auger about 3 years ago

some software may fail to build on a nonsystemd host if /usr/include/systemd is not populated - the case i noticed was 'icinga2' - the configure stage requires /usr/include/systemd/sd-daemon.h - elogind provides the systemd headers; but in another directory

<pre>
$ pkgfile sd-daemon.h
nonsystemd/elogind
libre/systemd-libsystemd
</pre>

elogind conflicts with systemd-libsystemd; so it should be a safe to add the symlink

Back