diff --git a/chapter06/bash.xml b/chapter06/bash.xml
index d462d2631..d00e685ca 100644
--- a/chapter06/bash.xml
+++ b/chapter06/bash.xml
@@ -45,9 +45,9 @@
Prepare Bash for compilation:
-./configure --prefix=/usr \
- --build=$(support/config.guess) \
- --host=$LFS_TGT \
+./configure --prefix=/usr \
+ --build=$(sh support/config.guess) \
+ --host=$LFS_TGT \
--without-bash-malloc
diff --git a/lfs-latest-git.php b/lfs-latest-git.php
index 32c8150ca..d4f331697 100644
--- a/lfs-latest-git.php
+++ b/lfs-latest-git.php
@@ -17,7 +17,7 @@ $regex[ 'intltool' ] = "/^.*Latest version is (\d[\d\.]+\d).*$/";
$regex[ 'less' ] = "/^.*current released version is less-(\d+).*$/";
$regex[ 'mpfr' ] = "/^mpfr-([\d\.]+)\.tar.*$/";
$regex[ 'Python' ] = "/^.*Latest Python 3.*Python (3[\d\.]+\d).*$/";
-$regex[ 'systemd' ] = "/^.*v([\d]+)$/";
+$regex[ 'systemd' ] = "/^.*systemd v([\d]+)$/";
//$regex[ 'sysvinit' ] = "/^.*sysvinit-([\d\.]+)dsf\.tar.*$/";
$regex[ 'tzdata' ] = "/^.*tzdata([\d]+[a-z]).*$/";
$regex[ 'xz' ] = "/^.*xz-([\d\.]*\d).*$/";
diff --git a/part3intro/toolchaintechnotes.xml b/part3intro/toolchaintechnotes.xml
index aae3d7f3a..53c1f4a23 100644
--- a/part3intro/toolchaintechnotes.xml
+++ b/part3intro/toolchaintechnotes.xml
@@ -300,12 +300,11 @@
its library search order. Detailed information can be obtained from
ld by passing it the --verbose
flag. For example, $LFS_TGT-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,
- $LFS_TGT-gcc dummy.c -Wl,--verbose 2>&1 | grep succeeded
- will show all the files successfully opened during the linking.
+ will illustrate the current search paths and their order. Note that this
+ example can be run as shown only while being user
+ lfs. If you come back to this
+ page later, replace $LFS_TGT-ld with just
+ ld.
The next package installed is gcc. An example of what can be
seen during its run of configure is:
@@ -318,14 +317,18 @@ checking what linker to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/ldgcc itself, the same search paths are not
necessarily used. To find out which standard linker gcc
- will use, run: $LFS_TGT-gcc -print-prog-name=ld.
+ will use, run: $LFS_TGT-gcc -print-prog-name=ld. Again,
+ remove the $LFS_TGT- part if coming back to this
+ later.
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
+ a program. For example, $LFS_TGT-gcc -v
+ example.c (or without
+ $LFS_TGT- if coming back later to this) will show
detailed information about the preprocessor, compilation, and assembly
- stages, including gcc's included search paths and their
- order.
+ stages, including gcc's search paths for included
+ headers and their order.
Next installed are sanitized Linux API headers. These allow the
standard C library (glibc) to interface with features that the Linux