Re: [PATCH] Reduce build verbosity when updating timestamp files

[Bart Schaefer <schaefer@brasslantern.com>]

On Jul 28,  9:46am, Peter Stephenson wrote:
}
} sometimes I build from the archive on a machine that doesn't have
} autoconf, and I run autoconf on a machine with access to the same disk.
} After running configure on the build machine, I have to make some
} timestamp file on the other machine to get he headers sorted out (only
} the first time after configure.ac changed).  So it's useful to see what
} that is.  However, I have a feeling I end up digging in the Makefile
} anyway.  There may be a better solution to this.

I do this all the time.  You need to touch these three files:

    config.h.in
    configure
    stamp-h.in

"make" will then proceed through re-running configure and rebuilding.

My current minor peeve is that config.modules keeps getting reset to the
default and I haven't figured out where.  I've taken to keeping a copy
as config.modules.local and manually copying it back to config.modules
from time to time.  I should automate that somehow, I suppose, but in
the rare event that a new module gets added that would stomp on it.