Tom Lane wrote: > Bruce's suggestion of somehow checking this in the top Makefile is > a possibility, but even better would be if creating configure from > configure.in failed outright. We have an AC_PREREQ in there that > fails if autoconf is too old, but can we tighten it to also complain > if too new?
Yes: diff -ur ../cvs-pgsql/configure.in ./configure.in --- ../cvs-pgsql/configure.in 2007-11-16 21:25:10.000000000 +0100 +++ ./configure.in 2007-11-16 22:27:36.000000000 +0100 @@ -19,7 +19,7 @@ AC_INIT([PostgreSQL], [8.3beta3], [EMAIL PROTECTED]) -AC_PREREQ(2.59) +m4_if(m4_defn([m4_PACKAGE_VERSION]), [2.59], [], [m4_fatal([Autoconf version 2.59 is required])]) AC_COPYRIGHT([Copyright (c) 1996-2007, PostgreSQL Global Development Group]) AC_CONFIG_SRCDIR([src/backend/access/common/heaptuple.c]) AC_CONFIG_AUX_DIR(config) This appears to work with 2.53, 2.59, and 2.61, which are the ones that affect us at the moment. I can backpatch this all the way to 7.3 if desired. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
