Changeset 05ed965
- Timestamp:
- 09/29/2003 06:13:23 AM (21 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 1c0503f
- Parents:
- 4fa86d1
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/glibc-inst.xml
r4fa86d1 r05ed965 106 106 exact reasons are not yet clear.</para></listitem> 107 107 108 <listitem><para>The atime test sometimes fails when the LFS par ition is mounted108 <listitem><para>The atime test sometimes fails when the LFS partition is mounted 109 109 with the noatime option or due to other file system quirks.</para></listitem> 110 110 … … 113 113 114 114 <listitem><para>The shm test might fail in the circumstances of the host system 115 running the devfs file system but not having the tmpfs file system mounted at115 running the devfs file system but not having the tmpfs file system mounted at 116 116 /dev/shm due to lack of support for tmpfs in the kernel.</para></listitem> 117 117 </itemizedlist> … … 119 119 <para>In summary, don't worry too much if you see Glibc test suite failures here 120 120 in Chapter 5. The Glibc in Chapter 6 is the one we'll ultimately end up using so 121 that is the one we would really like to pass. But please keep in mind, even in122 Chapter 6 some failures could still occur, the math tests for example. When121 that is the one we would really like to see pass. But please keep in mind, even 122 in Chapter 6 some failures could still occur, the math tests for example. When 123 123 experiencing a failure, note the failure then continue on by reissuing the 124 124 <userinput>make check</userinput>. The test suite should pick up where it left -
index.xml
r4fa86d1 r05ed965 4 4 5 5 6 <!ENTITY version "2003092 8">7 <!ENTITY releasedate "September 2 8th, 2003">6 <!ENTITY version "20030929"> 7 <!ENTITY releasedate "September 29th, 2003"> 8 8 <!ENTITY nbsp " "> 9 9
Note:
See TracChangeset
for help on using the changeset viewer.