Peter Eisentraut <peter_e@gmx.net> writes:
>> Huh? There is only one config.status, and it'll update all its output
>> files whenever it runs. I don't see the issue.
> The rules in the makefiles cause config.status to only update the file
> that triggered the rule. E.g.,
> GNUmakefile: GNUmakefile.in $(top_builddir)/config.status
> CONFIG_FILES=$@ CONFIG_HEADERS= ./config.status
> (Yes, this interface is incredibly stupid.)
Uh, why don't we just make it generate all its output files each time?
regards, tom lane