Context Navigation

-              r9d719e2
+              refcb393
   <note>
+    <para>Experience has shown that there is little to be gained from running
+    the test suites in <xref linkend="chapter-temporary-tools"/>. There can be
+    no escaping the fact that the host system always exerts some influence on
+    the tests in that chapter, often causing inexplicable failures. Because
+    the tools built in <xref linkend="chapter-temporary-tools"/> are temporary
+    and eventually discarded, we do not recommend running the test suites in
+    <xref linkend="chapter-temporary-tools"/> for the average reader. The
+    instructions for running those test suites are provided for the benefit of
+    testers and developers, but they are strictly optional.</para>
+    <para>Running the test suites in <xref linkend="chapter-temporary-tools"/>
+    is impossible, since the programs are compiled with a cross-compiler,
+    so are not supposed to be able to run on the build host.</para>
   </note>

chapter04/addinguser.xml

-              r9d719e2
+              refcb393
   <para>Grant <systemitem class="username">lfs</systemitem> full access to
   <filename class="directory">$LFS/tools</filename> by making
+  all directories under <filename class="directory">$LFS</filename> by making
   <systemitem class="username">lfs</systemitem> the directory owner:</para>
 <screen><userinput>chown -v lfs $LFS/tools</userinput></screen>
+<screen><userinput>chown -v lfs $LFS/{usr,lib,var,etc,bin,sbin,lib64,tools}</userinput></screen>
   <para>If a separate working directory was created as suggested, give

r9d719e2	refcb393
14	14	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="introduction.xml"/>
15	15	<!--<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="aboutlfs.xml"/>-->
16		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="creating~~toolsdir~~.xml"/>
	16	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="creatingminlayout.xml"/>
17	17	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="addinguser.xml"/>
18	18	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="settingenviron.xml"/>

r9d719e2	refcb393
12	12
13	13	<para>In this chapter, we will perform a few additional tasks to prepare
14		for building the temporary system. We will create a ~~directory~~ in
	14	for building the temporary system. We will create a set of directories in
15	15	<filename class="directory">$LFS</filename> for the installation of the
16	16	temporary tools, add an unprivileged user to reduce risk,

-              r9d719e2
+              refcb393
 LC_ALL=POSIX
 LFS_TGT=$(uname -m)-lfs-linux-gnu
 PATH=/tools/bin:/bin:/usr/bin
+PATH=$LFS/tools/bin:/bin:/usr/bin
 export LFS LC_ALL LFS_TGT PATH</literal>
 EOF</userinput></screen>
 …
   the shell will always search the <envar>PATH</envar> when a program is to
   be run. As such, the shell will find the newly compiled tools in
   <filename class="directory">$LFS/tools</filename> as soon as they are
+  <filename class="directory">~/tools</filename> as soon as they are
   available without remembering a previous version of the same program in a
   different location.</para>
 …
     <varlistentry>
       <term><parameter>PATH=/tools/bin:/bin:/usr/bin</parameter></term>
+      <term><parameter>PATH=$LFS/tools/bin:/bin:/usr/bin</parameter></term>
       <listitem>
   <para>By putting <filename class="directory">/tools/bin</filename> ahead of the
+  <para>By putting <filename class="directory">$LFS/tools/bin</filename> ahead of the
   standard <envar>PATH</envar>, all the programs installed in <xref
   linkend="chapter-temporary-tools"/> are picked up by the shell immediately after

Note: See TracChangeset for help on using the changeset viewer.