lfs-book-zh_CN/chapter05/glibc.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
  <!ENTITY % general-entities SYSTEM "../general.ent">
  %general-entities;
]>

<sect1 id="ch-tools-glibc" role="wrap">
  <?dbhtml filename="glibc.html"?>

  <sect1info condition="script">
    <productname>glibc</productname>
    <productnumber>&glibc-version;</productnumber>
    <address>&glibc-url;</address>
  </sect1info>

  <title>Glibc-&glibc-version;</title>

  <indexterm zone="ch-tools-glibc">
    <primary sortas="a-Glibc">Glibc</primary>
    <secondary>tools</secondary>
  </indexterm>

  <sect2 role="package">
    <title/>

    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    href="../chapter06/glibc.xml"
    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>

    <segmentedlist>
      <segtitle>&buildtime;</segtitle>
      <segtitle>&diskspace;</segtitle>

      <seglistitem>
        <seg>&glibc-ch5-sbu;</seg>
        <seg>&glibc-ch5-du;</seg>
      </seglistitem>
    </segmentedlist>

  </sect2>

  <sect2 role="installation">
    <title>安装 Glibc</title>

    <!--para>The Glibc documentation recommends building Glibc 
    in a dedicated build directory:</para-->
    <para>Glibc 文档推荐在一个专用目录中构建 Glibc：</para>

<screen><userinput remap="pre">mkdir -v build
cd       build</userinput></screen>

    <para>然后准备编译 Glibc：</para>

<screen><userinput remap="configure">../configure                             \
      --prefix=/tools                    \
      --host=$LFS_TGT                    \
      --build=$(../scripts/config.guess) \
      --enable-kernel=&min-kernel;             \
      --with-headers=/tools/include      \
      libc_cv_forced_unwind=yes          \
      libc_cv_c_cleanup=yes</userinput></screen>

    <variablelist>
      <title>配置选项的含义：</title>

      <varlistentry>
        <term><parameter>--host=$LFS_TGT, --build=$(../scripts/config.guess)</parameter></term>
        <listitem>
          <!--para>The combined effect of these switches is that Glibc's build system
          configures itself to cross-compile, using the cross-linker and
          cross-compiler in <filename class="directory">/tools</filename>.</para-->
          <para>在它们的共同作用下，Glibc 的构建系统将自身配置为使用
          	  <filename class="directory">/tools</filename>
			  中的交叉链接器和交叉编译器，进行交叉编译。</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><parameter>--enable-kernel=&min-kernel;</parameter></term>
        <listitem>
          <!--para>This tells Glibc to compile the library with support
          for &min-kernel; and later Linux kernels.  Workarounds for older
          kernels are not enabled.</para-->
	      <para>该选项告诉 Glibc 编译出支持 &min-kernel; 版或者更新的
			  Linux 内核，这样就不会使用那些为更老内核准备的替代方案。
		  </para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><parameter>--with-headers=/tools/include</parameter></term>
        <listitem>
          <!--para>This tells Glibc to compile itself against the headers recently
          installed to the tools directory, so that it knows exactly what
          features the kernel has and can optimize itself accordingly.</para-->
	      <para>该选项告诉 Glibc 在刚刚安装到 tools
			  目录中的头文件基础上进行编译，这样它就知道内核拥有哪些特性，
			  并据此对自身进行优化。</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><parameter>libc_cv_forced_unwind=yes</parameter></term>
        <listitem>
          <!--para>The linker installed during
          <xref linkend="ch-tools-binutils-pass1"/> was cross-compiled and as
          such cannot be used until Glibc has been installed.  This means that
          the configure test for force-unwind support will fail, as it relies on
          a working linker.  The libc_cv_forced_unwind=yes variable is passed in
          order to inform <command>configure</command> that force-unwind
		  support is available without it having to run the test.</para-->
	      <para>在 <xref linkend="ch-tools-binutils-pass1"/>
			  中安装的链接器是交叉链接器，在 Glibc 安装前不能正常使用。
			  这导致对于强制栈展开特性的配置检查失败，
			  因为该检查需要正常工作的链接器。
			  libc_cv_forced_unwind=yes 变量被传递给
			  <command>configure</command> 脚本，
			  从而表明强制栈展开支持是可用的，不需要进行测试。</para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term><parameter>libc_cv_c_cleanup=yes</parameter></term>
        <listitem>
          <!--para>Similarly, we pass libc_cv_c_cleanup=yes through to the
          <command>configure</command> script so that the test is skipped and C
          cleanup handling support is configured.</para-->
          <para>类似的，我们传递 libc_cv_c_cleanup=yes 给
			  <command>configure</command> 脚本，从而跳过相关测试，
			  并表明 C 清理支持可用。</para>
        </listitem>
      </varlistentry>
