Anand Avati <anand.avati@xxxxxxxxx> wrote: > a) we upgrade the release build machine to use newer aclocal macros > > b) qualify geo-replication to work on python 3 and remove the check. Solution b is not enough: even if the configure script does not claim a specific version of python, it will still be unable to detect an installed python > 2.4 because it contains that: for am_cv_pathless_PYTHON in python python2 python2.4 python2.3 python2.2 python2.1 python2.0 none; do What about solution c? c) Tweak autogen.sh so that it patches generated configure and add the checks for python > 2.4 if they are missing: --- autogen.sh.orig 2012-05-15 03:22:48.000000000 +0200 +++ autogen.sh 2012-05-15 03:24:28.000000000 +0200 @@ -5,4 +5,6 @@ (libtoolize --automake --copy --force || glibtoolize --automake --copy --force) autoconf automake --add-missing --copy --foreign cd argp-standalone;./autogen.sh + +sed 's/for am_cv_pathless_PYTHON in python python2 python2.4/for am_cv_pathless_PYTHON in python python2 python3 python3.2 python3.1 python3.0 python2.7 2.6 python2.5 python2.4/' configure > configure.new && mv configure.new configure -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@xxxxxxxxxx
