Ignore:
Timestamp:
06/07/2020 08:16:00 PM (4 years ago)
Author:
Bruce Dubbs <bdubbs@…>
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, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, 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:
595ff03
Parents:
d53fefa
Message:

Initial commit of alternative cross LFS

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/branches/cross2@11897 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter06/introduction.xml

    rd53fefa rfcc02767  
    66]>
    77
    8 <sect1 id="ch-system-introduction">
     8<sect1 id="ch-tools-introduction">
    99  <?dbhtml filename="introduction.html"?>
    1010
    1111  <title>Introduction</title>
    1212
    13   <para>In this chapter, we enter the building site and start constructing the
    14   LFS system in earnest. That is, we chroot into the temporary mini Linux system,
    15   make a few final preparations, and then begin installing the packages.</para>
     13  <para>This chapter shows how to build a minimal Linux system.
     14  This system will contain just enough tools to start constructing the final
     15  LFS system in <xref linkend="chapter-building-system"/> and allow a working
     16  environment with more user convenience than a minimum environment would.</para>
    1617
    17   <para>The installation of this software is straightforward. Although in many
    18   cases the installation instructions could be made shorter and more generic,
    19   we have opted to provide the full instructions for every package to minimize
    20   the possibilities for mistakes.  The key to learning what makes a Linux system
    21   work is to know what each package is used for and why you (or the system)
    22   may need it.</para>
    23 
    24   <para>We do not recommend using optimizations.  They can make
    25   a program run slightly faster, but they may also cause compilation
    26   difficulties and problems when running the program.  If a package refuses to
    27   compile when using optimization, try to compile it without optimization and
    28   see if that fixes the problem. Even if the package does compile when using
    29   optimization, there is the risk it may have been compiled incorrectly because
    30   of the complex interactions between the code and build tools.  Also note that
    31   the <option>-march</option> and <option>-mtune</option> options using values
    32   not specified in the book have not been tested. This may cause problems with
    33   the toolchain packages (Binutils, GCC and Glibc).  The small potential gains
    34   achieved in using compiler optimizations are often outweighed by the risks.
    35   First-time builders of LFS are encouraged to build without custom
    36   optimizations. The subsequent system will still run very fast and be stable
    37   at the same time.</para>
    38 
    39   <para>Before the installation instructions, each installation page provides
    40   information about the package, including a concise description of what it
    41   contains, approximately how long it will take to build, and how much disk
    42   space is required during this building process. Following the installation
    43   instructions, there is a list of programs and libraries (along with brief
    44   descriptions of these) that the package installs.</para>
    45 
    46   <note><para>The SBU values and required disk space includes
    47   test suite data for all applicable packages in Chapter&nbsp;6.</para></note>
    48 
    49   <sect2>
    50     <title>About libraries</title>
    51 
    52     <para>In general, the LFS editors discourage building and installing static
    53     libraries.  The original purpose for most static libraries has been made
    54     obsolete in a modern Linux system.  In addition linking a static library
    55     into a program can be detrimental.  If an update to the library is needed
    56     to remove a security problem, all programs that use the static library will
    57     need to be relinked to the new library.  Since the use of static libraries
    58     is not always obvious, the relevant programs (and the procedures needed to
    59     do the linking) may not even be known.</para>
    60 
    61     <para>In the procedures in Chapter&nbsp;6, we remove or disable installation of
    62     most static libraries. Usually this is done by passing a
    63     <option>--disable-static</option> option to <command>configure</command>.
    64     In other cases, alternate means are needed. In a few cases, especially
    65     glibc and gcc, the use of static libraries remains essential to the general
    66     package building process. </para>
    67 
    68     <para>For a more complete discussion of libraries, see the discussion
    69     <ulink url="&blfs-root;/view/&short-version;/introduction/libraries.html">
    70     Libraries: Static or shared?</ulink> in the BLFS book.</para>
    71 
    72   </sect2>
    73 
     18  <para>There are two steps in building this minimal system. The first step
     19  is to build a new and host-independent toolchain (compiler, assembler,
     20  linker, libraries, and a few useful utilities).  The second step uses this
     21  toolchain to build the other essential tools.</para>
     22<!--
     23  <para>The files compiled in this chapter will be installed under the
     24  <filename class="directory">$LFS</filename> directory to keep them
     25  separate from the files installed in the next chapter and the host
     26  production directories. Since the packages compiled here are temporary,
     27  we do not want them to pollute the soon-to-be LFS system.</para>
     28-->
    7429</sect1>
Note: See TracChangeset for help on using the changeset viewer.