bug-autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AC_PATH_PROG ignores the variable


From: Alexandre Duret-Lutz
Subject: Re: AC_PATH_PROG ignores the variable
Date: Wed, 10 Nov 2004 10:24:40 +0100
User-agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)

>>> "Paul" == Paul Eggert <address@hidden> writes:

 Paul> Given the tradition, though, how about if we change
 Paul> AC_PATH_PROG to warn if the user specifies a value that
 Paul> is not an absolute file name?  After the warning, it can
 Paul> then go ahead and continue with the current behavior for
 Paul> now.  Later, after a transition period, we can change it
 Paul> to have the more-consistent behavior.

Would that affect AC_PATH_PROGS or not?

AC_PATH_PROGS is documented as leaving the value of the variable
unchanged if no program is found.  So AM_PATH_PYTHON does

      PYTHON=:
      AC_PATH_PROGS([PYTHON], _AM_PYTHON_INTERPRETER_LIST)

Now this code works exactly as documented: $PYTHON is still set
to ':' unless a python interpreter has been found in the list.
However as we have seen it is pure luck because AC_PATH_PROGS is
implemented in term of AC_PATH_PROG which ignore non-absolute
path values.

It's no big deal to change the above lines to 

      AC_PATH_PROGS([PYTHON], _AM_PYTHON_INTERPRETER_LIST, :)

and I don't really care if a new version of Autoconf causes
configure scripts generated by past versions of Automake to
complain (other might disagree, but I'm happy when people
upgrade).

I just wanted to point out that this warning is not necessary
something a user can fix.
-- 
Alexandre Duret-Lutz





reply via email to

[Prev in Thread] Current Thread [Next in Thread]