From d878ce39f84b3896c3bcecc9ca8beafd82cfd008 Mon Sep 17 00:00:00 2001 From: Matthew Burgess Date: Sun, 27 Jun 2004 14:55:19 +0000 Subject: * Moved discussion of glibc test failures to chapter 6, and reworded notes aboutoptional tests. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3854 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter05/glibc.xml | 64 +++++++++++++++++------------------------------------ 1 file changed, 20 insertions(+), 44 deletions(-) (limited to 'chapter05/glibc.xml') diff --git a/chapter05/glibc.xml b/chapter05/glibc.xml index df76dfa1d..b05a59cf1 100644 --- a/chapter05/glibc.xml +++ b/chapter05/glibc.xml @@ -117,53 +117,29 @@ running the test suite. make -Compilation is now complete. As mentioned earlier, we don't recommend -running the test suites for the temporary system here in this chapter. If you -still want to run the Glibc test suite anyway, the following command will do -so: +Compilation is now complete. As mentioned earlier, running the test suites +for the temporary tools installed in this chapter is not mandatory. If you want +to run the Glibc test suite though, the following command will do so: make check -The Glibc test suite is highly dependent on certain functions of your host -system, in particular the kernel. Additionally, here in this chapter some tests -can be adversely affected by existing tools or environmental issues on the host -system. Of course, these won't be a problem when we run the Glibc test suite -inside the chroot environment of . In -general, the Glibc test suite is always expected to pass. However, as mentioned -above, in certain circumstances some failures are unavoidable. Here is a list -of the most common issues we are aware of: - - -The math tests sometimes fail when running -on systems where the CPU is not a relatively new genuine Intel or authentic AMD. -Certain optimization settings are also known to be a factor here. - -The gettext test sometimes fails due to -host system issues. The exact reasons are not yet clear. - -The atime test sometimes fails when the -LFS partition is mounted with the noatime option, or due -to other file system quirks. - -The shm test might fail when the host -system is running the devfs file system but doesn't have the tmpfs file system -mounted at /dev/shm due to lack of support for tmpfs in -the kernel. - -When running on older and slower hardware, some tests might -fail due to test timeouts being exceeded. - - -In summary, don't worry too much if you see Glibc test suite failures -here in this chapter. The Glibc in is -the one we'll ultimately end up using, so that is the one we would really like -to see pass the tests (but even there some failures could still occur -- the -math tests, for example). When experiencing a failure, -make a note of it, then continue by reissuing the make -check. The test suite should pick up where it left off and continue. -You can circumvent this stop-start sequence by issuing a make -k -check. But if you do that, be sure to log the output so that you can -later peruse the log file and examine the total number of failures. +For a discussion of test failures that are of particular +importance, please see . + +In this chapter, some tests can be adversely affected by existing tools or +environmental issues on the host system. In short, don't worry too much if you +see Glibc test suite failures in this chapter. The Glibc in + is the one we'll ultimately end up +using, so that is the one we would really like to see pass the tests (but even +there some failures could still occur -- the math tests, +for example). + +When experiencing a failure, make a note of it, then continue by reissuing +the make check. The test suite should pick up where it left +off and continue. You can circumvent this stop-start sequence by issuing a +make -k check. If you do that though, be sure to log the +output so that you can later peruse the log file and examine the total number of +failures. Though it is a harmless message, the install stage of Glibc will at the end complain about the absence of /tools/etc/ld.so.conf. -- cgit v1.2.3-54-g00ecf