Re: Is it me, or is it autotools being silly?
On 14/07/2021 11:55, Miro Hrončok wrote:
On 14. 07. 21 11:49, David Sommerseth wrote:
>
> Hi,
>
> So I'm running some builds for the openvpn3-linux project on Fedora Rawhide
> ... And we have this little line in configure.ac:
>
> AM_PATH_PYTHON([3.5],, [:])
>
> When ./configure runs, it reports:
>
> checking for python3 version... 3.1
>
> As a colleague said, mathematically this is correct. But that doesn't really
> help. Who/what is truncating Python 3.10 to 3.1? And how can that be fixed?
> Is someone already looking into this?
Is the configure script regenerated during build? Old consifure scripts tend to
do this.
No, the tarball is pre-generated - on an Ubuntu 20.04 box, iirc.
This was fixed e.g. in automake:
https://bugzilla.redhat.com/show_bug.cgi?id=1889732
But depending on how is the configure script created, might require fix in the
project itself.
Thanks! This was the pointer I needed and didn't find myself. I'll dig
into this.
I suggest to grep the configure script for 'sys.version' and
see what it does
with that value (e.g. sys.version[:3] is usually the problem).
Yupp, the configure script does contain sys.version[:3].
Thanks for quick and good feedback! I'll probably just add a re-run of
autoreconf before %configure in the .spec file to circumvent this for
now until we get automake upgraded.
--
kind regards,
David Sommerseth