Re: Bug in AM_PATH_PYTHON ?

[Ralf Corsepius]

Am Fre, 2001-11-23 um 09.24 schrieb Patrick Guio:
> 
> 
> Dear all,
> I have updated my autoconf/automake/libtool package to
> aclocal (GNU automake) 1.5a
> autoconf (GNU Autoconf) 2.52g
> automake (GNU automake) 1.5a
> libtoolize (GNU libtool) 1.4c
> 
> and have written a short configure.in
> 
> AC_PREREQ(2.52g)
> AC_INIT
> AC_CONFIG_SRCDIR([hello.py.in])
> AC_PROG_MAKE_SET()
> AC_CANONICAL_TARGET()
> SHELL=${CONFIG_SHELL-/bin/sh}
> AC_SUBST(SHELL)
> AM_INIT_AUTOMAKE(hello,1.0)
> AM_PATH_PYTHON(2)
> AC_CONFIG_FILES([hello.py], [chmod +x hello.py])
> AC_CONFIG_FILES([Makefile])
> AC_OUTPUT
> 
> I am running RH7.2 and have several python versions. The default "python"
> is version 1.5 but there are in addition python2 and python2.1
> all of them coming from rpm's.
> The problem is that configure does not check all the possibilities as it
> should do:
Should it? I am not familiar enough with python, to be able to comment
on whether it should.

AFAIS, AM_PATH_PYTHON simply checks for the first program called 
python or python2.1 or python2.0 or python1.6 or python1.5 
and then tries to check if the PYTHON found matches the version passed
to AM_PATH_PYTHON.

Anyway, to work around your issue, presetting PYTHON from the
environment should work, eg.
PYTHON=phython2 ./configure

Ralf