aboutsummaryrefslogtreecommitdiffstats
path: root/appendixa/autoconf-desc.xml
diff options
context:
space:
mode:
authorTimothy Bauscher <timothy@linuxfromscratch.org>2002-09-28 21:08:29 +0000
committerTimothy Bauscher <timothy@linuxfromscratch.org>2002-09-28 21:08:29 +0000
commit2c094d60db777dce20fd4eccf4996299c2a0dfe0 (patch)
tree6059aa8ca1a67a6e974f8802b9af66a7330272a4 /appendixa/autoconf-desc.xml
parentf5cc1c171ba0c9aece1fe1046ce4dbaed8850e9f (diff)
Applied Bill Maltby's grammar patch. Changed $LFS to LFS where appropriate. Internal XML cleanup: removed double spacing where appropriate.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2138 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'appendixa/autoconf-desc.xml')
-rw-r--r--appendixa/autoconf-desc.xml22
1 files changed, 11 insertions, 11 deletions
diff --git a/appendixa/autoconf-desc.xml b/appendixa/autoconf-desc.xml
index e6a96c78c..d038efbed 100644
--- a/appendixa/autoconf-desc.xml
+++ b/appendixa/autoconf-desc.xml
@@ -11,7 +11,7 @@ ifnames</para></sect3>
<sect4><title>autoconf</title>
<para>autoconf is a tool for producing shell scripts that automatically
configure software source code packages to adapt to many kinds of
-Unix-like systems. The configuration scripts produced by autoconf are
+Unix-like systems. The configuration scripts produced by autoconf are
independent of autoconf when they are run, so their users do not need to
have autoconf.</para></sect4>
@@ -24,18 +24,18 @@ statements for configure to use.</para></sect4>
<sect4><title>autoreconf</title>
<para>If there are a lot of autoconf-generated configure scripts, the
-autoreconf program can save some work. It runs autoconf (and
-autoheader, where appropriate) repeatedly to remake the autoconf
+autoreconf program can save some work. It runs autoconf and
+autoheader (where appropriate) repeatedly to remake the autoconf
configure scripts and configuration header templates in the directory
tree rooted at the current directory.</para></sect4>
<sect4><title>autoscan</title>
<para>The autoscan program can help to create a configure.in file for
-a software package. autoscan examines source files in the directory
-tree rooted at a directory given as a command line argument, or the
-current directory if none is given. It searches the source files for
-common portability problems and creates a file configure.scan which
-is a preliminary configure.in for that package.</para></sect4>
+a software package. autoscan examines the source files in a directory
+tree. If a directory is not specified on the command line, then the
+current working directory is used. The source files are searched for
+common portability problems and a configure.scan file is created to
+serve as the preliminary configure.in for that package.</para></sect4>
<sect4><title>autoupdate</title>
<para>The autoupdate program updates a configure.in file that calls
@@ -46,9 +46,9 @@ macro names.</para></sect4>
<para>ifnames can help when writing a configure.in for a software
package. It prints the identifiers that the package already uses in C
preprocessor conditionals. If a package has already been set up to
-have some portability, this program can help to figure out what its
-configure needs to check for. It may help fill in some gaps in a
-configure.in generated by autoscan.</para></sect4>
+have some portability, this program can help to determine what configure
+needs to check. It may fill in some gaps in a configure.in file generated
+by autoscan.</para></sect4>
</sect3>