Zack Weinberg 07130c3e48 autom4te: always update the output file, even if it hasn’t changed ... Automake generates a Makefile rule for regenerating the configure script, that relies on an invocation of ‘autoconf’ always bumping the timestamp on the configure script, even if it hasn’t changed. The patch to make autom4te update the output file atomically (1725c94714) broke this. Fixes several failures in automake’s test suite. * bin/autom4te.in (handle_output): Always call update_file with force=1. * tests/tools.at (autoconf: timestamp changes): New test.		2020-12-29 15:33:33 -05:00
..
autoconf.as	Manually sync ChannelDefs.pm from automake.	2020-09-22 15:46:42 -04:00
autoheader.in	Disable all warnings when running autoconf as a subprocess.	2020-09-22 15:46:43 -04:00
autom4te.in	autom4te: always update the output file, even if it hasn’t changed	2020-12-29 15:33:33 -05:00
autoreconf.in	autoreconf --install --force: replace install-sh with no timestamp	2020-12-08 10:34:31 -05:00
autoscan.in	Disable all warnings when running autoconf as a subprocess.	2020-09-22 15:46:43 -04:00
autoupdate.in	Manually sync ChannelDefs.pm from automake.	2020-09-22 15:46:42 -04:00
ifnames.in	Fatalize all warnings in Perl code.	2020-08-31 13:15:46 -04:00
local.mk	maint: make update-copyright	2020-01-01 11:45:50 -08:00