From 0ba4e25770e91c82d8ab9c9959cb5142b1e30150 Mon Sep 17 00:00:00 2001 From: Matthew Burgess Date: Sat, 9 Jul 2005 15:24:35 +0000 Subject: Minor typo and grammar fixes (Chris Staub) git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@6463 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter05/toolchaintechnotes.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'chapter05/toolchaintechnotes.xml') diff --git a/chapter05/toolchaintechnotes.xml b/chapter05/toolchaintechnotes.xml index 802e6cf4d..6524c3486 100644 --- a/chapter05/toolchaintechnotes.xml +++ b/chapter05/toolchaintechnotes.xml @@ -69,7 +69,7 @@ linker will be used Binutils is installed first because the -./configure runs of both GCC and Glibc perform +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 @@ -94,7 +94,7 @@ 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: +seen during its run of configure is: checking what assembler to use... /tools/i686-pc-linux-gnu/bin/as @@ -123,7 +123,7 @@ will always use the gcc found in a 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 +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/" -- cgit v1.2.3-54-g00ecf