Bug 48484 - tests/mocklibc needs autoreconf to be run before jhbuild?
Summary: tests/mocklibc needs autoreconf to be run before jhbuild?
Status: RESOLVED MOVED
Alias: None
Product: PolicyKit
Classification: Unclassified
Component: daemon (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: David Zeuthen (not reading bugmail)
QA Contact: David Zeuthen (not reading bugmail)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-09 14:52 UTC by Federico Mena-Quintero
Modified: 2018-08-20 21:38 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Federico Mena-Quintero 2012-04-09 14:52:04 UTC
I was doing a jhbuild on a fresh environment (nothing built or installed before), and polkit failed here:

*** Configuring polkit *** [1/45]
./autogen.sh --prefix /home/federico/jhbuild/install --libdir '/home/federico/jhbuild/install/lib'  --disable-static
Running autoreconf on test/mocklibc ...
src/Makefile.am:2: Libtool library used but `LIBTOOL' is undefined
src/Makefile.am:2:   The usual way to define `LIBTOOL' is to add `LT_INIT'
src/Makefile.am:2:   to `configure.ac' and run `aclocal' and `autoconf' again.
src/Makefile.am:2:   If `LT_INIT' is in `configure.ac', make sure
src/Makefile.am:2:   its definition is in aclocal's search path.
autoreconf: automake failed with exit status: 1

I went into polkit/tests/mocklibc and ran "autoconf -f -i".  It complained a little, but then just running jhbuild again worked fine.

Maybe polkit/autogen.sh needs to do something about tests/mocklibc before running autofoo on the whole source tree?
Comment 1 David Zeuthen (not reading bugmail) 2012-04-11 07:18:14 UTC
I think we just need to make mocklibc not have its own configure.ac and so on - I mean, it's just a couple of C files, it's overkill to make it have its own build system.
Comment 2 GitLab Migration User 2018-08-20 21:38:27 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/polkit/polkit/issues/56.


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.