Bug#713303: dxflib: FTBFS: automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'

Lucas Nussbaum lucas at lucas-nussbaum.net
Sat Jun 22 12:45:27 UTC 2013


Source: dxflib
Version: 2.2.0.0-8
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> dh build --with autoreconf
>    dh_testdir
>    dh_autoreconf
> aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
> libtoolize: putting auxiliary files in `.'.
> libtoolize: copying file `./ltmain.sh'
> libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.in and
> libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
> libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
> automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
> configure.in:8: installing './missing'
> automake: warnings are treated as errors
> automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
> /usr/share/automake-1.13/am/ltlibrary.am: warning: 'libdxflib.la': linking libtool libraries using a non-POSIX
> /usr/share/automake-1.13/am/ltlibrary.am: archiver requires 'AM_PROG_AR' in 'configure.in'
> Makefile.am:22:   while processing Libtool library 'libdxflib.la'
> Makefile.am: installing './depcomp'
> autoreconf: automake failed with exit status: 1
> dh_autoreconf: autoreconf -f -i returned exit code 1
> make: *** [build] Error 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/20/dxflib_2.2.0.0-8_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



More information about the debian-science-maintainers mailing list