Reflect the 'configure.in' -> 'configure.ac' rename throughout

In README, code comments, and auxiliary files.

Copyright-paperwork-exempt: yes
Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com>
This commit is contained in:
Stefano Lattarini
2013-04-20 22:18:16 +02:00
committed by Paul Smith
parent 50e2cb1b1a
commit 0daa9d37c4
5 changed files with 13 additions and 5 deletions

View File

@@ -61,7 +61,7 @@ Building From Git
To build GNU make from Git, you will need Autoconf, Automake, and
Gettext, and any tools that those utilities require (GNU m4, Perl,
etc.). See the configure.in file to find the minimum versions of each
etc.). See the configure.ac file to find the minimum versions of each
of these tools. You will also need a copy of wget.
When building from Git you must build in the source directory: "VPATH
@@ -149,7 +149,7 @@ Steps to Release
Here are the things that need to be done (in more or less this order)
before making an official release:
* Update the configure.in file with the new release number.
* Update the configure.ac file with the new release number.
* Update the NEWS file with the release number and date.
* In Savannah modify the "Value", "Rank", and "Description" values for the
current "SCM" entry in both "Component Version" and "Fix Release" fields