When configuring GNU make 3.79.1, if I run "configure
--disable-nsec-timestamps" and then run "configure" again, the fact
that I disabled nsec timestamps in the earlier run is cached. This is
inconsistent with the other --disable options. Here's a patch.
2000-07-23 Paul Eggert <[EMAIL PROTECTED]>
* configure.in (enable_nsec_timestamps): Renamed from
make_cv_nsec_timestamps, since enable/disable options
shouldn't be cached.
===================================================================
RCS file: configure.in,v
retrieving revision 3.79.1.1
retrieving revision 3.79.1.2
diff -pu -r3.79.1.1 -r3.79.1.2
--- configure.in 2000/07/23 07:22:51 3.79.1.1
+++ configure.in 2000/07/23 07:44:05 3.79.1.2
@@ -50,11 +50,11 @@ dnl See if the user wants nsec timestamp
AC_ARG_ENABLE(nsec-timestamps,
[ --disable-nsec-timestamps disable use of sub-second timestamps],
- [make_cv_nsec_timestamps="$enableval"],
- [make_cv_nsec_timestamps="yes"])
+ [enable_nsec_timestamps="$enableval"],
+ [enable_nsec_timestamps="yes"])
jm_AC_TYPE_UINTMAX_T
-if test "x$make_cv_nsec_timestamps" != xno; then
+if test "x$enable_nsec_timestamps" != xno; then
AC_STRUCT_ST_MTIM_NSEC
AC_MSG_CHECKING([whether to use high resolution file timestamps])
AC_CACHE_VAL(make_cv_file_timestamp_hi_res, [
