From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm2-2.02.150: error running autotools
Date: Mon, 18 Apr 2016 19:33:56 +0200 [thread overview]
Message-ID: <57151A83.2000400@redhat.com> (raw)
In-Reply-To: <CAPD1+aPkA54SDUFf=OPzLwjE2p3QpcQgx8_Uh4dRYB+xmHX1rw@mail.gmail.com>
Dne 14.4.2016 v 12:24 Timo Gurr napsal(a):
> 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.
Hi
Well sorry for now - the current state of upstream configure.in file
does require newer version of autotools & autoconf & and few
other devel files installed.
So do not run autoconf and use already generated one - available
in both - git repo & released tar ball.
Once there will be enough time we may possibly fix it and make
it more backward compatible. Until that - use exiting generated
configure script.
Regards
Zdenek
next prev parent reply other threads:[~2016-04-18 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 10:24 [linux-lvm] lvm2-2.02.150: error running autotools Timo Gurr
2016-04-18 17:33 ` Zdenek Kabelac [this message]
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=57151A83.2000400@redhat.com \
--to=zkabelac@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.