Context Navigation

-              r960d87a
+              r6a8ff5c
   <note>
+    <para>Experience has shown that there is little to be gained
+    from running the test suites in <xref
+    linkend="chapter-testsuite-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-testsuite-tools"/> are temporary and
+    eventually discarded, we do not recommend running the test suites in
+    <xref linkend="chapter-testsuite-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>It is not possible to run testsuites when cross-compiling, so there
+    are no instructions given for running testsuites until
+    <xref linkend="chapter-building-system"/>.</para>
   </note>
 …
   most likely cause is that the host system does not have the
   <systemitem class="filesystem">devpts</systemitem> file system set up
   correctly. This issue is discussed in greater detail in <xref
   linkend="chapter-testsuite-tools"/>.</para>
+  correctly. This issue is discussed in greater detail at
+  <ulink url="http://www.linuxfromscratch.org/lfs/faq.html#no-ptys"/>.</para>
   <para>Sometimes package test suites will fail, but for reasons which the

final-preps/settingenviron.xml

r960d87a	r6a8ff5c
56	56	the shell will always search the <envar>PATH</envar> when a program is to
57	57	be run. As such, the shell will find the newly compiled tools in
58		<filename class="directory">$LFS/tools</filename> as soon as they are
	58	<filename class="directory">$LFS/cross-tools</filename> as soon as they are
59	59	available without remembering a previous version of the same program in a
60	60	different location.</para>

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