<!--  <varlistentry>
        <term><parameter>libc_cv_ctors_header=yes</parameter></term>
        <listitem>
          <para>Similarly, we pass libc_cv_ctors_header=yes through to the
          <command>configure</command> script so that the test is skipped and
          gcc constructor support is configured.</para>
        </listitem>
      </varlistentry>-->

    </variablelist>

    <para>在当前阶段，可能出现下列警告：</para>

    <blockquote>
<screen><computeroutput>configure: WARNING:
*** These auxiliary programs are missing or
*** incompatible versions: msgfmt
*** some features will be disabled.
*** Check the INSTALL file for required versions.</computeroutput></screen>
    </blockquote>

    <!--para>The missing or incompatible <command>msgfmt</command> program is
    generally harmless. This <command>msgfmt</command> program is part of the
    Gettext package which the host distribution should provide.</para-->
    <para><command>msgfmt</command>程序的缺失或不兼容一般是无害的。
		<command>msgfmt</command>程序是 Gettext 软件包的一部分，
		宿主发行版应该提供它。</para>

    <note><!--para>There have been reports that this package may fail when 
    building as a "parallel make".  If this occurs, rerun the make command
	with a "-j1" option.</para-->
        <para>有报告称该软件包在并行构建时可能失败，如果发生了这种情况，
			加上 "-j1" 选项重新执行 make 命令。</para>
	</note>

    <para>编译该软件包：</para>

<screen><userinput remap="make">make</userinput></screen>

    <para>安装该软件包：</para>

<screen><userinput remap="install">make install</userinput></screen>

  <caution>
    <!--para>At this point, it is imperative to stop and ensure that the basic
    functions (compiling and linking) of the new toolchain are working as
    expected. To perform a sanity check, run the following commands:</para-->
    <para>现在我们不可避免地要停下确认新工具链的各基本功能（编译和链接）
		能如我们所预期的那样工作。执行以下命令进行完整性检查：</para>

<screen><userinput>echo 'int main(){}' &gt; dummy.c
$LFS_TGT-gcc dummy.c
readelf -l a.out | grep ': /tools'</userinput></screen>

    <!--para>If everything is working correctly, there should be no errors,
    and the output of the last command will be of the form:</para-->
    <para>如果所有东西正常工作，那么应该没有错误，
		而且最后一行命令应该输出下列格式的内容：</para>

<screen><computeroutput>[Requesting program interpreter: /tools/lib64/ld-linux-x86-64.so.2]</computeroutput></screen>

    <!--para>Note that for 32-bit machines, the interpreter name will be
    <filename>/tools/lib/ld-linux.so.2</filename>.</para-->
    <para>注意，对于 32 位机器，解释器的名字将会是
		<filename>/tools/lib/ld-linux.so.2</filename>。</para>

    <!--para>If the output is not shown as above or there was no output at all,
    then something is wrong. Investigate and retrace the steps to find out
    where the problem is and correct it. This issue must be resolved before
    continuing on.</para-->
    <para>如果输出不像上面描述的那样，或者根本没有输出，就说明出了问题。
		检查并重新跟踪各个步骤，找到出问题的地方并修正它。
		在继续构建之前，必须解决这个问题。</para>

	<!--para>Once all is well, clean up the test files:</para-->
    <para>检验步骤顺利完成后，清理测试文件：</para>

<screen><userinput>rm -v dummy.c a.out</userinput></screen>

  </caution>

  <note><!--para>Building Binutils in the section after next will serve as an
  additional check that the toolchain has been built properly. If Binutils
  fails to build, it is an indication that something has gone wrong with the
  previous Binutils, GCC, or Glibc installations.</para-->
	  <para>在 <xref linkend="ch-tools-binutils-pass2"/> 中，构建 Binutils
		  能够对工具链是否正常构建进行额外检查。如果 Binutils 不能构建，
		  说明在之前安装 Binutils 、GCC 或者 Glibc 时出了问题。
	  </para>
  </note>

  </sect2>

  <sect2 role="content">
    <title/>

    <para>该软件包的详细信息可以在
    <xref linkend="contents-glibc"/> 中找到。</para>

  </sect2>

</sect1>