From dcff0464e8bc95ae211aef1f6aefe57dfade125d Mon Sep 17 00:00:00 2001 From: Alex Gronenwoud Date: Wed, 4 Feb 2004 22:23:18 +0000 Subject: Changing chapter IDs in anticipation. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3221 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter05/glibc.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'chapter05/glibc.xml') diff --git a/chapter05/glibc.xml b/chapter05/glibc.xml index 5b5f1d77e..1340cc9c0 100644 --- a/chapter05/glibc.xml +++ b/chapter05/glibc.xml @@ -90,7 +90,7 @@ so: 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 +inside the chroot environment of . In general, the Glibc test suite is always expected to pass. However, as mentioned above, some failures are unavoidable in certain circumstances. Here is a list of the most common issues we are aware of: @@ -117,9 +117,9 @@ 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 +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. -But please keep in mind, even in some failures +But please keep in mind, even in 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 -- cgit v1.2.3-54-g00ecf