glibc.xml 8.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246
  1. <?xml version="1.0" encoding="ISO-8859-1"?>
  2. <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
  3. "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
  4. <!ENTITY % general-entities SYSTEM "../general.ent">
  5. %general-entities;
  6. ]>
  7. <sect1 id="ch-tools-glibc" role="wrap">
  8. <?dbhtml filename="glibc.html"?>
  9. <sect1info condition="script">
  10. <productname>glibc</productname>
  11. <productnumber>&glibc-version;</productnumber>
  12. <address>&glibc-url;</address>
  13. </sect1info>
  14. <title>Glibc-&glibc-version;</title>
  15. <indexterm zone="ch-tools-glibc">
  16. <primary sortas="a-Glibc">Glibc</primary>
  17. <secondary>tools</secondary>
  18. </indexterm>
  19. <sect2 role="package">
  20. <title/>
  21. <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
  22. href="../chapter08/glibc.xml"
  23. xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
  24. <segmentedlist>
  25. <segtitle>&buildtime;</segtitle>
  26. <segtitle>&diskspace;</segtitle>
  27. <seglistitem>
  28. <seg>&glibc-tmp-sbu;</seg>
  29. <seg>&glibc-tmp-du;</seg>
  30. </seglistitem>
  31. </segmentedlist>
  32. </sect2>
  33. <sect2 role="installation">
  34. <title>Installation of Glibc</title>
  35. <para>First, create a symbolic link for LSB compliance. Additionally,
  36. for x86_64, create a compatibility symbolic link required for proper
  37. operation of the dynamic library loader:</para>
  38. <screen><userinput remap="pre">case $(uname -m) in
  39. i?86) ln -sfv ld-linux.so.2 $LFS/lib/ld-lsb.so.3
  40. ;;
  41. x86_64) ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64
  42. ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64/ld-lsb-x86-64.so.3
  43. ;;
  44. esac</userinput></screen>
  45. <note>
  46. <para>
  47. The above command is correct. The <command>ln</command> command has
  48. a few syntactic versions, so be sure to check
  49. <command>info coreutils ln</command> and <filename>ln(1)</filename>
  50. before reporting what you may think is an error.
  51. </para>
  52. </note>
  53. <para>Some of the Glibc programs use the non-FHS compliant
  54. <filename class="directory">/var/db</filename> directory to store their
  55. runtime data. Apply the following patch to make such programs store their
  56. runtime data in the FHS-compliant locations:</para>
  57. <screen><userinput remap="pre">patch -Np1 -i ../glibc-&glibc-version;-fhs-1.patch</userinput></screen>
  58. <para>The Glibc documentation recommends building Glibc
  59. in a dedicated build directory:</para>
  60. <screen><userinput remap="pre">mkdir -v build
  61. cd build</userinput></screen>
  62. <para>Next, prepare Glibc for compilation:</para>
  63. <screen><userinput remap="configure">../configure \
  64. --prefix=/usr \
  65. --host=$LFS_TGT \
  66. --build=$(../scripts/config.guess) \
  67. --enable-kernel=&min-kernel; \
  68. --with-headers=$LFS/usr/include \
  69. libc_cv_slibdir=/lib</userinput></screen>
  70. <!--
  71. libc_cv_forced_unwind=yes \
  72. libc_cv_c_cleanup=yes</userinput></screen> -->
  73. <variablelist>
  74. <title>The meaning of the configure options:</title>
  75. <varlistentry>
  76. <term><parameter>--host=$LFS_TGT, --build=$(../scripts/config.guess)</parameter></term>
  77. <listitem>
  78. <para>The combined effect of these switches is that Glibc's build system
  79. configures itself to be cross-compiled, using the cross-linker and
  80. cross-compiler in <filename class="directory">$LFS/tools</filename>.</para>
  81. </listitem>
  82. </varlistentry>
  83. <varlistentry>
  84. <term><parameter>--enable-kernel=&min-kernel;</parameter></term>
  85. <listitem>
  86. <para>This tells Glibc to compile the library with support
  87. for &min-kernel; and later Linux kernels. Workarounds for older
  88. kernels are not enabled.</para>
  89. </listitem>
  90. </varlistentry>
  91. <varlistentry>
  92. <term><parameter>--with-headers=$LFS/usr/include</parameter></term>
  93. <listitem>
  94. <para>This tells Glibc to compile itself against the headers
  95. recently installed to the $LFS/usr/include directory, so that
  96. it knows exactly what features the kernel has and can optimize
  97. itself accordingly.</para>
  98. </listitem>
  99. </varlistentry>
  100. <varlistentry>
  101. <term><parameter>libc_cv_slibdir=/lib</parameter></term>
  102. <listitem>
  103. <para>This ensures that the library is installed in /lib instead
  104. of the default /lib64 on 64 bit machines.</para>
  105. </listitem>
  106. </varlistentry>
  107. <varlistentry>
  108. <term><option>libc_cv_include_x86_isa_level=no</option></term>
  109. <listitem>
  110. <para>This disables <quote>x86 ISA needed</quote> property in
  111. Glibc libraries. Use it <emphasis role="bold">if</emphasis>
  112. you are building Glibc with <option>-march</option> option in
  113. <envar>CFLAGS</envar>, to workaround an issue in Glibc-2.33
  114. breaking it.</para>
  115. </listitem>
  116. </varlistentry>
  117. </variablelist>
  118. <para>During this stage the following warning might appear:</para>
  119. <blockquote>
  120. <screen><computeroutput>configure: WARNING:
  121. *** These auxiliary programs are missing or
  122. *** incompatible versions: msgfmt
  123. *** some features will be disabled.
  124. *** Check the INSTALL file for required versions.</computeroutput></screen>
  125. </blockquote>
  126. <para>The missing or incompatible <command>msgfmt</command> program is
  127. generally harmless. This <command>msgfmt</command> program is part of the
  128. Gettext package which the host distribution should provide.</para>
  129. <note><para>There have been reports that this package may fail when
  130. building as a "parallel make". If this occurs, rerun the make command
  131. with a "-j1" option.</para></note>
  132. <para>Compile the package:</para>
  133. <screen><userinput remap="make">make</userinput></screen>
  134. <para>Install the package:</para>
  135. <warning><para>If <envar>LFS</envar> is not properly set, and despite the
  136. recommendations, you are building as
  137. <systemitem class="username">root</systemitem>, the next command will
  138. install the newly built glibc to your host system, which most likely
  139. will render it unusable. So double check that the environment is
  140. correctly set, before running the following command.</para></warning>
  141. <screen><userinput remap="install">make DESTDIR=$LFS install</userinput></screen>
  142. <variablelist>
  143. <title>The meaning of the <command>make install</command> option:</title>
  144. <varlistentry>
  145. <term><parameter>DESTDIR=$LFS</parameter></term>
  146. <listitem>
  147. <para>The <envar>DESTDIR</envar> make variable is used by almost all
  148. packages to define the location where the package should be
  149. installed. If it is not set, it defaults to the root (<filename
  150. class="directory">/</filename>) directory. Here we specify that
  151. the package be installed in <filename class="directory">$LFS
  152. </filename>, which will become the root after <xref linkend=
  153. "ch-tools-chroot"/>.</para>
  154. </listitem>
  155. </varlistentry>
  156. </variablelist>
  157. <caution>
  158. <para>At this point, it is imperative to stop and ensure that the basic
  159. functions (compiling and linking) of the new toolchain are working as
  160. expected. To perform a sanity check, run the following commands:</para>
  161. <screen><userinput>echo 'int main(){}' &gt; dummy.c
  162. $LFS_TGT-gcc dummy.c
  163. readelf -l a.out | grep '/ld-linux'</userinput></screen>
  164. <para>If everything is working correctly, there should be no errors,
  165. and the output of the last command will be of the form:</para>
  166. <screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen>
  167. <para>Note that for 32-bit machines, the interpreter name will be
  168. <filename>/lib/ld-linux.so.2</filename>.</para>
  169. <para>If the output is not shown as above or there was no output at all,
  170. then something is wrong. Investigate and retrace the steps to find out
  171. where the problem is and correct it. This issue must be resolved before
  172. continuing on.</para>
  173. <para>Once all is well, clean up the test files:</para>
  174. <screen><userinput>rm -v dummy.c a.out</userinput></screen>
  175. </caution>
  176. <note><para>Building packages in the next chapter will serve as an
  177. additional check that the toolchain has been built properly. If some
  178. package, especially binutils-pass2 or gcc-pass2, fails to build, it is
  179. an indication that something has gone wrong with the
  180. previous Binutils, GCC, or Glibc installations.</para></note>
  181. <para>Now that our cross-toolchain is complete, finalize the installation
  182. of the limits.h header. For doing so, run a utility provided by the GCC
  183. developers:</para>
  184. <screen><userinput>$LFS/tools/libexec/gcc/$LFS_TGT/&gcc-version;/install-tools/mkheaders</userinput></screen>
  185. </sect2>
  186. <sect2 role="content">
  187. <title/>
  188. <para>Details on this package are located in
  189. <xref linkend="contents-glibc" role="."/></para>
  190. </sect2>
  191. </sect1>