Re: config.in

[Andreas Schwab <schwab@suse.de>]

Richard Stallman <rms@gnu.org> writes:

|>     |> Ordinary make has to fix the timestamps too, and touch the generated
|>     |> files, when you are building from CVS.  It should not attempt
|>     |> to run autoconf unless the user says `make configure' or `make config.in'.
|> 
|>     In neither cases the makefile caters for CVS timestamp issues at the
|>     moment.  Doing it right would require a script like gcc_update from the
|>     gcc repository, since make cannot know whether the timestamp difference
|>     comes from modifying configure.in or from CVS update.
|> 
|> If someone wants to "do it right", then by all means do so.
|> But unless and until that happens, we should do something simple:
|> Makefile.in should update configure and src/config.in
|> simply by touching them.

But I expect a simple "make" to update configure and config.in if I modify
configure.in.  If the makefile just uses touch then they stay out of
date.  This is bad.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."