build-sys: "link" python _reader and pam_systemd against libsd-daemon-internal

The same old story as d3b9e0ff: those two use libsystemd-shared, and
in turn, some functions in libsystemd-shared use libsystemd-daemon.
The fact that *those* functions are used neither by the python modules
in question nor pam_systemd isn't always enough. Currently, I'm seeing
linking failures with -flto. The result of adding
libsystemd-daemon-internal to the list of linked libraries should be
harmless, with no change in size or final link requirements.
parent 11f22867
......@@ -3597,6 +3597,7 @@ pam_systemd_la_LIBADD = \
libsystemd-audit.la \
libsystemd-dbus.la \
libsystemd-shared.la \
libsystemd-daemon-internal.la \
$(PAM_LIBS)
pamlib_LTLIBRARIES = \
......@@ -3776,7 +3777,8 @@ _reader_la_LIBADD = \
$(PYTHON_LIBS) \
libsystemd-journal.la \
libsystemd-id128.la \
libsystemd-shared.la
libsystemd-shared.la \
libsystemd-daemon-internal.la
dist_pkgpyexec_PYTHON = \
src/python-systemd/journal.py \
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment