Ignore:
Timestamp:
02/06/2002 11:15:46 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, 12.2, 12.2-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_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/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
c5ba0d6
Parents:
76c0b78
Message:

[Bug 190] reorganise and sync descriptions

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • appendixa/autoconf-desc.xml

    r76c0b78 rbdc08c1  
    1 <sect2>
    2 <title>Contents</title>
     1<sect2><title>Contents of autoconf-&autoconf-contversion;</title>
    32
    4 <para>The Autoconf package contains the autoconf, autoheader, autoreconf,
    5 autoscan, autoupdate and ifnames programs</para>
     3<sect3><title>Program Files</title>
     4<para>autoconf, autoheader, autoreconf, autoscan, autoupdate and
     5ifnames</para></sect3>
    66
    7 </sect2>
     7<sect3><title>Descriptions</title>
    88
    9 <sect2><title>Description</title>
    10 
    11 <sect3><title>autoconf</title>
     9<sect4><title>autoconf</title>
    1210<para>Autoconf is a tool for producing shell scripts that automatically
    1311configure software source code packages to adapt to many kinds of
    1412UNIX-like systems.  The configuration scripts produced by Autoconf are
    1513independent of Autoconf when they are run, so their users do not need to
    16 have Autoconf.</para></sect3>
     14have Autoconf.</para></sect4>
    1715
    18 <sect3><title>autoheader</title>
     16<sect4><title>autoheader</title>
    1917<para>The autoheader program can create a template file of C #define
    20 statements for configure to use</para></sect3>
     18statements for configure to use</para></sect4>
    2119
    22 <sect3><title>autoreconf</title>
     20<sect4><title>autoreconf</title>
    2321<para>If there are a lot of Autoconf-generated configure scripts, the
    2422autoreconf program can save some work.  It runs autoconf (and
    2523autoheader, where appropriate) repeatedly to remake the Autoconf
    2624configure scripts and configuration header templates in the directory
    27 tree rooted at the current directory.</para></sect3>
     25tree rooted at the current directory.</para></sect4>
    2826
    29 <sect3><title>autoscan</title>
     27<sect4><title>autoscan</title>
    3028<para>The autoscan program can help to create a configure.in file for
    3129a software package. autoscan examines source files in the directory
     
    3331current directory if none is given.  It searches the source files for
    3432common portability problems and creates a file configure.scan which
    35 is a preliminary configure.in for that package.</para></sect3>
     33is a preliminary configure.in for that package.</para></sect4>
    3634
    37 <sect3><title>autoupdate</title>
     35<sect4><title>autoupdate</title>
    3836<para>The autoupdate program updates a configure.in file that calls
    3937Autoconf macros by their old names to use the current
    40 macro names.</para></sect3>
     38macro names.</para></sect4>
    4139
    42 <sect3><title>ifnames</title>
     40<sect4><title>ifnames</title>
    4341<para>ifnames can help when writing a configure.in for a software
    4442package. It prints the identifiers that the package already uses in C
     
    4644have some portability, this program can help to figure out what its
    4745configure needs to check for. It may help fill in some gaps in a
    48 configure.in generated by autoscan.</para></sect3>
     46configure.in generated by autoscan.</para></sect4>
     47
     48</sect3>
    4949
    5050</sect2>
    51 
Note: See TracChangeset for help on using the changeset viewer.