Bug 70269 - build: configure.ac requires automake >= 1.12, sync autogen.sh
Summary: build: configure.ac requires automake >= 1.12, sync autogen.sh
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: logger (show other bugs)
Version: git master
Hardware: All All
: medium major
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-08 07:35 UTC by Alban Browaeys
Modified: 2013-11-07 18:26 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
build: configure.ac requires automake >= 1.12, sync autogen.sh (1.21 KB, patch)
2013-10-08 07:35 UTC, Alban Browaeys 		Details | Splinter Review
View All

Description Alban Browaeys 2013-10-08 07:35:51 UTC 
Created attachment 87263 [details] [review]
build: configure.ac requires automake >= 1.12, sync  autogen.sh

autogen.sh uses automake 1.11 if available but configure.ac then
fails as too old an automake for it since commit a81174c5 .

Failure is:
main::scan_file() called too early to check prototype at /usr/bin/aclocal-1.11 line 643.
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
main::scan_file() called too early to check prototype at /usr/bin/aclocal-1.11 line 643.
configure.ac:88: require Automake 1.12, but have 1.11.6
autoreconf: automake-1.11 failed with exit status: 1
Comment 1 Simon McVittie 2013-11-07 18:26:31 UTC 
I'd prefer to just stop overriding the version, tbh.

Fixed in git for 0.9.0, by cherry-picking patches from the branch that was merged into telepathy-glib 0.99.x.

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.