We do use --enable-compat-libs. libsystemd-daemon.so.0 doesn't exist any
more as nothing in Ubuntu uses it any more. But as I said you can build
software whose ./configure is still checking for the old split out
libraries with libsystemd-login-dev and friends (and then it will end up
being linked
libsystemd-daemon.so.0 is a missing shared object that has pkgconfig
support and headers (sd-daemon.h). Why would all the dev support be
there, when the Shared Object is no where to be found?
please package this shared object. Why can Fedora 22/23 get this right,
but the Ubuntu+1 team can not?
Marty claims I can build it and I've seen freedesktop.org posts says I
can too if I have sd-daemon.c
Is sd-daemon.c the true source? I can't find this in any Vivid *.dsc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Looking at system-219 from upstream now.
In order to build libsystemd-daemon.so.0, you need to configure like this:
./configure --enable-compat-libs
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
here is the upstream tree
http://cgit.freedesktop.org/systemd/systemd/plain/src/libsystemd/
sd-daemon.c is the source of interest
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
You can build that using libsystemd-login-dev, they provide
compatibility shims for the obsolete libsystemd-logind0 (and similar)
libraries.
** Changed in: systemd (Ubuntu)
Status: New = Won't Fix
** Changed in: systemd (Ubuntu)
Status: Won't Fix = Invalid
--
You received this
*** This is an automated message ***
This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu. As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports
7 matches
Mail list logo
