diff --git a/chapter05/sed.xml b/chapter05/sed.xml
index 6b18e4e1d..172c4ecba 100644
--- a/chapter05/sed.xml
+++ b/chapter05/sed.xml
@@ -1,52 +1,69 @@
-
%general-entities;
]>
+
-Sed-&sed-version;
-
+
-
-Sed
-tools
+ Sed-&sed-version;
-
-
+
+ Sed
+ tools
+
-
-&buildtime;
-&diskspace;
-0.2 SBU8.4 MB
-
+
+
-
+
-
+
+ &buildtime;
+ &diskspace;
-
-Installation of Sed
+
+ 0.2 SBU
+ 8.4 MB
+
+
-Prepare Sed for compilation:
+
+
+
+
+
+ Installation of Sed
+
+ Prepare Sed for compilation:
./configure --prefix=/tools
-Compile the package:
+ Compile the package:
make
-To test the results, issue: make check.
+ To test the results, issue:
+ make check.
-Install the package:
+ Install the package:
make install
-
+
-
-Details on this package are located in
-
+
+
+
+ Details on this package are located in
+
+
+
-
diff --git a/chapter05/stripping.xml b/chapter05/stripping.xml
index b1d4f7dfa..99c95fa82 100644
--- a/chapter05/stripping.xml
+++ b/chapter05/stripping.xml
@@ -1,38 +1,39 @@
-
%general-entities;
]>
-
-Stripping
-
-The steps in this section are optional, but if the LFS partition
-is rather small, it is beneficial to learn that unnecessary items can
-be removed. The executables and libraries built so far contain about
-130 MB of unneeded debugging symbols. Remove those symbols
-with:
+
+
+
+ Stripping
+
+ The steps in this section are optional, but if the LFS partition is
+ rather small, it is beneficial to learn that unnecessary items can be removed.
+ The executables and libraries built so far contain about 130 MB of unneeded
+ debugging symbols. Remove those symbols with:
strip --strip-debug /tools/lib/*
strip --strip-unneeded /tools/{,s}bin/*
-The last of the above commands will skip some twenty files,
-reporting that it does not recognize their file format. Most of these
-are scripts instead of binaries.
+ The last of the above commands will skip some twenty files,
+ reporting that it does not recognize their file format. Most of these
+ are scripts instead of binaries.
-Take care not to use
---strip-unneeded on the libraries. The static
-ones would be destroyed and the toolchain packages would need to be
-built all over again.
+ Take care not to use
+ --strip-unneeded on the libraries. The static
+ ones would be destroyed and the toolchain packages would need to be
+ built all over again.
-To save another 30 MB, remove the documentation:
+ To save another 30 MB, remove the documentation:
rm -rf /tools/{info,man}
-There will now be at least 850 MB of free space on the LFS file
-system that can be used to build and install Glibc in the next phase.
-If you can build and install Glibc, you can build and install the rest
-too.
+ There will now be at least 850 MB of free space on the LFS file
+ system that can be used to build and install Glibc in the next phase.
+ If you can build and install Glibc, you can build and install the rest
+ too.
-
diff --git a/chapter05/tar.xml b/chapter05/tar.xml
index 1c2f8ffea..0266f3872 100644
--- a/chapter05/tar.xml
+++ b/chapter05/tar.xml
@@ -1,57 +1,74 @@
-
%general-entities;
]>
+
-Tar-&tar-version;
-
+
-
-Tar
-tools
+ Tar-&tar-version;
-
-
+
+ Tar
+ tools
+
-
-&buildtime;
-&diskspace;
-0.2 SBU12.7 MB
-
+
+
-
+
-
+
+ &buildtime;
+ &diskspace;
-
-Installation of Tar
+
+ 0.2 SBU
+ 12.7 MB
+
+
-If you wish to run the test suite, apply the following patch to fix
-some issues with GCC-&gcc-version;:
+
+
+
+
+
+ Installation of Tar
+
+ If you wish to run the test suite, apply the following patch to fix
+ some issues with GCC-&gcc-version;:
patch -Np1 -i ../&tar-gcc4_fix-patch;
-Prepare Tar for compilation:
+ Prepare Tar for compilation:
./configure --prefix=/tools
-Compile the package:
+ Compile the package:
make
-To test the results, issue: make check.
+ To test the results, issue:
+ make check.
-Install the package:
+ Install the package:
make install
-
+
-
-Details on this package are located in
-
+
+
+
+ Details on this package are located in
+
+
+
-
diff --git a/chapter05/tcl.xml b/chapter05/tcl.xml
index 3787a3d95..5e57053ab 100644
--- a/chapter05/tcl.xml
+++ b/chapter05/tcl.xml
@@ -1,119 +1,145 @@
-
%general-entities;
]>
+
-Tcl-&tcl-version;
-
+
-Tcl
+ Tcl-&tcl-version;
-
-The Tcl package contains the Tool Command Language.
+
+ Tcl
+
-
-&buildtime;
-&diskspace;
-0.9 SBU23.3 MB
-
+
+
-
-&dependencies;
-Bash, Binutils, Coreutils, Diffutils,
-GCC, Glibc, Grep, Make, and Sed
-
+ The Tcl package contains the Tool Command Language.
-
+
+ &buildtime;
+ &diskspace;
-
-Installation of Tcl
+
+ 0.9 SBU
+ 23.3 MB
+
+
-This package and the next two (Expect and DejaGNU) are
-installed to support running the test suites for GCC and Binutils.
-Installing three packages for testing purposes may seem excessive, but
-it is very reassuring, if not essential, to know that the most
-important tools are working properly. Even if the test suites are not
-run in this chapter (they are not mandatory), these packages
-are required to run the test suites in .
+
+ &dependencies;
+
+
+ Bash, Binutils, Coreutils, Diffutils, GCC, Glibc, Grep,
+ Make, and Sed
+
+
+
+
+
+
+ Installation of Tcl
+
+ This package and the next two (Expect and DejaGNU) are installed
+ to support running the test suites for GCC and Binutils. Installing
+ three packages for testing purposes may seem excessive, but it is very
+ reassuring, if not essential, to know that the most important tools are
+ working properly. Even if the test suites are not run in this chapter
+ (they are not mandatory), these packages are required to run the test
+ suites in .
+
+ Tcl's configure script has a syntax error:
-Tcl's configure script has a syntax error:
cd unix
cp -v configure{,.orig}
sed "s/relid'/relid/" configure.orig > configure
-Prepare Tcl for compilation:
+ Prepare Tcl for compilation:
./configure --prefix=/tools
-Build the package:
+ Build the package:
make
-To test the results, issue: TZ=UTC make test.
-The Tcl test suite is known to experience failures
-under certain host conditions that are not fully understood.
-Therefore, test suite failures here are not surprising, and are not
-considered critical. The TZ=UTC parameter sets
-the time zone to Coordinated Universal Time (UTC), also known as
-Greenwich Mean Time (GMT), but only for the duration of the test suite
-run. This ensures that the clock tests are exercised correctly.
-Details on the TZ environment variable are provided in
-.
+ To test the results, issue: TZ=UTC make test.
+ The Tcl test suite is known to experience failures under certain host
+ conditions that are not fully understood. Therefore, test suite failures
+ here are not surprising, and are not considered critical. The
+ TZ=UTC parameter sets the time zone to Coordinated
+ Universal Time (UTC), also known as Greenwich Mean Time (GMT), but only
+ for the duration of the test suite run. This ensures that the clock tests
+ are exercised correctly. Details on the TZ environment
+ variable are provided in .
-Install the package:
+ Install the package:
make install
-Install Tcl's headers. The next package, Expect, requires them to build.
+ Install Tcl's headers. The next package, Expect, requires them
+ to build.
make install-private-headers
-Now make a necessary symbolic link:
+ Now make a necessary symbolic link:
ln -sv tclsh8.4 /tools/bin/tclsh
-
+
-Contents of Tcl
+
+ Contents of Tcl
-
-Installed programs
-Installed library
-tclsh (link to tclsh8.4) and tclsh8.4libtcl8.4.so
-
+
+ Installed programs
+ Installed library
-Short Descriptions
-
-
+
+ tclsh (link to tclsh8.4) and tclsh8.4
+ libtcl8.4.so
+
+
-
-tclsh8.4
-
-The Tcl command shell
-tclsh8.4
-
-
+
+ Short Descriptions
+
+
-
-tclsh
-
-A link to tclsh8.4
-tclsh
-
-
+
+ tclsh8.4
+
+ The Tcl command shell
+
+ tclsh8.4
+
+
+
-
-libtcl8.4.so
-
-The Tcl library
-libtcl8.4.so
-
-
-
+
+ tclsh
+
+ A link to tclsh8.4
+
+ tclsh
+
+
+
-
+
+ libtcl8.4.so
+
+ The Tcl library
+
+ libtcl8.4.so
+
+
+
+
+
+
+
-
diff --git a/chapter05/texinfo.xml b/chapter05/texinfo.xml
index 9a7451b4f..49c491d7b 100644
--- a/chapter05/texinfo.xml
+++ b/chapter05/texinfo.xml
@@ -1,52 +1,69 @@
-
%general-entities;
]>
+
-Texinfo-&texinfo-version;
-
+
-
-Texinfo
-tools
+ Texinfo-&texinfo-version;
-
-
+
+ Texinfo
+ tools
+
-
-&buildtime;
-&diskspace;
-0.2 SBU14.7 MB
-
+
+
-
+
-
+
+ &buildtime;
+ &diskspace;
-
-Installation of Texinfo
+
+ 0.2 SBU
+ 14.7 MB
+
+
-Prepare Texinfo for compilation:
+
+
+
+
+
+ Installation of Texinfo
+
+ Prepare Texinfo for compilation:
./configure --prefix=/tools
-Compile the package:
+ Compile the package:
make
-To test the results, issue: make check.
+ To test the results, issue:
+ make check.
-Install the package:
+ Install the package:
make install
-
+
-
-Details on this package are located in
-
+
+
+
+ Details on this package are located in
+
+
+
-
diff --git a/chapter05/toolchaintechnotes.xml b/chapter05/toolchaintechnotes.xml
index 6524c3486..8eabbbd17 100644
--- a/chapter05/toolchaintechnotes.xml
+++ b/chapter05/toolchaintechnotes.xml
@@ -1,225 +1,218 @@
-
%general-entities;
]>
+
-Toolchain Technical Notes
-
+
-This section explains some of the rationale and technical
-details behind the overall build method. It is not essential to
-immediately understand everything in this section. Most of this
-information will be clearer after performing an actual build. This
-section can be referred back to at any time during the process.
+ Toolchain Technical Notes
-The overall goal of is to
-provide a temporary environment that can be chrooted into and from which can be
-produced a clean, trouble-free build of the target LFS system in . Along the way, we separate the new system
-from the host system as much as possible, and in doing so, build a
-self-contained and self-hosted toolchain. It should be noted that the build
-process has been designed to minimize the risks for new readers and provide
-maximum educational value at the same time.
+ This section explains some of the rationale and technical details
+ behind the overall build method. It is not essential to immediately
+ understand everything in this section. Most of this information will be
+ clearer after performing an actual build. This section can be referred
+ back to at any time during the process.
-
-Before continuing, be aware of the name of the working platform,
-often referred to as the target triplet. Many times, the target
-triplet will probably be i686-pc-linux-gnu. A
-simple way to determine the name of the target triplet is to run the
-config.guess script that comes with the source for
-many packages. Unpack the Binutils sources and run the script:
-./config.guess and note the output.
+ The overall goal of is to
+ provide a temporary environment that can be chrooted into and from which can be
+ produced a clean, trouble-free build of the target LFS system in . Along the way, we separate the new system
+ from the host system as much as possible, and in doing so, build a
+ self-contained and self-hosted toolchain. It should be noted that the build
+ process has been designed to minimize the risks for new readers and provide
+ maximum educational value at the same time.
-Also be aware of the name of the platform's dynamic linker,
-often referred to as the dynamic loader (not to be confused with the
-standard linker ld that is part of Binutils). The
-dynamic linker provided by Glibc finds and loads the shared libraries
-needed by a program, prepares the program to run, and then runs it.
-The name of the dynamic linker will usually be
-ld-linux.so.2. On platforms that are less
-prevalent, the name might be ld.so.1,
-and newer 64 bit platforms might be named something else entirely. The name of
-the platform's dynamic linker can be determined by looking in the
-/lib directory on the host
-system. A sure-fire way to determine the name is to inspect a random
-binary from the host system by running: readelf -l <name
-of binary> | grep interpreter and noting the output.
-The authoritative reference covering all platforms is in the
-shlib-versions file in the root of the Glibc
-source tree.
-
+
+ Before continuing, be aware of the name of the working platform,
+ often referred to as the target triplet. Many times, the target
+ triplet will probably be i686-pc-linux-gnu. A
+ simple way to determine the name of the target triplet is to run the
+ config.guess script that comes with the source for
+ many packages. Unpack the Binutils sources and run the script:
+ ./config.guess and note the output.
-Some key technical points of how the build
-method works:
+ Also be aware of the name of the platform's dynamic linker, often
+ referred to as the dynamic loader (not to be confused with the standard
+ linker ld that is part of Binutils). The dynamic linker
+ provided by Glibc finds and loads the shared libraries needed by a program,
+ prepares the program to run, and then runs it. The name of the dynamic
+ linker will usually be ld-linux.so.2.
+ On platforms that are less prevalent, the name might be ld.so.1, and newer 64 bit platforms might
+ be named something else entirely. The name of the platform's dynamic linker
+ can be determined by looking in the /lib
+ directory on the host system. A sure-fire way to determine the name is to
+ inspect a random binary from the host system by running:
+ readelf -l <name of binary> | grep interpreter
+ and noting the output. The authoritative reference covering all platforms
+ is in the shlib-versions file in the root of the Glibc
+ source tree.
+
-
-The process is similar in principle to
-cross-compiling, whereby tools installed in the same prefix work in
-cooperation, and thus utilize a little GNU
-magic
+ Some key technical points of how the build method works:
-Careful manipulation of the standard linker's library
-search path ensures programs are linked only against chosen
-libraries
+
+
+ The process is similar in principle to cross-compiling, whereby
+ tools installed in the same prefix work in cooperation, and thus utilize
+ a little GNU magic
+
+
+ Careful manipulation of the standard linker's library search path
+ ensures programs are linked only against chosen libraries
+
+
+ Careful manipulation of gcc's
+ specs file tells the compiler which target dynamic
+ linker will be used
+
+
-Careful manipulation of gcc's
-specs file tells the compiler which target dynamic
-linker will be used
-
+ Binutils is installed first because the configure
+ runs of both GCC and Glibc perform various feature tests on the assembler
+ and linker to determine which software features to enable or disable. This
+ is more important than one might first realize. An incorrectly configured
+ GCC or Glibc can result in a subtly broken toolchain, where the impact of
+ such breakage might not show up until near the end of the build of an
+ entire distribution. A test suite failure will usually highlight this error
+ before too much additional work is performed.
-Binutils is installed first because the
-configure runs of both GCC and Glibc perform
-various feature tests on the assembler and linker to determine which
-software features to enable or disable. This is more important than
-one might first realize. An incorrectly configured GCC or Glibc can
-result in a subtly broken toolchain, where the impact of such breakage
-might not show up until near the end of the build of an entire
-distribution. A test suite failure will usually highlight this error
-before too much additional work is performed.
+ Binutils installs its assembler and linker in two locations,
+ /tools/bin and /tools/$TARGET_TRIPLET/bin. The tools in one
+ location are hard linked to the other. An important facet of the linker is
+ its library search order. Detailed information can be obtained from
+ ld by passing it the --verbose
+ flag. For example, an ld --verbose | grep SEARCH
+ will illustrate the current search paths and their order. It shows which
+ files are linked by ld by compiling a dummy program and
+ passing the --verbose switch to the linker. For example,
+ gcc dummy.c -Wl,--verbose 2>&1 | grep succeeded
+ will show all the files successfully opened during the linking.
-Binutils installs its assembler and linker in two locations,
-/tools/bin and /tools/$TARGET_TRIPLET/bin. The tools in
-one location are hard linked to the other. An important facet of the
-linker is its library search order. Detailed information can be
-obtained from ld by passing it the
---verbose flag. For example, an ld
---verbose | grep SEARCH will illustrate the current search
-paths and their order. It shows which files are linked by
-ld by compiling a dummy program and passing the
---verbose switch to the linker. For example,
-gcc dummy.c -Wl,--verbose 2>&1 | grep
-succeeded will show all the files successfully opened
-during the linking.
+ The next package installed is GCC. An example of what can be
+ seen during its run of configure is:
-The next package installed is GCC. An example of what can be
-seen during its run of configure is:
-
-checking what assembler to use...
+checking what assembler to use...
/tools/i686-pc-linux-gnu/bin/as
checking what linker to use... /tools/i686-pc-linux-gnu/bin/ld
-This is important for the reasons mentioned above. It also
-demonstrates that GCC's configure script does not search the PATH
-directories to find which tools to use. However, during the actual
-operation of gcc itself, the same
-search paths are not necessarily used. To find out which standard
-linker gcc will use, run: gcc
--print-prog-name=ld.
+ This is important for the reasons mentioned above. It also demonstrates
+ that GCC's configure script does not search the PATH directories to find which
+ tools to use. However, during the actual operation of gcc
+ itself, the same search paths are not necessarily used. To find out which
+ standard linker gcc will use, run:
+ gcc -print-prog-name=ld.
-Detailed information can be obtained from gcc
-by passing it the -v command line option while
-compiling a dummy program. For example, gcc -v
-dummy.c will show detailed information about the
-preprocessor, compilation, and assembly stages, including
-gcc's included search paths and their order.
+ Detailed information can be obtained from gcc by
+ passing it the -v command line option while compiling
+ a dummy program. For example, gcc -v dummy.c will show
+ detailed information about the preprocessor, compilation, and assembly stages,
+ including gcc's included search paths and their order.
-The next package installed is Glibc. The most important
-considerations for building Glibc are the compiler, binary tools, and
-kernel headers. The compiler is generally not an issue since Glibc
-will always use the gcc found in a
-PATH directory.
-The binary tools and kernel headers can be a bit more complicated.
-Therefore, take no risks and use the available configure switches to
-enforce the correct selections. After the run of
-configure, check the contents of the
-config.make file in the glibc-build directory for all important
-details. Note the use of CC="gcc -B/tools/bin/"
-to control which binary tools are used and the use of the
--nostdinc and -isystem
-flags to control the compiler's include search path. These items
-highlight an important aspect of the Glibc package—it is very
-self-sufficient in terms of its build machinery and generally does not
-rely on toolchain defaults.
+ The next package installed is Glibc. The most important considerations
+ for building Glibc are the compiler, binary tools, and kernel headers. The
+ compiler is generally not an issue since Glibc will always use the
+ gcc found in a PATH directory. The binary
+ tools and kernel headers can be a bit more complicated. Therefore, take no
+ risks and use the available configure switches to enforce the correct
+ selections. After the run of configure, check the contents
+ of the config.make file in the glibc-build directory for all important details.
+ Note the use of CC="gcc -B/tools/bin/" to control which
+ binary tools are used and the use of the -nostdinc
+ and -isystem flags to control the compiler's include
+ search path. These items highlight an important aspect of the Glibc
+ package—it is very self-sufficient in terms of its build machinery and
+ generally does not rely on toolchain defaults.
-After the Glibc installation, make some adjustments to ensure
-that searching and linking take place only within the /tools prefix. Install an adjusted
-ld, which has a hard-wired search path limited to
-/tools/lib. Then amend
-gcc's specs file to point to the new dynamic linker
-in /tools/lib. This last step
-is vital to the whole process. As mentioned above, a hard-wired path
-to a dynamic linker is embedded into every Executable and Link Format
-(ELF)-shared executable. This can be inspected by running:
-readelf -l <name of binary> | grep
-interpreter. Amending gcc's specs file
-ensures that every program compiled from here through the end of this
-chapter will use the new dynamic linker in /tools/lib.
+ After the Glibc installation, make some adjustments to ensure that
+ searching and linking take place only within the /tools prefix. Install an adjusted
+ ld, which has a hard-wired search path limited to
+ /tools/lib. Then amend
+ gcc's specs file to point to the new dynamic linker in
+ /tools/lib. This last step is vital
+ to the whole process. As mentioned above, a hard-wired path to a dynamic
+ linker is embedded into every Executable and Link Format (ELF)-shared
+ executable. This can be inspected by running:
+ readelf -l <name of binary> | grep interpreter.
+ Amending gcc's specs file ensures that every program compiled from here
+ through the end of this chapter will use the new dynamic linker in
+ /tools/lib.
-The need to use the new dynamic linker is also the reason why
-the Specs patch is applied for the second pass of GCC. Failure to do
-so will result in the GCC programs themselves having the name of the
-dynamic linker from the host system's /lib directory embedded into them, which
-would defeat the goal of getting away from the host.
+ The need to use the new dynamic linker is also the reason why
+ the Specs patch is applied for the second pass of GCC. Failure to do
+ so will result in the GCC programs themselves having the name of the
+ dynamic linker from the host system's /lib directory embedded into them, which
+ would defeat the goal of getting away from the host.
-During the second pass of Binutils, we are able to utilize the
---with-lib-path configure switch to control
-ld's library search path. From this point onwards,
-the core toolchain is self-contained and self-hosted. The remainder of
-the packages all build
-against the new Glibc in /tools.
+ During the second pass of Binutils, we are able to utilize the
+ --with-lib-path configure switch to control
+ ld's library search path. From this point onwards,
+ the core toolchain is self-contained and self-hosted. The remainder of
+ the packages all build against
+ the new Glibc in /tools.
-Upon entering the chroot environment in , the first major package to be
-installed is Glibc, due to its self-sufficient nature mentioned above.
-Once this Glibc is installed into /usr, perform a quick changeover of the
-toolchain defaults, then proceed in building the rest of the target
-LFS system.
+ Upon entering the chroot environment in , the first major package to be
+ installed is Glibc, due to its self-sufficient nature mentioned above.
+ Once this Glibc is installed into /usr, perform a quick changeover of the
+ toolchain defaults, then proceed in building the rest of the target
+ LFS system.
-
+
-
+ -->
-
diff --git a/chapter05/util-linux.xml b/chapter05/util-linux.xml
index ce6395bf7..2ede1c079 100644
--- a/chapter05/util-linux.xml
+++ b/chapter05/util-linux.xml
@@ -1,63 +1,80 @@
-
%general-entities;
]>
+
-Util-linux-&util-linux-version;
-
+
-
-Util-linux
-tools
+ Util-linux-&util-linux-version;
-
-
+
+ Util-linux
+ tools
+
-
-&buildtime;
-&diskspace;
-0.2 SBU8.9 MB
-
+
+
-
+
-
+
+ &buildtime;
+ &diskspace;
-
-Installation of Util-linux
+
+ 0.2 SBU
+ 8.9 MB
+
+
-Util-linux does not use the freshly installed headers and libraries from
-the /tools directory by default. This is
-fixed by altering the configure script:
+
+
+
+
+
+ Installation of Util-linux
+
+ Util-linux does not use the freshly installed headers and libraries
+ from the /tools directory by default.
+ This is fixed by altering the configure script:
sed -i 's@/usr/include@/tools/include@g' configure
-Prepare Util-linux for compilation:
+ Prepare Util-linux for compilation:
./configure
-Compile some support routines:
+ Compile some support routines:
make -C lib
-Only a few of the utilities contained in this package need to be
-built:
+ Only a few of the utilities contained in this package need to be
+ built:
make -C mount mount umount
make -C text-utils more
-This package does not come with a test suite.
+ This package does not come with a test suite.
-Copy these programs to the temporary tools directory:
+ Copy these programs to the temporary tools directory:
cp mount/{,u}mount text-utils/more /tools/bin
-
+
+
+
+
+
+ Details on this package are located in
+
+
+
-
-Details on this package are located in
-
-