glibc.xml 8.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180
  1. <sect1 id="ch05-glibc">
  2. <title>Installing Glibc-&glibc-version;</title>
  3. <?dbhtml filename="glibc.html" dir="chapter05"?>
  4. <screen>Estimated build time: &glibc-time-tools;
  5. Estimated required disk space: &glibc-compsize-tools;</screen>
  6. <para>For the package details see <xref linkend="contents-glibc"/>.</para>
  7. <sect2><title>&nbsp;</title><para>&nbsp;</para></sect2>
  8. <sect2>
  9. <title>Glibc installation</title>
  10. <para>Before starting to install Glibc, you must <userinput>cd</userinput>
  11. into the <filename>glibc-&glibc-version;</filename> directory and unpack
  12. Glibc-linuxthreads in that directory, not in the directory where you usually
  13. unpack all the sources.</para>
  14. <note><para>We are going to run the test suite for Glibc in this chapter.
  15. However, it's worth pointing out that running the Glibc test suite here
  16. is considered not as important as running it in
  17. <xref linkend="chapter06"/>.</para></note>
  18. <para>This package is known to behave badly when you have changed its
  19. default optimization flags (including the -march and -mcpu options).
  20. Therefore, if you have defined any environment variables that override
  21. default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
  22. them when building Glibc.</para>
  23. <para>Basically, compiling Glibc in any other way than the book suggests
  24. is putting the stability of your system at risk.</para>
  25. <para>Though it is a harmless message, the install stage of Glibc will
  26. complain about the absence of <filename>/tools/etc/ld.so.conf</filename>.
  27. Fix this annoying little warning with:</para>
  28. <screen><userinput>mkdir /tools/etc
  29. touch /tools/etc/ld.so.conf</userinput></screen>
  30. <para>Also, Glibc has a subtle problem when compiled with GCC &gcc-version;.
  31. Apply the following patch to fix this:</para>
  32. <screen><userinput>patch -Np1 -i ../&glibc-sscanf-patch;</userinput></screen>
  33. <para>The Glibc documentation recommends building Glibc outside of the source
  34. directory in a dedicated build directory:</para>
  35. <screen><userinput>mkdir ../glibc-build
  36. cd ../glibc-build</userinput></screen>
  37. <para>Next, prepare Glibc for compilation:</para>
  38. <screen><userinput>../glibc-&glibc-version;/configure --prefix=/tools \
  39. &nbsp;&nbsp;&nbsp;&nbsp;--disable-profile --enable-add-ons \
  40. &nbsp;&nbsp;&nbsp;&nbsp;--with-headers=/tools/include \
  41. &nbsp;&nbsp;&nbsp;&nbsp;--with-binutils=/tools/bin \
  42. &nbsp;&nbsp;&nbsp;&nbsp;--without-gd</userinput></screen>
  43. <para>The meaning of the configure options:</para>
  44. <itemizedlist>
  45. <listitem><para><userinput>--disable-profile</userinput>: This disables the
  46. building of the libraries with profiling information. Omit this option if you
  47. plan to do profiling.</para></listitem>
  48. <listitem><para><userinput>--enable-add-ons</userinput>: This enables any
  49. add-ons that were installed with Glibc, in our case Linuxthreads.</para></listitem>
  50. <listitem><para><userinput>--with-binutils=/tools/bin</userinput> and
  51. <userinput>--with-headers=/tools/include</userinput>: Strictly speaking
  52. these switches are not required. But they ensure nothing can go wrong with
  53. regard to what kernel headers and Binutils programs get used during the
  54. Glibc build.</para></listitem>
  55. <listitem><para><userinput> --without-gd</userinput>: This switch ensures
  56. that we don't build the <userinput>memusagestat</userinput> program, which
  57. strangely enough insists on linking against the host's libraries (libgd,
  58. libpng, libz, and so forth).</para></listitem>
  59. </itemizedlist>
  60. <para>During this stage you might see the following warning:</para>
  61. <blockquote><screen>configure: WARNING:
  62. *** These auxiliary programs are missing or incompatible versions: msgfmt
  63. *** some features will be disabled.
  64. *** Check the INSTALL file for required versions.</screen></blockquote>
  65. <para>The missing or incompatible <filename>msgfmt</filename> program is
  66. generally harmless, but it's believed it can sometimes cause problems when
  67. running the test suite.</para>
  68. <para>Compile the package:</para>
  69. <screen><userinput>make</userinput></screen>
  70. <para>Run the test suite:</para>
  71. <screen><userinput>make check</userinput></screen>
  72. <para>The Glibc test suite is highly dependent on certain functions of your host
  73. system, in particular the kernel. Additionally, here in this chapter some tests
  74. can be adversely affected by existing tools or environmental issues on the host
  75. system. Of course, these won't be a problem when we run the Glibc test suite
  76. inside the chroot environment of <xref linkend="chapter06"/>. In general, the
  77. Glibc test suite is always expected to pass. However, as mentioned above, some
  78. failures are unavoidable in certain circumstances. Here is a list of the most
  79. common issues we are aware of:</para>
  80. <itemizedlist>
  81. <listitem><para>The <emphasis>math</emphasis> tests sometimes fail when running
  82. on systems where the CPU is not a relatively new genuine Intel or authentic AMD.
  83. Certain optimization settings are also known to be a factor here.</para></listitem>
  84. <listitem><para>The <emphasis>gettext</emphasis> test sometimes fails due to
  85. host system issues. The exact reasons are not yet clear.</para></listitem>
  86. <listitem><para>The <emphasis>atime</emphasis> test sometimes fails when the
  87. LFS partition is mounted with the <emphasis>noatime</emphasis> option, or due
  88. to other file system quirks.</para></listitem>
  89. <listitem><para>The <emphasis>shm</emphasis> test might fail when the host
  90. system is running the devfs file system but doesn't have the tmpfs file system
  91. mounted at <filename>/dev/shm</filename> due to lack of support for tmpfs in
  92. the kernel.</para></listitem>
  93. <listitem><para>When running on older and slower hardware, some tests might
  94. fail due to test timeouts being exceeded.</para></listitem>
  95. </itemizedlist>
  96. <para>In summary, don't worry too much if you see Glibc test suite failures
  97. here in this chapter. The Glibc in <xref linkend="chapter06"/> is the one we'll
  98. ultimately end up using so that is the one we would really like to see pass.
  99. But please keep in mind, even in <xref linkend="chapter06"/> some failures
  100. could still occur -- the <emphasis>math</emphasis>
  101. tests for example. When experiencing a failure, make a note of it, then
  102. continue by reissuing the <userinput>make check</userinput>. The test suite
  103. should pick up where it left off and continue on. You can circumvent this
  104. stop-start sequence by issuing a <userinput>make -k check</userinput>. But if
  105. you do that, be sure to log the output so that you can later peruse the log
  106. file and examine the total number of failures.</para>
  107. <para>Now install the package:</para>
  108. <screen><userinput>make install</userinput></screen>
  109. <para>Different countries and cultures have varying conventions for how to
  110. communicate. These conventions range from very simple ones, such as the format
  111. for representing dates and times, to very complex ones, such as the language
  112. spoken. The "internationalization" of GNU programs works by means of
  113. <emphasis>locales</emphasis>. We'll install the Glibc locales now:</para>
  114. <screen><userinput>make localedata/install-locales</userinput></screen>
  115. <para>An alternative to running the previous command is to install only
  116. those locales which you need or want. This can be achieved by using the
  117. <userinput>localedef</userinput> command. Information on this can be
  118. found in the <filename>INSTALL</filename> file in the
  119. <filename>glibc-&glibc-version;</filename> source. However, there are a number
  120. of locales that are essential for the tests of future packages to pass, in
  121. particular, the <emphasis>libstdc++</emphasis> tests from GCC. The following
  122. instructions, instead of the install-locales target above, will install
  123. the minimum set of locales necessary for the tests to run successfully:</para>
  124. <screen><userinput>mkdir -p /tools/lib/locale
  125. localedef -i de_DE -f ISO-8859-1 de_DE
  126. localedef -i de_DE@euro -f ISO-8859-15 de_DE@euro
  127. localedef -i en_HK -f ISO-8859-1 en_HK
  128. localedef -i en_PH -f ISO-8859-1 en_PH
  129. localedef -i en_US -f ISO-8859-1 en_US
  130. localedef -i es_MX -f ISO-8859-1 es_MX
  131. localedef -i fr_FR -f ISO-8859-1 fr_FR
  132. localedef -i fr_FR@euro -f ISO-8859-15 fr_FR@euro
  133. localedef -i it_IT -f ISO-8859-1 it_IT
  134. localedef -i ja_JP -f EUC-JP ja_JP</userinput></screen>
  135. </sect2>
  136. </sect1>