Bug 65325

Summary: Can't build realmd without systemd
Product: realmd Reporter: Jeremy Bicha <jbicha>
Component: GeneralAssignee: Stef Walter <stefw>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: buildlog

Description Jeremy Bicha 2013-06-04 03:53:06 UTC
Created attachment 80261 [details]
buildlog

I'm having trouble building realmd 0.14.2 without systemd on Ubuntu 13.10 Alpha.

I've tried passing --without-systemd-journal --without-systemd-unit-dir but it looks to me that the configure script fails if it can't autodetect a systemd unit directory or if one isn't specified.

Build log attached.
Comment 1 Stef Walter 2013-06-05 19:44:29 UTC
It seems like ./configure was not run with the --without-systemd-unit-dir argument:

...
configure: error: "Couldn't find systemd system unit directory"
checking systemd unit directory... ==> config.log <==
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by realmd configure 0.14.2, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  $ ./configure --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --libdir=${prefix}/lib/x86_64-linux-gnu --libexecdir=${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode --disable-dependency-tracking


The log seems to invoke configure twice. Once with, and once without --without-systemd-unit-dir.


Alternatively, if I'm thoroughly confused, could you point out where I've screwed up the configure.ac script?
Comment 2 Jeremy Bicha 2013-06-05 22:14:33 UTC
Thanks for the hint.

I finally figured things out. One problem was that we were using git tags to generate the tarball instead of just using the released tarballs.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.