[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#725569: libpam-unix2: FTBFS: configure.in:36: error: required file './compile' not found



Source: libpam-unix2
Version: 1:2.6-1
Severity: serious
Tags: jessie sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20131006 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh_testdir
> autoreconf -vf
> autoreconf: Entering directory `.'
> autoreconf: configure.in: not running autopoint: --install not given
> autoreconf: running: aclocal --force -I m4
> aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
> autoreconf: configure.in: tracing
> autoreconf: configure.in: not using Libtool
> autoreconf: running: /usr/bin/autoconf --force
> autoreconf: running: /usr/bin/autoheader --force
> autoreconf: running: automake --force-missing
> automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
> configure.in:97: warning: The 'AM_PROG_MKDIR_P' macro is deprecated, and its use is discouraged.
> configure.in:97: You should use the Autoconf-provided 'AC_PROG_MKDIR_P' macro instead,
> configure.in:97: and use '$(MKDIR_P)' instead of '$(mkdir_p)'in your Makefile.am files.
> configure.in:36: error: required file './compile' not found
> configure.in:36:   'automake --add-missing' can install 'compile'
> automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
> autoreconf: automake failed with exit status: 1
> make: *** [config.status] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/10/06/libpam-unix2_2.6-1_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.


Reply to: