> What I suggest is to consider to start with something really small -- no more
> than 10 or 20 lines of changes *maximum* so that it is something that we can
> easily determine what the consequences will be.
Is the appended update suggestion small enough to be acceptable?
Regards,
Markus
>From f7ab6680b6adbda0e8390d144dad9edc17466fbf Mon Sep 17 00:00:00 2001
From: Markus Elfring <elfr...@users.sourceforge.net>
Date: Sun, 27 Dec 2009 18:07:16 +0100
Subject: [PATCH] Bug #1415: move check for autoconf version to the beginning of configuration templates
The macro "AC_PREREQ" was called too late.
---
bacula/autoconf/configure.in | 6 ++----
gui/autoconf/configure.in | 5 ++---
2 files changed, 4 insertions(+), 7 deletions(-)
diff --git a/bacula/autoconf/configure.in b/bacula/autoconf/configure.in
index 148a38c..71bcfef 100644
--- a/bacula/autoconf/configure.in
+++ b/bacula/autoconf/configure.in
@@ -2,6 +2,8 @@ dnl
dnl
dnl Process this file with autoconf to produce a configure script.
dnl
+dnl require a recent autoconf
+AC_PREREQ([2.61])
AC_INIT(src/version.h)
BUILD_DIR=`pwd`
cd ..
@@ -20,10 +22,6 @@ AC_SUBST(WIN32BUILDDIR)
AC_SUBST(WIN32MAINDIR)
AC_SUBST(WIN32TOPDIR)
-dnl require a recent autoconf
-AC_PREREQ(2.61)
-
-
dnl search for true and false programs.
AC_PATH_PROGS(TRUEPRG, true, :)
AC_PATH_PROGS(FALSEPRG, false, :)
diff --git a/gui/autoconf/configure.in b/gui/autoconf/configure.in
index 9de83b0..e0dff78 100644
--- a/gui/autoconf/configure.in
+++ b/gui/autoconf/configure.in
@@ -2,6 +2,8 @@ lal#
dnl#
dnl# Process this file with autoconf to produce a configure script.
dnl#
+dnl require a recent autoconf
+AC_PREREQ([2.59])
AC_INIT(autoconf/configure.in)
BUILD_DIR=`pwd`
cd ..
@@ -10,9 +12,6 @@ cd ${BUILD_DIR}
AC_SUBST(BUILD_DIR)
AC_CONFIG_AUX_DIR(${BUILD_DIR}/autoconf)
-dnl require a recent autoconf
-AC_PREREQ(2.13)
-
# ------------------------------------------
# Where to get Bacula source
--
1.6.5.7
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
