Changeset cc8dba9


Ignore:
Timestamp:
03/27/2017 07:49:04 PM (7 years ago)
Author:
Pierre Labastie <pierre@…>
Branches:
2.4, ablfs-more, legacy, trunk
Children:
6bba83f
Parents:
5e59386
Message:

Refactor two README files

Files:
2 edited

Legend:

Unmodified
Added
Removed

  • README

    r5e59386 rcc8dba9  
    331. INTRODUCTION::
    44
    5      This collection of scripts, known as jhalfs, strives to create
    6   accurate makefiles from the Linux From Scratch book series XML files.
    7   This software is an evolution of the original "jhalfs-0.2" code developed
    8   by Jeremy Huntwork.
    9 
    10      The usage of this script assumes you have read and are familiar with
    11   the book(s) and, therefore, the configuration variables found in menuconfig
    12   interface will have meaning to you.
    13 
    14   The list of supported books can be found at
    15   http://wiki.linuxfromscratch.org/alfs/wiki/SupportedBooks
    16 
    17   NOTES::
    18   *.  The resulting Makefile takes considerable time to run to completion.
    19   Lay in a supply of caffeine beverages.
    20 
    21   *.  It is recommended that you temporarily unpack your linux kernel,
    22   run <make menuconfig>, configure the kernel as per the book and save
    23   the resulting .config file.
    24 
    25   *.  Read carefully this file and the other README.* files before using
    26   this tool.
     5     The scripts in this directory implement an automation of the building
     6  of a GNU/LInux system, as described in the Linux From Scratch book series.
     7  The name of the project is jhalfs: in that name, "alfs" stands for
     8  "automated linux from scratch", and the initials "jh" have been kept since
     9  the original "jhalfs-0.2" code developed by Jeremy Huntwork.
     10
     11     The list of supported books can be found at
     12  http://wiki.linuxfromscratch.org/alfs/wiki/SupportedBooks.
     13
     14     The documentation is split among various README.* files. Here is a list
     15  of what is in which:
     16    - README (this file): instructions to use the LFS book. This should be
     17      enough if you just want to build a base system as per the LFS book. It is
     18      also a required reading for all the other projects.
     19    - README.CLFS: supplementary instructions to use the CLFS book series.
     20    - README.BLFS: instructions to install an automated build infrastructure
     21      for the BLFS book. There are two ways to do so: (i) install the
     22      tools at the end of an LFS build (CLFS is not supported in that case), or
     23      (ii) install the tools on an already running system. Both methods are
     24      described in that file.
     25    - README.CUSTOM: instructions to run custom commands either during the xLFS
     26      build, at the end of a xLFS build. Note that you will not find
     27      instructions on how to write those commands, but some examples are
     28      available.
     29    - README.PACKAGE_MANAGEMENT: instructions to use package management during
     30      the build (only for LFS, patches welcome for CLFS...)
     31    - README.HLFS: very short file explaining why you cannot use HLFS with the
     32      present tool version.
     33
     34     Other sources of information are the context help in the menu interface,
     35  and the xLFS books themselves.
    2736
    28372. PREREQUISITES::
    2938
    30      To use this tool you MUST:
    31 
    32      - have experience building {c,h,b}LFS packages
    33      - know how to edit and write shell scripts
    34      - know how a Makefile works
    35      - be able to trace build failures and to find what is causing them
    36        (user error, package bug, {c,h,b}LFS command bug, or jhalfs code bug)
    37 
    38      If you do not have the above skills, please don't use this tool.
    39 
     39     As said elsewhere, it is strongly advised that you first build manually
     40  a complete system before attempting to automate the build.
     41
     42     Of course the "Host System Requirements" should be fulfilled. The needed
     43  supplementary packages are detailed at the bottom of the page:
     44  http://www.linuxfromscratch.org/alfs/download.html
    4045
    41463. INSTALLATION::
    4247
    43      No installation is required. You should just run <make> in this directory.
     48     No installation is required. You may want to move the files in this
     49  directory to a convenient location, and then follow the instructions below.
    4450
    45514. CONFIGURATION::
    4652
    47      Configuration is done through a menu based interface. See the section
    48      RUNNING, for details.
     53  4.1. CONFIGURATION OF THE TOOLS:
     54       There is no configuration of the tools themselves. The various
     55    parameters for the build are set through a menu driven interface. See
     56    the section RUNNING below for details.
     57
     58  4.2. PRELIMINARY TASKS:
     59       This tool has no support at all for creating a partition and a mount
     60    point for the built system. You should follow the book up to the section
     61    "Mounting the new partition". Note that the default name for the
     62    partition mount point is "/mnt/build_dir", instead of /mnt/{c,}lfs.
     63    You can change that default to anything you'd like in the menu, so you
     64    may name it /mnt/lfs, or whatever you like. One important point is that
     65    the user you are logged in as (and not the (c)lfs user) should have write
     66    permission to the mounted directory. We'll use the name /mnt/build_dir
     67    in the sequel.
     68
     69       The tool can download the needed packages for you, or you may download
     70    them yourself. The tool may optionally use a package archive directory
     71    where the downloaded packages are stored. That directory name may be made
     72    available to the tool in two ways: (i) export the SRC_ARCHIVE variable,
     73    for example SRC_ARCHIVE=/usr/src, (ii) enter the name at the "Package
     74    Archive Directory" menu prompt. Note that the user should have write
     75    permission to that directory. If a needed package is found in that
     76    directory, it is copied to /mnt/build_dir/sources, if not, it is
     77    downloaded to that directory and copied to /mnt/build_dir/sources,
     78    except if found in /mnt/build_dir/sources, in which case, it is just
     79    copied to $SRC_ARCHIVE. If you want the tool to download packages and you
     80    do not want to archive them, just unset SRC_ARCHIVE, and keep the
     81    default entry for "Package Archive Directory". If you choose to download
     82    the packages by yourself, you should download (or copy) them to
     83    /mnt/build_dir/sources directly.
     84   
     85       If you want to build the kernel as part of the automated build, select
     86    "Build the kernel" in the menu. Then, a configuration file must be
     87    provided. In order to do so, it is recommended to download the kernel
     88    tarball, unpack it, run <make menuconfig>, configure the kernel as per
     89    the book, and save the resulting .config file to a location where it can
     90    be retrieved later on (a convenient location and name is
     91    $SRC_ARCHIVE/config-<arch>-<kernel version>-<config details>).
     92
     93       Another file you may provide is the fstab file. To use it, select
     94    "Use a custom fstab file" in the menu interface, and enter the name of
     95    the file where asked. As for the kernel configuration, this file has to
     96    be prepared before running the menu. A convenient location and name is
     97    $SRC_ARCHIVE/fstablfs.
     98
     99       At a more advanced level, you may want to supply custom commands
     100    to be run at the end of (C)LFS build. Scripts containing those commands
     101    are located in the ./custom/config directory. Examples are given in
     102    ./custom/examples. A template is provided as ./custom/template. See
     103    README.CUSTOM for more details.
    49104
    501055. RUNNING::
    51106
    52      The command <make> will launch a menu based configuration program. You will
    53      recognize the layout from building the kernel or uClibc/BusyBox. The
    54      underlying menu code was borrowed from BusyBox and slightly modified for
    55      our use.
     107     The command <make> will launch a menu based configuration program. The
     108  underlying menu code was borrowed from BusyBox and slightly modified for
     109  our use.
    56110
    57111     Help on parameter function is available from the on-line help. Please
    58      make use of that feature: it may contain additional information not
    59      duplicated in this file.
     112  make use of that feature: it may contain additional information not
     113  duplicated in this file.
    60114
    61115     You should first choose which book and flavour you want to build. Note
    62      that when you choose the BLFS book, the tool will just install the BLFS
    63      tool to your system. You'll have to run that installed tool to build
    64      packages in BLFS. See README.BLFS to know how. If you choose any other
    65      book, you'll have to configure the settings and the build parameters
    66      from the menu. Note that you may choose to install the blfs tools onto
    67      the newly built system (see below). It is not the same thing as choosing
    68      the BLFS book in the menu, which will install the blfs tools on the
    69      currently running system.
    70    
     116  that when you choose the BLFS book, the tool will just install the BLFS
     117  tool to your system. You'll have to run that installed tool to build
     118  packages in BLFS. See README.BLFS to know how. If you choose any other
     119  book, you'll have to configure the settings and the build parameters
     120  from the menu. Note that you may choose to install the blfs tools onto
     121  the newly built system. It is not the same thing as choosing
     122  the BLFS book in the menu, which will install the blfs tools on the
     123  currently running system.
     124
     125     The "General Settings" menu is where the "Build Directory" name is to be
     126  entered. Other entries in that menu select what the tool should do. The
     127  "Run the Makefile" entry selects whether the tool will start the build
     128  automatically after generating the needed files. The "Rebuild files" selects
     129  whether to clean the build directory before doing anything else. To protect
     130  against removing important files, this can only be done in an empty directory,
     131  or a directory previously populated by the tool.
     132
     133     The "Build Settings" menu is where various options for the build can be
     134  selected. Two options, "Use a custom fstab file" and "Build the kernel",
     135  have been described above. "Do not use/display progress_bar", if set, will
     136  prevent a progress bar to be displayed during the build. That may be useful
     137  on slow machine. The other options should be self explanatory, using either
     138  the online help or book reading.
     139
     140     The "Advanced Features" menu is for various maintenance tasks, like
     141  testing the build instructions or reporting build statistics. One useful
     142  option is "Optimization and parallelisation". It is not recommended to use
     143  it for setting compiler optimization flags, although it is possible, but
     144  if you select it, you'll be able to select the number of parallel `make'
     145  jobs, which allows much faster builds on modern multicore CPUs.
    71146
    72147     Once you have set the parameters and saved the configuration, the script
    73      is launched. Its aim is to extract instructions from the selected book
    74      to generate scripts, and to generate a Makefile, which allows running
    75      the scripts in the right order. The script verifies first that the host
    76      can run it and build the xLFS system, then validates the configuration
    77      and lists the parameters. At this point, you may choose to quit or to
    78      continue with the listed parameters. The script will then proceed to
    79      generate the Makefile and the build scripts, optionally download
    80      packages, and eventually verify the host prerequisite. If you have
    81      selected "Run the makefile", the command make is launched in the
    82      adequate directory, and the build begins. If not, you'll have to run
    83      "make" manually, for example: "make -C /mnt/build_dir/jhalfs", if you
    84      have used the default parameters (see the layout under $BUILDDIR in the
    85      Q&A below).
    86 
    87      IMPORTANT::
    88          You must be logged as a normal user with sudo privileges to run
    89          the Makefile. Furthermore, you are supposed to have enough privilege
    90          to become any user. If you are not bothered about security issues,
    91          the entry for the user "jhalfs_user" in /etc/sudoers could be
    92          jhalfs_user ALL=(ALL) NOPASSWD:ALL
    93 
    94      NOTE::
    95          If you run the jhalfs script directly the only function you can select
    96          is to display the version number running <./jhalfs -v>
    97 
    98 6. BLFS_TOOL SUPPORT::
    99 
    100      For books that support it (only LFS for jhalfs version 2.4),
    101      there is an option to install an automated framework for building BLFS
    102      packages. It is called blfs-tool. When you tick `BOOK Settings/Add
    103      blfs-tool support' in jhalfs configuration menu, the tools are
    104      installed in $BLFS_ROOT (default /blfs_root) on the xLFS system,
    105      and a few dependencies (which you may select) are built at the
    106      end of the jhalfs run, before the custom tools. The instructions for
    107      building the dependencies are taken from the BLFS book.
    108 
    109      (TODO: blfs-tools have not been tested with current (version 3.0) of CLFS,
    110      and certainly need some adaptation to run)
    111      WARNING:: If you add blfs-tool support on a CLFS Sysroot build
    112                you MUST edit the scripts to fix the installation paths.
    113 
    114      After booting the new xLFS system some steps are needed to finish
    115      the installation of the automated tools:
    116 
    117        - A user account must be created. You must be logged on that user
    118          account to use blfs-tool. This is not strictly necessary,
    119          since the packages can be built as root, too, but it is
    120          never a good idea to build packages as root.
    121 
    122        - Move /blfs-root to that user's home and change ownership of the
    123          directory and files to the user.
    124 
    125        - Give the user read and write privileges over the $TRACKING_DIR
    126          directory and the files that it contains.
    127 
    128        - Configure sudo, adding the needed privileges for the user. For
    129          newer sudo version, do not forget to add a line Defaults secure_path=
    130          containing /sbin and /usr/sbin (in /etc/sudoers), otherwise some
    131          executables are not found.
    132 
    133        - Although it is not strictly necessary, it is recommended to install
    134          the bash shell startup files (as per `3.After LFS Configuration
    135          Issues' of the BLFS book), as some instructions in BLFS rely on
    136          their being present.
    137 
    138      We assume that blfs-tool will be used on a running fresh xLFS system.
    139      To use it to build BLFS packages from the chroot jail is also possible,
    140      but not supported.
    141 
    142      To know how to use blfs-tool, see README.BLFS.
    143 
    144 7. LAYOUT::
     148  is launched. Its aim is to extract instructions from the selected book
     149  to generate scripts, and to generate a Makefile, which allows running
     150  the scripts in the right order. The script verifies first that the host
     151  can run itself and build the xLFS system, then validates the configuration
     152  and lists the parameters. At this point, you may choose to quit or to
     153  continue with the listed parameters. The script will then proceed to
     154  generate the Makefile and the build scripts, optionally download
     155  packages, and eventually verify the host prerequisite. If you have
     156  selected "Run the makefile", the command <make> is launched in the
     157  adequate directory, and the build begins. If not, you'll have to run
     158  "make" manually, for example: "make -C /mnt/build_dir/jhalfs", if you
     159  have used the default parameters (see the layout under $BUILDDIR in the
     160  Q&A below).
     161
     162  IMPORTANT::
     163      You must be logged as a normal user with sudo privileges to run
     164      the Makefile. Furthermore, you are supposed to have enough privilege
     165      to become any user. If you are not bothered about security issues,
     166      the entry for the user "jhalfs_user" in /etc/sudoers could be
     167      jhalfs_user ALL=(ALL) NOPASSWD:ALL
     168
     169  NOTE::
     170      If you run the jhalfs script directly the only function you can select
     171      is to display the version number by running <./jhalfs -v>
     172
     1736. LAYOUT::
    145174
    146175        /BLFS (see README.BLFS)
    … …  
    205234        blfs-tool
    206235
    207 8. FAQ::
    208     Q. "This 'help' file is very sparse"
    209     A. Yes, it is. This tool, jhalfs, is for those who understand the LFS books
    210        and wish to automate the build. 99% of any problems that arise can be
    211        solved by reading the book(s).
    212 
    213     Q. "It doesn't work!"
    214     A. Yes it does, try >> make
    215        Remember you must have 'sudo' privileges.
    216 
    217     Q. "It still doesn't work"
    218     A. jhalfs was designed to work against the development versions of the LFS
    219        series of books. Consequently changes in a book(s) sometimes breaks older
    220        versions of jhalfs. Before you start pulling out your hair download the
    221        latest version of jhalfs to see if that solves your problem.
     2367. FAQ::
     237    Q. "It doesn't work"
     238    A. There are several reasons why it may be so. One possibility is the
     239       following:jhalfs was designed to work against the development versions
     240       of the LFS series of books. Consequently changes in a book(s) sometimes
     241       breaks older versions of jhalfs. Before you start pulling out your hair
     242       download the latest version of jhalfs to see if that solves your
     243       problem. Note that it may be the other way around. If you want to build
     244       an old version of the book, you may have to downgrade you jahlfs
     245       version.
    222246
    223247    Q. "How do I specify the build location?"

  • README.BLFS

    r5e59386 rcc8dba9  
    22
    331. INTRODUCTION::
    4 
    5      If you want to add blfs-tool support into an xLFS base system build,
    6   read the "BLFS_TOOL SUPPORT" section found in the README and be sure
    7   to follow the after-booting installation instructions.
    84
    95     To automate package builds from the BLFS book instructions is a huge
    … …  
    21172. PREREQUISITES::
    2218
    23      To use this tool you MUST:
    24 
    25      - have experience building BLFS packages
    26      - know how to edit and write shell scripts
    27      - know how a Makefile works
    28      - be able to trace build failures and to find what is causing it
    29        (user error, package bug, BLFS command bug, or jhalfs code bug)
    30 
    31      If you do not have the above skills, please don't use this tool.
    32 
    33 
    34 3. USAGE::
    35 
    36      Due to the complexity of the BLFS book, the scripts and Makefile
    37      generation is done in several steps:
    38 
    39   3.1  INSTALLED PACKAGES TRACKING SYSTEM::
    40 
    41        This tool includes a very simple tracking system to log which packages
    42     have been installed using the tool. It is used to skip installed packages
    43     from target selection menu and to test if an installed package has been
    44     updated in the BLFS book. Do not rely on this feature as a package
    45     management tool.
    46 
    47        The tracking system itself is an XML file: instpkg.xml. It is
    48     initialized when <make> is first run in blfs_root. It resides in a
    49     directory, which is created when needed during the process of building
    50     custom tools or blfs dependencies, right after xLFS. You can specify
    51     that directory location in the blfs-tools sub-menu of jhalfs. You may
    52     need to update permissions and/or ownership of this directory before
    53     using the blfs tool (see README in jhalfs).
    54 
    55        The default location of the tracking directory is /var/lib/jhalfs/BLFS.
    56     NB : after the initial build, that directory is only used to contain
    57     instpkg.xml, unless custom tools have been built. In the latter case,
    58     it also contains empty files whose name are "$PKG-$VERSION" for each
    59     versionned package built. The information about those packages is
    60     included into instpkg.xml the next time the tool is run.
    61 
    62   3.2  BLFS_TOOL INSTALLATION::
    63 
    64     3.2.1 Normal install
    65        The tools are installed just after the building of xLFS, if the
    66     appropriate options have been selected in the building menu, as per
    67     jhalfs README. If you forgot to select the options and xLFS has been
    68     built, it is possible to go back to selecting the appropriate
    69     BLFS tools options in the jhalfs menu, then tick `Run makefile'
    70     and not `Rebuild files'. You obtain a /blfs_root directory in the
    71     root directory of the new xLFS system, which contains the followings:
     19     In addition to a full LFS system, the following packages and their
     20  dependencies are needed by this tool:
     21    - required: libxml2, libxslt, DocBook XML DTD
     22    - recommended: wget (to download the package tarballs) and sudo (to build
     23      as a user)
     24    - optional: lynx (allows to read the generated linearized book), GPM (to
     25      cut and paste commands from the book), subversion (to update the book
     26      sources), openssl (used by wget for all https:// sites)
     27  Note that the optional dependencies are recommended for ease of use of the
     28  tool.
     29
     30     You should also have the following personal skills:
     31    - Ability to write and debug shell scripts: as said in the introduction,
     32      not all the generated scripts can be used directly. They need to be
     33      edited to produce an error free build.
     34    - Ability to debug build failures, like missing dependencies or
     35      installation directories not known to the system (when you install in
     36      /opt for example).
     37    - Ability to choose the tools you need to configure and administrate
     38      your system: in the BLFS book, nothing is mandatory, nothing is
     39      useless. You are on your own in choosing what to build, but wrong
     40      decisions may lead to a non functional system...
     41
     423. INSTALL::
     43
     44     There are two ways to install the BLFS tools on an LFS system, described
     45  in paragraphs 3.1 and 3.2, respectively:
     46
     47  3.1 INSTALLATION ON A RUNNING SYSTEM
     48
     49     Select "Use Book --> Beyond Linux From Scratch" in the jhalfs menu:
     50  The tools are installed in $HOME$BLFS_ROOT (the default for $BLFS_ROOT
     51  is /blfs_root). The BLFS book is downloaded or copied to its directory.
     52  The tracking directory (see below) is initialized but not created: before
     53  the installation, you should ensure the tracking directory (default location
     54  /var/lib/jhalfs/BLFS) exists and is writable by the user. After the
     55  intallation, you should perform the following additional steps:
     56
     57    - Configure sudo, adding the needed privileges for the user. For
     58      newer sudo version, do not forget to add a line `Defaults secure_path='
     59      containing /sbin and /usr/sbin (in /etc/sudoers), otherwise some
     60      executables are not found.
     61
     62    - Although it is not strictly necessary, it is recommended to install
     63      the bash shell startup files (as per `3.After LFS Configuration
     64      Issues' of the BLFS book), as some instructions in BLFS rely on
     65      their being present.
     66
     67  3.2 INSTALLATION ON A JUST BUILT xLFS SYSTEM
     68
     69    For books that support it (only LFS for jhalfs version 2.4),
     70  there is an option to install the BLFS tools right after building
     71  the xLFS system: just tick `BOOK Settings/Add blfs-tool support' in
     72  jhalfs configuration menu. The tools are installed in $BLFS_ROOT
     73  (default /blfs_root) on the xLFS system, and the dependencies are built
     74  at the end of the jhalfs run, before the custom tools.
     75
     76  (TODO: blfs-tools have not been tested with current (version 3.0) of CLFS,
     77  and certainly need some adaptation to run)
     78
     79  After booting the new xLFS system some steps are needed to finish
     80  the installation of the automated tools:
     81
     82    - A user account must be created. You must be logged on that user
     83      account to use blfs-tool. This is not strictly necessary,
     84      since the packages can be built as root, too, but it is
     85      never a good idea to build packages as root.
     86
     87    - Move /blfs-root to that user's home and change ownership of the
     88      directory and files to the user.
     89
     90    - Give the user read and write privileges over the $TRACKING_DIR
     91      directory and the files that it contains.
     92
     93    - Configure sudo and add the bash shell startup files, as described
     94      above
     95
     96     We assume that the BLFS tools will be used on a booted xLFS system.
     97  Using them to build BLFS packages in a chroot jail is also possible,
     98  but not supported.
     99
     100  3.3 DIRECTORY LAYOUT IN THE $BLFS_ROOT DIRECTORY
    72101
    73102    blfs-xml/*              SVN tree of the selected BLFS book version
    … …  
    99128    envars.conf             envars needed when running the target build scripts
    100129
    101     3.2.2 Install to an already running LFS/BLFS system
    102        If you forgot to install the tools when building xLFS, or want to try
    103     the tools, you can select the BLFS book from the jhalfs menu. It will
    104     run a script, which creates the above hierarchy in your home directory and
    105     initialize the tracking file. You have first to make sure that the tracking
    106     dir exists and is writable by the user. You may also populate it with
    107     (empty) files whose names are of the form package-version, for installed
    108     packages, so that they are included into the tracking file.
    109 
    110     3.3.3 Working files
    111         Several files are generated during the process:
     130    Working files: several files are generated when first running the tool
    112131
    113132    packages.xml            auto-generated packages database
    … …  
    119138    scripts/*               the scriptlets
    120139
     140  3.4 INSTALLED PACKAGES TRACKING SYSTEM:
     141
     142       This tool includes a very simple tracking system to log which packages
     143    have been installed using the tool. It is used to skip installed packages
     144    from target selection menu and to test if an installed package has been
     145    updated in the BLFS book. Do not rely on this feature as a package
     146    management tool.
     147
     148       The tracking system itself is an XML file: instpkg.xml. It is
     149    initialized when <make> is first run in blfs_root. It resides in a
     150    directory, which is created when needed during the process of building
     151    custom tools or blfs dependencies, right after xLFS. You can specify
     152    that directory location in the blfs-tools sub-menu of jhalfs. You may
     153    need to update permissions and/or ownership of this directory before
     154    using the blfs tool (see README in jhalfs).
     155
     156       The default location of the tracking directory is /var/lib/jhalfs/BLFS.
     157    NB : after the initial build, that directory is only used to contain
     158    instpkg.xml, unless custom tools have been built. In the latter case,
     159    it also contains empty files whose name are "$PKG-$VERSION" for each
     160    versionned package built. The information about those packages is
     161    included into instpkg.xml the next time the tool is run.
     162
     1634. USAGE::
     164
    121165       From now on, all the work must be done from inside the installation
    122166    root directory.
    123167
    124        You may move that directory to the $HOME of a non root user, or build
    125     as root from that directory.
    126 
    127   3.3  UPDATING BOOK SOURCES::
     168     Due to the complexity of the BLFS book, the scripts and Makefile
     169     generation is done in several steps:
     170
     171  4.1  UPDATING BOOK SOURCES::
    128172
    129173       If you are using the development book version and you want to update
    … …  
    143187    and used to solve dependencies.
    144188
    145   3.4  CONFIGURING AND PARSING THE BOOK::
     189  4.2  CONFIGURING AND PARSING THE BOOK::
    146190
    147191       The next step is to create a book and build scripts in dependency
    … …  
    181225    generated while resolving dependencies.
    182226
    183   3.5  EDITING BUILD SCRIPTS::
     227  4.3  EDITING BUILD SCRIPTS::
    184228
    185229       Now it is time to review the generated book and scripts, making any
    … …  
    198242    needed by the build scripts.
    199243
    200   3.6  CREATING THE MAKEFILE::
     244  4.4  CREATING THE MAKEFILE::
    201245
    202246       When the build scripts are ready to be run, the Makefile can be
    … …  
    207251    "make".
    208252
    209 4. GENERATED BUILD SCRIPTS ISSUES::
     2535. GENERATED BUILD SCRIPTS ISSUES::
    210254
    211255      In this section, known issues with the generated build scripts are
    … …  
    223267   fields of each involved script.
    224268
    225    4.1  BLFS BOOTSCRIPTS::
     269   5.1  BLFS BOOTSCRIPTS::
    226270
    227271        Normally, bootscript installation should work. On the other hand, the
    … …  
    230274     the build.
    231275
    232    4.2  PACKAGE CONFIGURATION::
     276   5.2  PACKAGE CONFIGURATION::
    233277
    234278        For those packages that have a "Configuration" section, you should
    … …  
    238282     variables are used.
    239283
    240    4.3  PAGES WITH TWO OR MORE PACKAGES::
     284   5.3  PAGES WITH TWO OR MORE PACKAGES::
    241285
    242286        For example: sane, poppler, audacious, freetts, which, etc.
    … …  
    249293     instructions may need to be repeated for each tarball in turn.
    250294
    251    4.4  XORG7
     295   5.4  XORG7
    252296
    253297        The book has special page layouts for the Xorg7 packages. The tool
    … …  
    258302     dependency chain brings in the whole set of Xorg packages.
    259303
    260    4.5  PATCHES
     304   5.5  PATCHES
    261305
    262306        Please, make sure that all scripts have the commands to download/apply
    … …  
    264308     missing (as of BLFS 8.0, all the patches seem to be downloaded).
    265309
    266    4.6  ROOT COMMANDS
     310   5.6  ROOT COMMANDS
    267311
    268312        If building as a normal user (the default setting), be sure that all
    … …  
    293337        Due to book layout issues, some sudo commands may be missing.
    294338
    295    4.7  OTHERS
     339   5.7  OTHERS
    296340
    297341        There may be other issues that we are not aware of. If you find
Note: See TracChangeset for help on using the changeset viewer.