[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#30616: automake-1.16: aclocal is unable to process AM_PATH_PYTHON wi
From: |
Thomas Deutschmann |
Subject: |
bug#30616: automake-1.16: aclocal is unable to process AM_PATH_PYTHON with variable as value |
Date: |
Mon, 26 Feb 2018 23:14:39 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Thunderbird/52.6.0 |
Hi,
the problem is line
> m4_define_default([am_py_min_ver], m4_ifval([$1], [$1], [2.0]))
Code like
> AM_PATH_PYTHON([$PYTHON_VERSION])
will result in "am_py_min_ver" set to "$PYTHON_VERSION" which is
obviously not a valid value. I.e. the passed argument isn't expanded
when used in the macro.
However, I don't understand why we need the dynamic in the list
creation. From my understanding, GNU Pyconfigure, the implementation
source, provided a macro which requires to set lower and upper bound
("PC_INIT([MIN_VER], [MAX_VER])"). But given that the AM_PATH_PYTHON
public function wasn't changed, we don't need to (better: cannot)
generate the list dynamically. So I would recommend to change this line to
> m4_define_default([am_py_min_ver], [2.0])
This fixes the problem in cryptsetup, util-linux and PythonMagick for
me. And the check still works. I.e. when I remove the minimum Python
version or newer on my system, configure fails like expected.
--
Regards,
Thomas Deutschmann / Gentoo Linux Developer
C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5