Created attachment 127025 [details] build log Building dbus with autotools from git master branch fails with the following messages. Last lines of build log: [ 105s] libtoolize: copying file `m4/ltsugar.m4' [ 105s] libtoolize: copying file `m4/ltversion.m4' [ 105s] libtoolize: copying file `m4/lt~obsolete.m4' [ 117s] configure.ac:68: installing 'build-aux/compile' [ 117s] configure.ac:15: installing 'build-aux/config.guess' [ 117s] configure.ac:15: installing 'build-aux/config.sub' [ 117s] configure.ac:20: installing 'build-aux/install-sh' [ 117s] configure.ac:20: installing 'build-aux/missing' [ 117s] configure.ac:82: installing 'build-aux/tap-driver.sh' [ 117s] bus/Makefile.am: installing 'build-aux/depcomp' [ 119s] configure.ac:343: error: Unexpanded AX_ macro found. Please install GNU autoconf-archive [ 119s] If this token and others are legitimate, please use m4_pattern_allow. [ 119s] See the Autoconf documentation. [ 119s] autoconf failed - version 2.5x is probably required [ 119s] error: Bad exit status from /var/tmp/rpm-tmp.7Mdi87 (%build) package autoconf-archive has been installed and autoconf is version 2.69 The full log is appended.
> [ 34s] [85/136] cumulate autoconf-archive-2013.06.09-4.1.2 That's... not recent. Sorry, your autoconf-archive is about 2 years too old to build the latest from git.
If you are building in an environment that does not have a somewhat recent autoconf-archive, please use tarball releases, or "make dist" in a more recent environment and use the result in your older environment. This will copy the current m4 macros from autoconf-archive into the dist tarball. In particular, the latest git snapshot from the development branch is not something that is intended to be deployed in a "LTS" environment.
(In reply to Simon McVittie from comment #2) > If you are building in an environment that does not have a somewhat recent > autoconf-archive, please use tarball releases, or "make dist" in a more > recent environment and use the result in your older environment. This will > copy the current m4 macros from autoconf-archive into the dist tarball. > > In particular, the latest git snapshot from the development branch is not > something that is intended to be deployed in a "LTS" environment. Thanks for this info. I was not aware that dbus autoconf depends on additional dependencies. There is an unstable dbus cross build using autotools on obs to catch any package building regressions in development branch which may also affect stable branch in future.
(In reply to Ralf Habacker from comment #3) > Thanks for this info. I was not aware that dbus autoconf depends on > additional dependencies. BTW: It looks that this autoconf-archive is a new dependency which affects package building on all supported platforms.
(In reply to Ralf Habacker from comment #4) > BTW: It looks that this autoconf-archive is a new dependency which affects > package building on all supported platforms. """ D-Bus 1.11.4 (2016-08-15) == The “copper pickaxe” release. Dependencies: • Building from git (but not from tarballs) now requires macros from the GNU Autoconf Archive, for example the autoconf-archive package in Debian or Fedora derivatives. """ That doesn't specifically say so, but it requires a somewhat recent autoconf-archive; versions from 2013 are not going to be suitable. Because of the way Autoconf works, this new dependency only affects builds from git or using `autoreconf`) (it does not affect ordinary builds from tarballs). If you're autobuilding the unstable development version of dbus, please autobuild it on a recent development version of whatever base environment you're using. From your log it seems you're basing on openSUSE 13.2; openSUSE Leap would probably be a better platform for building the latest versions.
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.