eventlog version 0.2.12-1 failed to build on armel
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:/
Direct link to the build log: https:/
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/
/usr/share/
tests/Makefile.am: installing `./compile'
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
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-
Related branches
tags: | removed: arm-porting-queue |
Changed in eventlog (Debian): | |
status: | Unknown → New |
Changed in eventlog (Ubuntu): | |
assignee: | nobody → Colin Watson (cjwatson) |
Changed in eventlog (Debian): | |
status: | New → Fix Released |
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