From: Timo Gurr <timo.gurr@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] lvm2-2.02.150: error running autotools
Date: Thu, 14 Apr 2016 12:24:26 +0200 [thread overview]
Message-ID: <CAPD1+aPkA54SDUFf=OPzLwjE2p3QpcQgx8_Uh4dRYB+xmHX1rw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
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
[-- Attachment #2: sys-fs_lvm2-2.02.150.txt --]
[-- Type: text/plain, Size: 2693 bytes --]
^[[35;01m===^[[0m Running ebuild phase killold as root:root...
^[[35;01m===^[[0m Starting builtin_killold
^[[35;01m===^[[0m Done builtin_killold
^[[35;01m===^[[0m Completed ebuild phase killold
^[[35;01m===^[[0m Running ebuild phases init saveenv as paludisbuild:paludisbuild...
^[[35;01m===^[[0m Starting builtin_init
^[[35;01m===^[[0m Done builtin_init
^[[35;01m===^[[0m Starting builtin_saveenv
^[[35;01m===^[[0m Done builtin_saveenv
^[[35;01m===^[[0m Completed ebuild phases init saveenv
--- No need to do anything for setup phase
^[[35;01m===^[[0m Running ebuild phases loadenv unpack saveenv as paludisbuild:paludisbuild...
^[[35;01m===^[[0m Starting builtin_loadenv
^[[35;01m===^[[0m Done builtin_loadenv
^[[35;01m===^[[0m 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
^[[35;01m===^[[0m Done src_unpack
^[[35;01m===^[[0m Starting builtin_saveenv
^[[35;01m===^[[0m Done builtin_saveenv
^[[35;01m===^[[0m Completed ebuild phases loadenv unpack saveenv
^[[35;01m===^[[0m Running ebuild phases loadenv prepare saveenv as paludisbuild:paludisbuild...
^[[35;01m===^[[0m Starting builtin_loadenv
^[[35;01m===^[[0m Done builtin_loadenv
^[[35;01m===^[[0m 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.
^[[31;01m*^[[0m 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.
next reply other threads:[~2016-04-14 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 10:24 Timo Gurr [this message]
2016-04-18 17:33 ` [linux-lvm] lvm2-2.02.150: error running autotools Zdenek Kabelac
2016-04-18 18:16 ` Alasdair G Kergon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPD1+aPkA54SDUFf=OPzLwjE2p3QpcQgx8_Uh4dRYB+xmHX1rw@mail.gmail.com' \
--to=timo.gurr@gmail.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).