diff options
author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2013-05-01 22:30:54 -0400 |
---|---|---|
committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2013-05-02 22:55:38 -0400 |
commit | b5fafdf63f72b07ff646a898ef94a81643b8d1a7 (patch) | |
tree | 1f67cac69e13332562107f82eafaadab08176d41 /test/h.service | |
parent | 11f22867f9cdbfc6656905861090cded91a41bd7 (diff) |
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.
Diffstat (limited to 'test/h.service')
0 files changed, 0 insertions, 0 deletions