From: Ruediger Pluem <rpluem@apache.org>
Date: Sun, 30 Nov 2008 11:23:26 +0000 (+0000)
Subject: * Enable the use of autoconf >= 2.62 without causing APR / APR-UTIL options
X-Git-Tag: 2.3.0~70
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=5f335094ee441d168d2ec7cae5aca7351a9e580d;p=apache

* Enable the use of autoconf >= 2.62 without causing APR / APR-UTIL options
  passed to the configure script issue warnings about unknown options.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@721796 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/configure.in b/configure.in
index e13e051882..5a98367c50 100644
--- a/configure.in
+++ b/configure.in
@@ -18,6 +18,15 @@ sinclude(build/find_apr.m4)
 sinclude(build/find_apu.m4)
 sinclude(acinclude.m4)
 
+dnl Later versions of autoconf (>= 2.62) by default cause the produced
+dnl configure script to emit at least warnings when it comes across unknown
+dnl command line options. These versions also have the macro
+dnl AC_DISABLE_OPTION_CHECKING defined which turns this off by default.
+dnl We want to have this turned off here since our configure calls can
+dnl contain options for APR / APR-UTIL configure that are unknown to us.
+dnl So avoid confusing the user by turning this off. See also PR 45221.
+ifdef([AC_DISABLE_OPTION_CHECKING], [AC_DISABLE_OPTION_CHECKING])
+
 dnl XXX we can't just use AC_PREFIX_DEFAULT because that isn't subbed in
 dnl by configure until it is too late.  Is that how it should be or not?
 dnl Something seems broken here.