simple configure.ac, but any configure.ac using AM_PATH_PYTHON() is enough AC_INIT() AM_PATH_PYTHON() AC_CONFIG_FILES(foo.in) AC_OUTPUT
output in jaunty: $ ./configure checking for python... /usr/bin/python checking for python version... 2.6 checking for python platform... linux2 checking for python script directory... /usr/lib/python2.6/dist-packages checking for python extension module directory... /usr/lib/python2.6/dist-packages configure: creating ./config.status
correct behaviour is not to expand the variables and keeping the ${prefix} and ${exec_prefix} macros
simple configure.ac, but any configure.ac using AM_PATH_PYTHON() is enough FILES(foo. in)
AC_INIT()
AM_PATH_PYTHON()
AC_CONFIG_
AC_OUTPUT
output in jaunty: python2. 6/dist- packages python2. 6/dist- packages
$ ./configure
checking for python... /usr/bin/python
checking for python version... 2.6
checking for python platform... linux2
checking for python script directory... /usr/lib/
checking for python extension module directory... /usr/lib/
configure: creating ./config.status
correct behaviour is not to expand the variables and keeping the ${prefix} and ${exec_prefix} macros