Hi Yogesh, The error means that PKG_CHECK_MODULES failed to get systemd for configure. So pkg-config did not work for it. Perhaps the devel (or -dev) package is not installed for it? Or pkg-config is not?
The systemctl commands work anyway. The integration signals server readiness via the systemd API to systemd. But stuff like start and stop of the server is going to work fine, also without that type of (more detailed) status information available. Of course that needs the systemd unit, which is not installed by Unbound; that is something for the packager (because everyone has a different set up), there are examples in contrib/ dir of the source, or find packages for your system for how to do that part. Best regards, Wouter On 1/30/19 10:22 AM, Yogesh Sharma via Unbound-users wrote: > Hi Team, > > I am trying to compile unbound 1.8.3 with enable-systemd. Though we have > libsystemd installed, I am getting error *configure: error: systemd > enabled but libsystemd not found* > > Could you please help knowing the cause. > > Also, by enabling systemd, does it means it is going to enable systemctl > commands by having a systemd unit. > > Command: ./configure --enable-systemd --enable-cachedb --with-pthreads > --with-libhiredis > > # rpm -ql systemd-libs-219-62.el7_6.3.x86_64 > /usr/lib64/libnss_myhostname.so.2 > /usr/lib64/libnss_mymachines.so.2 > /usr/lib64/libsystemd-daemon.so.0 > /usr/lib64/libsystemd-daemon.so.0.0.12 > /usr/lib64/libsystemd-id128.so.0 > /usr/lib64/libsystemd-id128.so.0.0.28 > /usr/lib64/libsystemd-journal.so.0 > /usr/lib64/libsystemd-journal.so.0.11.5 > /usr/lib64/libsystemd-login.so.0 > /usr/lib64/libsystemd-login.so.0.9.3 > /usr/lib64/libsystemd.so.0 > /usr/lib64/libsystemd.so.0.6.0 > /usr/lib64/libudev.so.1 > /usr/lib64/libudev.so.1.6.2 > /usr/lib64/security/pam_systemd.so > > > /Thanks & Regards, > > Yogesh Sharma > /
signature.asc
Description: OpenPGP digital signature
