diff --git a/part3intro/toolchaintechnotes.xml b/part3intro/toolchaintechnotes.xml
index 7997b0891..6deffe91c 100644
--- a/part3intro/toolchaintechnotes.xml
+++ b/part3intro/toolchaintechnotes.xml
@@ -359,20 +359,17 @@ checking what linker to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/ldNext comes 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 compiler relating to the --host
+ kernel headers. The compiler and binary tools are generally not an issue
+ since glibc will always those relating to the --host
parameter passed to its configure script; e.g., in our case, the compiler
- will be $LFS_TGT-gcc. The binary tools and kernel
- headers can be a bit more complicated. Therefore, we take no risks and use
- the available configure switches to enforce the correct selections. After
+ will be $LFS_TGT-gcc and the readelf
+ tool will be $LFS_TGT-readelf. The kernel headers can
+ be a bit more complicated. Therefore, we take no risks and use
+ the available configure switch to enforce the correct selection. After
the run of configure, check the contents of the
config.make file in the build directory for all important details.
- Note the use of CC="$LFS_TGT-gcc" (with
- $LFS_TGT expanded) 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
+ 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.