aboutsummaryrefslogtreecommitdiffstats
path: root/chapter05
diff options
context:
space:
mode:
authorJeremy Utley <jeremy@linuxfromscratch.org>2003-09-09 20:59:10 +0000
committerJeremy Utley <jeremy@linuxfromscratch.org>2003-09-09 20:59:10 +0000
commit431f48d1b8cb6cbd73be48f4096798f4d1a4cca5 (patch)
tree6a44780841fadf6d51f27861b36e4439ce4f07ba /chapter05
parentc825bdcb3e7a8cd3aa09e6e5d8a82d953d311987 (diff)
Added some notes regarding failed tests
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2756 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05')
-rw-r--r--chapter05/dejagnu-inst.xml6
-rw-r--r--chapter05/glibc-inst.xml4
2 files changed, 9 insertions, 1 deletions
diff --git a/chapter05/dejagnu-inst.xml b/chapter05/dejagnu-inst.xml
index c1794e6ac..4a22085f9 100644
--- a/chapter05/dejagnu-inst.xml
+++ b/chapter05/dejagnu-inst.xml
@@ -13,7 +13,11 @@
make install</userinput></screen></para>
<para>This completes the testing tools. We can now rebuild GCC and Binutils
-to link them against the new Glibc, and test them properly.</para>
+to link them against the new Glibc, and test them properly. One thing to note,
+however, is that these test suites are highly dependent on the features
+supported by your host distribution. Most notably, a host distribution which
+does not properly support the devpts filesystem will cause most of these tests
+to fail.</para>
</sect2>
diff --git a/chapter05/glibc-inst.xml b/chapter05/glibc-inst.xml
index b76027bc8..61dc8bb83 100644
--- a/chapter05/glibc-inst.xml
+++ b/chapter05/glibc-inst.xml
@@ -89,6 +89,10 @@ would require you to regenerate the binary files.</para>
make check
make install</userinput></screen></para>
+<para>The glibc make check process is highly dependent on certain functions
+of your host operating system. The most common is a host that fails to mount
+a tmpfs filesystem at /dev/shm, which may cause glibc tests to fail.</para>
+
<para>The locales (used by Glibc to make your Linux system respond in a
different language) weren't installed when you ran the previous command,
so we have to do that ourselves now:</para>