On Wed, 2 Jan 2019 21:17:43 +0100 Michael Biebl <bi...@debian.org> wrote: > Hi Simon > > On Tue, 4 Dec 2018 21:18:07 +0000 Simon McVittie <s...@debian.org> wrote: > > Package: libsystemd-dev > > Version: 239-14 > > Severity: wishlist > > > > libsystemd-dev doesn't provide a static library. Is this deliberate? > > More or less. Upstream by default does not build any static libraries > and this needs to be turned on explicitly. > > I quickly tested a build with > -Dstatic-libsystemd=true -Dstatic-libudev=true > which results in loads of warnings from dpkg-shlibdeps like this: > > strip: > debian/libsystemd-dev/lib/x86_64-linux-gnu/stObSVqO/src_libsystemd_sd-bus_bus-common-errors.c.o: > plugin needed to handle lto object > > > The size of the libudev-dev and libsystem-dev package exploded: > $ du -hs debian/libsystemd-dev/lib/x86_64-linux-gnu/libsystemd.a > debian/libudev-dev/lib/x86_64-linux-gnu/libudev.a > 14M debian/libsystemd-dev/lib/x86_64-linux-gnu/libsystemd.a > 18M debian/libudev-dev/lib/x86_64-linux-gnu/libudev.a > > I haven't actually test if the resulting .a files can be used to > successfully link a program statically. At the very least we'd have to > add an autopkgtest to regularly test this as this is not something which > is used and tested by upstream. > > This and the issue with the huge .a files make me a bit concerned > enabling the build of the static libraries. >
Simon, have you tried building systemd with -Dstatic-libsystemd=true -Dstatic-libudev=true ? Does this produce something useful? Upstream doesn't seem to be too keen on supporting static builds, so if we divert here downstream, I'd be interested if there is actual demand from users of such a libsystemd.a or if this all mostly hyphothetical. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
