lvm2-2.02.150: error running autotools

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

 



When running autotools on lvm2-2.02.150 I get the following error:

Using autoconf:2.5
Using automake:1.15
eautoreconf: running in
/var/tmp/paludis/build/sys-fs-lvm2-2.02.150/work/LVM2.2.02.150 ...
aclocal
aclocal-1.15: warning: autoconf input should be named 'configure.ac',
not 'configure.in'
autoconf
configure.in:1527: error: possibly undefined macro: AC_PYTHON_MODULE
     If this token and others are legitimate, please use m4_pattern_allow.
     See the Autoconf documentation.
* Failed Running autoconf !

Attached is a full build.log and the error can also be observed on our CI:
https://galileo.mailstation.de/jenkins/job/arbor/6248/console

System is a 64bit Exherbo installation, lvm2-2.02.137
configures/compiles und runs without any problems.

-- 
Timo Gurr
=== Running ebuild phase killold as root:root...
=== Starting builtin_killold
=== Done builtin_killold
=== Completed ebuild phase killold
=== Running ebuild phases init saveenv as paludisbuild:paludisbuild...
=== Starting builtin_init
=== Done builtin_init
=== Starting builtin_saveenv
=== Done builtin_saveenv
=== Completed ebuild phases init saveenv
--- No need to do anything for setup phase
=== Running ebuild phases loadenv unpack saveenv as paludisbuild:paludisbuild...
=== Starting builtin_loadenv
=== Done builtin_loadenv
=== Starting src_unpack
>>> Unpacking LVM2.2.02.150.tgz to /var/tmp/paludis/build/sys-fs-lvm2-2.02.150/work
tar zxf /var/cache/paludis/distfiles/LVM2.2.02.150.tgz --no-same-owner
=== Done src_unpack
=== Starting builtin_saveenv
=== Done builtin_saveenv
=== Completed ebuild phases loadenv unpack saveenv
=== Running ebuild phases loadenv prepare saveenv as paludisbuild:paludisbuild...
=== Starting builtin_loadenv
=== Done builtin_loadenv
=== Starting src_prepare
Using autoconf:2.5
Using automake:1.15
eautoreconf: running in /var/tmp/paludis/build/sys-fs-lvm2-2.02.150/work/LVM2.2.02.150 ...
aclocal
aclocal-1.15: warning: autoconf input should be named 'configure.ac', not 'configure.in'
autoconf
configure.in:1527: error: possibly undefined macro: AC_PYTHON_MODULE
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
 * Failed Running autoconf !

!!! ERROR in sys-fs/lvm2-2.02.150::arbor:
!!! In autotools_run_tool at line 594
!!! Failed Running autoconf !

!!! Call stack:
!!!    * autotools_run_tool (/var/tmp/paludis/build/sys-fs-lvm2-2.02.150/temp/loadsaveenv:594)
!!!    * eautoconf (/var/tmp/paludis/build/sys-fs-lvm2-2.02.150/temp/loadsaveenv:829)
!!!    * eautoreconf (/var/tmp/paludis/build/sys-fs-lvm2-2.02.150/temp/loadsaveenv:885)
!!!    * autotools_src_prepare (/var/tmp/paludis/build/sys-fs-lvm2-2.02.150/temp/loadsaveenv:615)
!!!    * src_prepare (/var/tmp/paludis/build/sys-fs-lvm2-2.02.150/temp/loadsaveenv:2725)
!!!    * exheres_internal_prepare (/usr/x86_64-pc-linux-gnu/libexec/paludis/exheres-0/src_prepare.bash:46)
!!!    * ebuild_main (/usr/x86_64-pc-linux-gnu/libexec/paludis/ebuild.bash:725)
!!!    * main (/usr/x86_64-pc-linux-gnu/libexec/paludis/ebuild.bash:748)

diefunc: making ebuild PID 9494 exit with error
die trap: exiting with error.
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

[Index of Archives]     [Gluster Users]     [Kernel Development]     [Linux Clusters]     [Device Mapper]     [Security]     [Bugtraq]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux