Changeset 4fa86d1 for chapter05/glibc-inst.xml
- Timestamp:
- 09/29/2003 06:08:10 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, 12.2, 12.2-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/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 05ed965
- Parents:
- c1cfddf
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/glibc-inst.xml
rc1cfddf r4fa86d1 78 78 79 79 <para>The missing or incompatible <filename>msgfmt</filename> program is 80 generally harmless and shouldn't cause us any problems.</para> 80 generally harmless, but it's believed it can sometimes cause problems when 81 running the test suite.</para> 81 82 82 <para>Co ntinue with compilingthe package:</para>83 <para>Compile the package:</para> 83 84 84 <para><screen><userinput>make 85 make check 86 make install</userinput></screen></para> 85 <para><screen><userinput>make</userinput></screen></para> 87 86 88 <para>The glibc make check process is highly dependent on certain functions 89 of your host operating system. The most common is a host that fails to mount 90 a tmpfs filesystem at /dev/shm, which may cause glibc tests to fail.</para> 87 <para>Run the test suite:</para> 91 88 92 <para>The locales (used by Glibc to make your Linux system respond in a 93 different language) weren't installed when you ran the previous command, 94 so we have to do that ourselves now:</para> 89 <para><screen><userinput>make check</userinput></screen></para> 90 91 <para>The Glibc test suite is highly dependent on certain functions of your host 92 system, in particular the kernel. Additionally, here in Chapter 5, some tests 93 can be adversely affected by existing tools or environmental issues on the host 94 system. Of course, these won't be a problem when we run the Glibc test suite 95 inside the chroot environment of Chapter 6. In general, the Glibc test suite is 96 always expected to pass. However, as mentioned above, some failures are 97 unavoidable in certain circumstances. Here is a list of the most common issues 98 we are aware of:</para> 99 100 <itemizedlist> 101 <listitem><para>The math tests sometimes fail when running on systems where the 102 CPU is not a relatively new genuine Intel or genuine AMD. Certain optimization 103 settings are also known to be a factor here.</para></listitem> 104 105 <listitem><para>The gettext test sometimes fails due to host system issues. The 106 exact reasons are not yet clear.</para></listitem> 107 108 <listitem><para>The atime test sometimes fails when the LFS parition is mounted 109 with the noatime option or due to other file system quirks.</para></listitem> 110 111 <listitem><para>In general, when running on slower hardware, some tests might 112 fail due to test timeouts being exceeded.</para></listitem> 113 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 filesystem mounted at 116 /dev/shm due to lack of support for tmpfs in the kernel.</para></listitem> 117 </itemizedlist> 118 119 <para>In summary, don't worry too much if you see Glibc test suite failures here 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 in 122 Chapter 6 some failures could still occur, the math tests for example. When 123 experiencing a failure, note the failure then continue on by reissuing the 124 <userinput>make check</userinput>. The test suite should pick up where it left 125 off and continue on. You can circumvent this stop-start sequence by issuing a 126 <userinput>make -k check</userinput>. But If you do that, be sure to log the 127 output so that you can later on peruse the log file and examine the total number 128 of failures.</para> 129 130 <para>Now install the package:</para> 131 132 <para><screen><userinput>make install</userinput></screen></para> 133 134 <para>Different countries and cultures have varying conventions for how to 135 communicate. These conventions range from very simple ones, such as the format 136 for representing dates and times, to very complex ones, such as the language 137 spoken. This "internationalization" works by means of locales. We'll install the 138 Glibc locales now:</para> 95 139 96 140 <para><screen><userinput>make localedata/install-locales</userinput></screen></para> … … 100 144 <userinput>localedef</userinput> command. Information on this can be 101 145 found in the <filename>INSTALL</filename> file in the 102 <filename>glibc-&glibc-version;</filename> tree. However, there are a146 <filename>glibc-&glibc-version;</filename> source. However, there are a 103 147 number of locales that are essential for the tests of future packages 104 148 to pass correctly, in particular, the libstdc++ tests from GCC. The following 105 instructions, in placeof the install-locales command above, will install149 instructions, instead of the install-locales command above, will install 106 150 the minimum set of locales necessary for the tests to run successfully:</para> 107 151
Note:
See TracChangeset
for help on using the changeset viewer.