[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: versioning config.cache

From: Dave Hart
Subject: Re: versioning config.cache
Date: Sat, 2 May 2009 09:43:07 +0000

Here's my latest revision of ntp_cacheversion.m4 with a bunch of shell
programming tweaks thanks to Eric, plus a change to not clear the
cache right after an empty cache file is created on the first run.

Thanks for the tips and comments.

Dave Hart

# NTP_CACHEVERSION(component, version)
# ------------------------------------
# compare this configure script's cache version stamp with the stamp
# saved by the prior run in config.cache.  If they differ, clear all
# cache variables to avoid using results cached with a script that
# is known to differ in a cache-invalidating manner.
# Note: use immediately following AC_INIT in, as clearing
# all _cv_ variables only makes sense immediately after loading, before
# use or modification.
# It is assumed that parent files which use
# AC_CONFIG_SUBDIR to invoke child files have used
# NTP_CACHEVERSION if any children do.  The top-level configure script
# will clear a previous cache lacking any saved cache version number,
# while children do not.  The reason is the children can rely on the
# parent having cleared any cache variables predating this mechanism.
# Therefore the child can rely on the config.cache generated by the
# parent on the first run despite not finding its version stamp
# previously saved.

    AC_BEFORE([$0], [AC_PROG_CC])dnl

    case "$ntp_cv_[$1]_cache_version" in
        # same version, good
        # No cache, predates ntp_cv_$1_cache_version, or is empty.
        case "$cache_file" in
            # Parent configure will have cleared cache once already.
            # This will misfire if a top-level configure is invoked
            # with --config-cache= value beginning with '../', is
            # there a better way to detect this configure was
            # invoked by a parent directory configure?
            # This appears to be the top-level configure file.
            # Do not clear the cache immediately after it is created
            # empty as it is noisy.  Differentiate a newly-created
            # config.cache from one predating the cache version
            # mechanism by looking for the first cached variable set
            # by Autoconf
            case "$ac_cv_path_install" in
                # presumably empty config.cache file
        # configure cache version mismatches config.cache version
    case "$ntp_cache_flush" in
        # Clear all *_cv_* variables except our various components'
        # ntp_cv_*_cache_version vars.
        c_varname_list=`set |
                        sed -n -e 's/=.*$//' \
                               -e '/ntp_cv_.*_cache_version/d' \
                               -e '/_cv_/p'
        for c_varname in $c_varname_list
            dnl use AS_UNSET([$c_varname]) eventually
            eval ${c_varname}=;  $as_unset $c_varname
        dnl use AS_UNSET([c_varname_list c_varname]) eventually
        c_varname_list=;  $as_unset c_varname_list c_varname
        AC_MSG_NOTICE([$cache_file saved by another version, ignored.])
        AC_MSG_NOTICE([configure script cache version: [$2]])
        c_version="${ntp_cv_[$1]_cache_version:-(no version found)}"
        AC_MSG_NOTICE([$cache_file version: $c_version])
        $as_unset c_version

    # save configure version in config.cache for next time

    $as_unset ntp_cache_flush

reply via email to

[Prev in Thread] Current Thread [Next in Thread]