Travis Shirk <[EMAIL PROTECTED]> writes:
|> Hello,
|>
|> I'm writing a function to find python2, and I did not get far before
|> noticing this:
|>
|> creating cache ./config.cache
|> checking for python2... /usr/bin/python2
|> checking for python... (cached) /usr/bin/python2
|> updating cache ./config.cache
|>
|> Here's the function:
|>
|> AC_DEFUN([ACX_CHECK_PYTHON2], [
|> PYTHON=""
|> for p in python2 python; do
|> AC_PATH_PROG([PYTHON], [${p}])
|> done
|> ])
|>
|> So, why is the first discovery of python2 getting the cache result for the
|> check for python.
Because the cache value is keyed on the first parameter of AC_PATH_PROG.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 N�rnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
