diff options
| -rw-r--r-- | chapter01/askforhelp.xml | 2 | ||||
| -rw-r--r-- | chapter02/creatingfilesystem.xml | 4 | ||||
| -rw-r--r-- | chapter05/toolchaintechnotes.xml | 6 | ||||
| -rw-r--r-- | prologue/errata.xml | 2 |
4 files changed, 7 insertions, 7 deletions
diff --git a/chapter01/askforhelp.xml b/chapter01/askforhelp.xml index 030387729..f8213b160 100644 --- a/chapter01/askforhelp.xml +++ b/chapter01/askforhelp.xml @@ -58,7 +58,7 @@ need to ask for help.</para> <para>Both the screen output and the contents of various files are useful in determining the cause of compilation problems. The screen output -from the <command>./configure</command> script and the +from the <command>configure</command> script and the <command>make</command> run can be helpful. It is not necessary to include the entire output, but do include enough of the relevant information. Below is an example of the type of diff --git a/chapter02/creatingfilesystem.xml b/chapter02/creatingfilesystem.xml index 7fb10bd41..aa79776a5 100644 --- a/chapter02/creatingfilesystem.xml +++ b/chapter02/creatingfilesystem.xml @@ -11,8 +11,8 @@ be created. The most widely-used system in the Linux world is the second extended file system (ext2), but with newer high-capacity hard disks, journaling file systems are becoming increasingly -popular. We will create an ext2 file system, however build -instructions for other file systems can be found at <ulink +popular. We will create an ext2 file system. Build instructions for other file +systems can be found at <ulink url="&blfs-root;view/svn/postlfs/filesystems.html"/>.</para> <para>To create an ext2 file system on the LFS partition, run the following:</para> 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</para></listitem> </itemizedlist> <para>Binutils is installed first because the -<command>./configure</command> runs of both GCC and Glibc perform +<command>configure</command> 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</userinput> will show all the files successfully opened during the linking.</para> <para>The next package installed is GCC. An example of what can be -seen during its run of <command>./configure</command> is:</para> +seen during its run of <command>configure</command> is:</para> <screen><computeroutput>checking what assembler to use... /tools/i686-pc-linux-gnu/bin/as @@ -123,7 +123,7 @@ will always use the <command>gcc</command> 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 -<command>./configure</command>, check the contents of the +<command>configure</command>, check the contents of the <filename>config.make</filename> file in the <filename class="directory">glibc-build</filename> directory for all important details. Note the use of <parameter>CC="gcc -B/tools/bin/"</parameter> diff --git a/prologue/errata.xml b/prologue/errata.xml index 50c2ba126..bec649d2b 100644 --- a/prologue/errata.xml +++ b/prologue/errata.xml @@ -8,7 +8,7 @@ <?dbhtml filename="errata.html"?> <para>The software used to create an LFS system is constantly being updated and -enhanced. Security warnings, and bug fixes may become available after the LFS +enhanced. Security warnings and bug fixes may become available after the LFS book has been released. To check whether the package versions or instructions in this release of LFS need any modifications to accomodate security vulnerabilities or other bug fixes, please visit <ulink url="&errata;"/> before |