From edfff4b06ffcb9924885e4790792093349cf2585 Mon Sep 17 00:00:00 2001 From: Sam Hartman Date: Tue, 19 Oct 2010 19:57:56 +0000 Subject: [PATCH] configure.in: don't force use of cache Back when hardware was slower and we had lots and lots of imakefile-like configure scripts, forcing the use of config.cache made sense for performance reasons. Now that we have one configure script and we build on modern hardware, config.cache just introduces errors as you are debugging changes to the configure script. This commit stops second guessing autoconf's cache handling. git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@24468 dc483132-0cff-0310-8789-dd5450dbe970 --- src/configure.in | 7 ------- 1 file changed, 7 deletions(-) diff --git a/src/configure.in b/src/configure.in index 8d6bb8277..592bdd824 100644 --- a/src/configure.in +++ b/src/configure.in @@ -1,11 +1,4 @@ K5_AC_INIT([aclocal.m4]) -# -# autoconf 2.49 defaults to a /dev/null cache file, which is what we -# do not want for performance reasons. -if test "x$cache_file" = "x/dev/null"; then - cache_file=./config.cache - AC_CACHE_LOAD -fi CONFIG_RULES KRB5_VERSION=K5_VERSION -- 2.26.2