On Mon, 1 Sep 2014 13:24:20 +0200 Jakub Wilk <[email protected]> wrote: > * Ritesh Raj Sarraf <[email protected]>, 2014-09-01, 16:20: > >>>>cc -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security > >>>>-D_FORTIFY_SOURCE=2 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 > >>>>-fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused > >>>>-Wstrict-prototypes -fPIC -DLIB_STRING=\"lib\" -DLIBDM_API_FLUSH > >>>>-D_GNU_SOURCE -DLIBDM_API_COOKIE -DUSE_SYSTEMD=208 -c -o uxsock.o uxsock.c > >>>>uxsock.c:20:31: fatal error: systemd/sd-daemon.h: No such file or > >>>>directory > >>>> #include <systemd/sd-daemon.h> > >>>> ^ > >>>>compilation terminated. > >>>>../Makefile.inc:57: recipe for target 'uxsock.o' failed > >>>>make[2]: *** [uxsock.o] Error 1 > > > >I fixed this one by adding a build-dep to systemd dev library. But for > >some reason, the build is failing on all architectures. But the same > >builds fine in my pbuilder. Any help ?? > > The error is: > | dh_install: multipath-tools missing files (/usr/lib/systemd/system/*), > aborting > | make: *** [install] Error 2 > > Upstream build system uses systemctl(1) to decide whether or not build > with systemd support enabled. Unsurprisingly, systemctl does not exist > in buildd chroots. You should either add "systemd" to build-depends, or > fix the build system to be less non-deterministic. >
For completeness sake, this is the relevant makefile section:
ifndef SYSTEMD
ifeq ($(shell systemctl --version > /dev/null 2>&1 && echo 1), 1)
SYSTEMD = $(shell systemctl --version 2> /dev/null |
sed -n 's/systemd \([0-9]*\)/\1/p')
endif
endif
So you might want to use
$(MAKE) $(OPTFLAGS) LIB=lib SYSTEMD=1
in your debian/rules to get a more reliable build result.
--
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
