Changeset 39a9546 for BOOK/final-preps

Timestamp:

Feb 21, 2006, 2:03:39 AM (19 years ago)

Author:

Jim Gifford <clfs@…>

Branches:

clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit

Children:

f9f5662

Parents:

052ede7

Message:

r1017@server (orig r1015): chris | 2006-01-07 10:08:14 -0800
Modification to About Test Suites, and various minor fixes

Location:

BOOK/final-preps

Files:

• abouttestsuites.xml (modified) (2 diffs)
• settingenviron.xml (modified) (1 diff)

BOOK/final-preps/abouttestsuites.xml

@@ -28 +28 @@
 
   <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>
 
@@ -46 +38 @@
   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

BOOK/final-preps/settingenviron.xml

@@ -56 +56 @@
   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">$LFS/cross-tools</filename> as soon as they are
   available without remembering a previous version of the same program in a
   different location.</para>