eventlog version 0.2.12-1 failed to build on armel

Bug #791265 reported by Ricardo Salveti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eventlog (Debian)
Fix Released
Unknown
eventlog (Ubuntu)
Fix Released
Undecided
Colin Watson

Bug Description

eventlog version 0.2.12-1 failed to build on armel
Link to failed build: https://launchpad.net/ubuntu/+source/eventlog/0.2.12-1/+build/2465818

Direct link to the build log: https://launchpad.net/ubuntu/+source/eventlog/0.2.12-1/+build/2465818/+files/buildlog_ubuntu-oneiric-armel.eventlog_0.2.12-1_FAILEDTOBUILD.txt.gz

This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 414 lines into the build log:

src/Makefile.am:2:
src/Makefile.am:2: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/Makefile.am:2: to `configure.in' and run `aclocal' and `autoconf' again.
src/Makefile.am: installing `./depcomp'
/usr/share/automake-1.7/am/depend2.am: am__fastdepCC does not appear in AM_CONDITIONAL
/usr/share/automake-1.7/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL
tests/Makefile.am: installing `./compile'
/usr/share/automake-1.7/am/depend2.am: am__fastdepCC does not appear in AM_CONDITIONAL
/usr/share/automake-1.7/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL
/usr/share/automake-1.7/am/depend2.am: am__fastdepCC does not appear in AM_CONDITIONAL
/usr/share/automake-1.7/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL
/usr/share/automake-1.7/am/depend2.am: am__fastdepCC does not appear in AM_CONDITIONAL
/usr/share/automake-1.7/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL
make: *** [build-stamp] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
******************************************************************************
Build finished at 20110511-1935
FAILED [dpkg-buildpackage died]
Purging chroot-autobuild/build/buildd/eventlog-0.2.12

Tags: ftbfs

Related branches

Revision history for this message
Dr. David Alan Gilbert (davidgil-uk) wrote :

First error doesn't look very ARM specific:

autoheader: error: AC_CONFIG_HEADERS not found in configure.in
configure.in:26: error: possibly undefined macro: AM_INIT_AUTOMAKE
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.in:33: error: possibly undefined macro: AM_CONFIG_HEADER
configure.in:47: error: possibly undefined macro: AM_PROG_LIBTOOL
Useless use of /d modifier in transliteration operator at /usr/bin/automake line 5985.
configure.in: no proper invocation of AM_INIT_AUTOMAKE was found.
configure.in: You should verify that configure.in invokes AM_INIT_AUTOMAKE,
configure.in: that aclocal.m4 is present in the top-level directory,
configure.in: and that aclocal.m4 was recently regenerated (using aclocal).
configure

tags: removed: arm-porting-queue
Changed in eventlog (Debian):
status: Unknown → New
Revision history for this message
Colin Watson (cjwatson) wrote :

Yes, it only happened to hit armel+powerpc and not other architectures because they were unlucky about when a new version of libtool got build.

Colin Watson (cjwatson)
Changed in eventlog (Ubuntu):
assignee: nobody → Colin Watson (cjwatson)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package eventlog - 0.2.12-1ubuntu1

---------------
eventlog (0.2.12-1ubuntu1) oneiric; urgency=low

  * Upgrade to current automake (LP: #791265).
 -- Colin Watson <email address hidden> Tue, 23 Aug 2011 13:34:44 +0100

Changed in eventlog (Ubuntu):
status: New → Fix Released
Changed in eventlog (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.