Ignore:
Timestamp:
07/22/2001 07:45:10 PM (23 years ago)
Author:
Mark Hymers <markh@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v3_0, v3_1, v3_2, v3_3, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
f1da843
Parents:
46f5461
Message:

XML changes

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@827 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed
  • appendixa/autoconf-desc.xml

    r46f5461 rb822811  
    22<title>Contents</title>
    33
    4 <para>
    5 The Autoconf package contains the autoconf, autoheader, autoreconf,
    6 autoscan, autoupdate and ifnames programs
    7 </para>
     4<para>The Autoconf package contains the autoconf, autoheader, autoreconf,
     5autoscan, autoupdate and ifnames programs</para>
    86
    97</sect2>
     
    1311<sect3><title>autoconf</title>
    1412
    15 <para>
    16 Autoconf is a tool for producing shell scripts that automatically
     13<para>Autoconf is a tool for producing shell scripts that automatically
    1714configure software source code packages to adapt to many kinds of
    1815UNIX-like systems.  The configuration scripts produced by Autoconf are
    1916independent of Autoconf when they are run, so their users do not need to
    20 have Autoconf.
    21 </para>
     17have Autoconf.</para>
    2218
    2319</sect3>
     
    2521<sect3><title>autoheader</title>
    2622
    27 <para>
    28 The autoheader program can create a template file of C #define
    29 statements for configure to use
    30 </para>
     23<para>The autoheader program can create a template file of C #define
     24statements for configure to use</para>
    3125
    3226</sect3>
     
    3428<sect3><title>autoreconf</title>
    3529
    36 <para>
    37 If there are a lot of Autoconf-generated configure scripts, the
     30<para>If there are a lot of Autoconf-generated configure scripts, the
    3831autoreconf program can save some work.  It runs autoconf (and
    3932autoheader, where appropriate) repeatedly to remake the Autoconf
    4033configure scripts and configuration header templates in the directory
    41 tree rooted at the current directory.
    42 </para>
     34tree rooted at the current directory.</para>
    4335
    4436</sect3>
     
    4638<sect3><title>autoscan</title>
    4739
    48 <para>
    49 The autoscan program can help to create a configure.in file for
     40<para>The autoscan program can help to create a configure.in file for
    5041a software package. autoscan examines source files in the directory
    5142tree rooted at a directory given as a command line argument, or the
    5243current directory if none is given.  It searches the source files for
    5344common portability problems and creates a file configure.scan which
    54 is a preliminary configure.in for that package.
    55 </para>
     45is a preliminary configure.in for that package.</para>
    5646
    5747</sect3>
     
    5949<sect3><title>autoupdate</title>
    6050
    61 <para>
    62 The autoupdate program updates a configure.in file that calls
    63 Autoconf macros by their old names to use the current macro names.
    64 </para>
     51<para>The autoupdate program updates a configure.in file that calls
     52Autoconf macros by their old names to use the current macro names.</para>
    6553
    6654</sect3>
     
    6856<sect3><title>ifnames</title>
    6957
    70 <para>
    71 ifnames can help when writing a configure.in for a software
     58<para>ifnames can help when writing a configure.in for a software
    7259package. It prints the identifiers that the package already uses in C
    7360preprocessor conditionals. If a package has already been set up to
    7461have some portability, this program can help to figure out what its
    7562configure needs to check for. It may help fill in some gaps in a
    76 configure.in generated by autoscan.
    77 </para>
     63configure.in generated by autoscan.</para>
    7864
    7965</sect3>
Note: See TracChangeset for help on using the changeset viewer.