Re: [PATCH 2/2] configure.ac: consistently require the same Python version

Thomas Uhle <thomas.uhle-cl+VPiYnx/[email protected]> Thu, 28 May 2026 13:37:32 +0200
Newsgroups gmane.comp.hardware.lirc
Message-ID <[email protected]>
On Thu, 28 May 2026, Doron Behar wrote:

> [...]
>
> +m4_define([PYTHON_MIN_VERSION], [3.7])
> # Try the 'm' (malloc/abiflags) version first, fallback to standard python3
> -PKG_CHECK_MODULES([PYTHON], [python3m >= 3.7], [pkg_cv_python_name="python3m"], [
> -    PKG_CHECK_MODULES([PYTHON], [python3 >= 3.7], [pkg_cv_python_name="python3"], [
> -        AC_MSG_WARN([No python package found >= 3.1 (missing devel package?)])
> +PKG_CHECK_MODULES([PYTHON], [python3m >= [PYTHON_MIN_VERSION,] [pkg_cv_python_name="python3m"], [
> +    PKG_CHECK_MODULES([PYTHON], [python3 >= [PYTHON_MIN_VERSION,] [pkg_cv_python_name="python3"], [
> +        AC_MSG_WARN([No python package found >= [PYTHON_MIN_VERSION] (missing devel package?)])

Looks like mismatched brackets ...  Have you tested these changes?

Best regards,

Thomas Uhle