mirror of
git://git.sv.gnu.org/autoconf
synced 2024-11-27 01:49:56 +08:00
40fa9edce6
The new feature of autoreconf --install installing config.guess, config.sub, and install-sh itself didn’t implement --force mode correctly; existing files would not be overwritten. The fix has two parts. If --force is in effect, we try to install everything that we can from the needed-auxfiles list *before* checking which of them already exist. But also, we don’t overwrite existing files unconditionally, even with --force; we only do so if the file we can install has a newer “timestamp” line than the copy at the destination. This is because Automake can also install all of the files we can install. Suppose someone is using autoconf 2.70 with a newly released automake 1.17; automake 1.17 will presumably ship with a newer config.guess than autoconf 2.70 did; that version should win. Fixes bug #110371. * bin/autoreconf.in (extract_time_stamp, our_aux_file_is_newer): New functions. (install_aux_file): If the destination exists, and our copy is not newer, do not overwrite it. (autoreconf_current_directory): When $force is true, attempt to install all needed aux files *before* scanning for missing aux files. (throughout): Remove extra \n from various error messages. * tests/torture.at (Missing auxiliary files (--force)): New test. |
||
---|---|---|
.. | ||
autoconf.as | ||
autoheader.in | ||
autom4te.in | ||
autoreconf.in | ||
autoscan.in | ||
autoupdate.in | ||
ifnames.in | ||
local.mk |