I updated maint/updatefiles to allow 2.64, but autoreconf failed on src/mpl. It seem 2.64's autoconf has problem with mpl's consecutive use of AS_HELP_STRINGs. /home/chan/mpich_work/mpich2/src/mpl> autoreconf -vif autoreconf: Entering directory `.' autoreconf: configure.in: not using Gettext autoreconf: running: aclocal --force -I confdb autoreconf: configure.in: tracing autoreconf: running: libtoolize --copy --force libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `confdb'. libtoolize: copying file `confdb/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `confdb'. libtoolize: copying file `confdb/libtool.m4' libtoolize: copying file `confdb/ltoptions.m4' libtoolize: copying file `confdb/ltsugar.m4' libtoolize: copying file `confdb/ltversion.m4' libtoolize: copying file `confdb/lt~obsolete.m4' autoreconf: running: /home/chan/autoconf/2.64/bin/autoconf --force configure:1510: error: possibly undefined macro: _m4_text_wrap_word If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. However autoconf-2.65 (and of course 2.63) works OK on the file, but output of configure --help on the valgrind option does not look quite right.... --without-valgrind to disable valgrind support (such as because of version issues) --with-valgrind=PATH use valgrind headers installed in PATH [default], [is], [yes] Maybe there is a bug... A.Chan