2. Linux From Scratch 12.3
3. part3intro_toolchaintechnotes
4. Search

Filters

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with screenshots • has:screenshot
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

has:check

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Last updated
• Number of words
• Number of comments
• Number of failing checks
• Key
• String location

	Translation	Source string	Target string
	Linux From Scratch 12.3/part3intro_toolchaintechnotes — Chinese (Simplified Han script)	Let us first define some terms used in this context.	首先我们定义讨论交叉编译时常用的术语：
	Linux From Scratch 12.3/part3intro_toolchaintechnotes — English	is the machine where we build programs. Note that this machine is also referred to as the <quote>host.</quote>	is the machine where we build programs. Note that this machine is also referred to as the <quote>host.</quote>
	Linux From Scratch 12.3/part3intro_toolchaintechnotes — Chinese (Simplified Han script)	is the machine where we build programs. Note that this machine is also referred to as the <quote>host.</quote>	指构建程序时使用的机器。注意在某些其他章节，这台机器被称为<quote>host</quote>(宿主)。
	Linux From Scratch 12.3/part3intro_toolchaintechnotes — Chinese (Simplified Han script)	As an example, let us imagine the following scenario (sometimes referred to as <quote>Canadian Cross</quote>). We have a compiler on a slow machine only, let's call it machine A, and the compiler ccA. We also have a fast machine (B), but no compiler for (B), and we want to produce code for a third, slow machine (C). We will build a compiler for machine C in three stages.	例如，我们考虑下列场景 (有时称为<quote>Canadian Cross</quote>)：我们仅在一台运行缓慢的机器上有编译器，称这台机器为 A，这个编译器为 ccA。我们还有一台运行较快的机器 (B)，但它没有安装编译器，而我们希望为另一台缓慢的机器 (C) 生成代码。如果要为 C 构建编译器，可以通过三个阶段完成：
	Linux From Scratch 12.3/part3intro_toolchaintechnotes — Chinese (Simplified Han script)	Build cross-compiler cc1 using ccA on machine A.	在机器 A 上，使用 ccA 构建交叉编译器 cc1
	Linux From Scratch 12.3/part3intro_toolchaintechnotes — Chinese (Simplified Han script)	Build cross-compiler cc2 using cc1 on machine A.	在机器 A 上，使用 cc1 构建交叉编译器 cc2
	Linux From Scratch 12.3/part3intro_toolchaintechnotes — Chinese (Simplified Han script)	Build compiler ccC using cc2 on machine B.	在机器 B 上，使用 cc2 构建交叉编译器 ccC
	Linux From Scratch 12.3/part3intro_toolchaintechnotes — Chinese (Simplified Han script)	Rebuild and test ccC using ccC on machine C.	在机器 C 上，用 ccC 重新构建它本身，并测试
	Linux From Scratch 12.3/part3intro_toolchaintechnotes — Chinese (Simplified Han script)	You should also be aware of the name of the platform's dynamic linker, often referred to as the dynamic loader (not to be confused with the standard linker <command>ld</command> that is part of binutils). The dynamic linker provided by package glibc finds and loads the shared libraries needed by a program, prepares the program to run, and then runs it. The name of the dynamic linker for a 32-bit Intel machine is <filename class="libraryfile">ld-linux.so.2</filename>; it's <filename class="libraryfile">ld-linux-x86-64.so.2</filename> on 64-bit systems. A sure-fire way to determine the name of the dynamic linker is to inspect a random binary from the host system by running: <userinput>readelf -l &lt;name of binary&gt; | grep interpreter</userinput> and noting the output. The authoritative reference covering all platforms is in <ulink url='https://sourceware.org/glibc/wiki/ABIList'>a Glibc wiki page</ulink>.	另外注意平台的动态链接器的名称，它又被称为动态加载器 (不要和 Binutils 中的普通链接器 <command>ld</command> 混淆)。动态链接器由 Glibc 提供，它寻找并加载程序所需的共享库，为程序运行做好准备，然后运行程序。在 32 位 Intel 机器上动态链接器的名称是 <filename class="libraryfile">ld-linux.so.2</filename> (在 64 位系统上是 <filename class="libraryfile">ld-linux-x86-64.so.2</filename>)。一个确定动态链接器名称的准确方法是从宿主系统找一个二进制可执行文件，然后执行：<userinput>readelf -l &lt;二进制文件名&gt; | grep interpreter</userinput> 并观察输出。包含所有平台的权威参考可以在 Glibc 源码树根目录的 <filename>shlib-versions</filename> 文件中找到。
	Linux From Scratch 12.3/part3intro_toolchaintechnotes — Chinese (Simplified Han script)	In order to fake a cross-compilation in LFS, the name of the host triplet is slightly adjusted by changing the &quot;vendor&quot; field in the <envar>LFS_TGT</envar> variable so it says &quot;lfs&quot;. We also use the <parameter>--with-sysroot</parameter> option when building the cross-linker and cross-compiler, to tell them where to find the needed host files. This ensures that none of the other programs built in <xref linkend="chapter-temporary-tools"/> can link to libraries on the build machine. Only two stages are mandatory, plus one more for tests.	为了将本机伪装成交叉编译目标机器，我们在 <envar>LFS_TGT</envar> 变量中，对宿主系统三元组的 &quot;vendor&quot; 域进行修改。我们还会在构建交叉链接器和交叉编译器时使用 <parameter>--with-sysroot</parameter> 选项，指定查找所需的 host 系统文件的位置。这保证在<xref linkend="chapter-temporary-tools"/>中的其他程序在构建时不会链接到宿主 (build) 系统的库。前两个阶段是必要的，第三个阶段可以用于测试：
	Linux From Scratch 12.3/part3intro_toolchaintechnotes — Chinese (Simplified Han script)	Build cross-compiler cc1 using cc-pc on pc.	在 pc 上使用 cc-pc 构建交叉编译器 cc1
	Linux From Scratch 12.3/part3intro_toolchaintechnotes — Chinese (Simplified Han script)	Build compiler cc-lfs using cc1 on pc.	在 pc 上使用 cc1 构建 cc-lfs
	Linux From Scratch 12.3/part3intro_toolchaintechnotes — Chinese (Simplified Han script)	Rebuild and test cc-lfs using cc-lfs on lfs.	在 lfs 上使用 cc-lfs 重新构建并测试它本身
	Linux From Scratch 12.3/part3intro_toolchaintechnotes — Chinese (Simplified Han script)	Binutils installs its assembler and linker in two locations, <filename class="directory">$LFS/tools/bin</filename> and <filename class="directory">$LFS/tools/$LFS_TGT/bin</filename>. The tools in one location are hard linked to the other. An important facet of the linker is its library search order. Detailed information can be obtained from <command>ld</command> by passing it the <parameter>--verbose</parameter> flag. For example, <command>$LFS_TGT-ld --verbose | grep SEARCH</command> will illustrate the current search paths and their order. (Note that this example can be run as shown only while logged in as user <systemitem class="username">lfs</systemitem>. If you come back to this page later, replace <command>$LFS_TGT-ld</command> with <command>ld</command>).	Binutils 将汇编器和链接器安装在两个位置，一个是 <filename class="directory">$LFS/tools/bin</filename>，另一个是 <filename class="directory">$LFS/tools/$LFS_TGT/bin</filename>。这两个位置中的工具互为硬链接。链接器的一项重要属性是它搜索库的顺序，通过向 <command>ld</command> 命令加入 <parameter>--verbose</parameter> 参数，可以得到关于搜索路径的详细信息。例如，<command>ld --verbose | grep SEARCH</command> 会输出当前的搜索路径及其顺序。此外，通过编译一个样品 (dummy) 程序并向链接器 <command>ld</command> 传递 <parameter>--verbose</parameter> 参数，可以知道哪些文件被链接。例如，<command>gcc dummy.c -Wl,--verbose 2&gt;&amp;1 | grep succeeded</command> 将显示所有在链接过程中被成功打开的文件。
	Linux From Scratch 12.3/part3intro_toolchaintechnotes — English	<computeroutput>checking what assembler to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/as checking what linker to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/ld</computeroutput>	<computeroutput>checking what assembler to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/as checking what linker to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/ld</computeroutput>
	Linux From Scratch 12.3/part3intro_toolchaintechnotes — English	This is important for the reasons mentioned above. It also demonstrates that gcc's configure script does not search the PATH directories to find which tools to use. However, during the actual operation of <command>gcc</command> itself, the same search paths are not necessarily used. To find out which standard linker <command>gcc</command> will use, run: <command>$LFS_TGT-gcc -print-prog-name=ld</command>. (Again, remove the <command>$LFS_TGT-</command> prefix if coming back to this later.)	This is important for the reasons mentioned above. It also demonstrates that gcc's configure script does not search the PATH directories to find which tools to use. However, during the actual operation of <command>gcc</command> itself, the same search paths are not necessarily used. To find out which standard linker <command>gcc</command> will use, run: <command>$LFS_TGT-gcc -print-prog-name=ld</command>. (Again, remove the <command>$LFS_TGT-</command> prefix if coming back to this later.)
	Linux From Scratch 12.3/part3intro_toolchaintechnotes — Chinese (Simplified Han script)	This is important for the reasons mentioned above. It also demonstrates that gcc's configure script does not search the PATH directories to find which tools to use. However, during the actual operation of <command>gcc</command> itself, the same search paths are not necessarily used. To find out which standard linker <command>gcc</command> will use, run: <command>$LFS_TGT-gcc -print-prog-name=ld</command>. (Again, remove the <command>$LFS_TGT-</command> prefix if coming back to this later.)	基于我们上面论述的原因，这些输出非常重要。这说明 GCC 的配置脚本没有在 PATH 变量指定的目录中搜索工具。然而，在 <command>gcc</command> 的实际运行中，未必会使用同样的搜索路径。为了查询 <command>gcc</command> 会使用哪个链接器，需要执行以下命令：<command>$LFS_TGT-gcc -print-prog-name=ld</command>。
	Linux From Scratch 12.3/part3intro_toolchaintechnotes — Chinese (Simplified Han script)	Detailed information can be obtained from <command>gcc</command> by passing it the <parameter>-v</parameter> command line option while compiling a program. For example, <command>$LFS_TGT-gcc -v <replaceable>example.c</replaceable></command> (or without <command> $LFS_TGT-</command> if coming back later) will show detailed information about the preprocessor, compilation, and assembly stages, including <command>gcc</command>'s search paths for included headers and their order.	通过向 <command>gcc</command> 传递 <parameter>-v</parameter> 参数，可以知道在编译样品程序时发生的细节。例如，<command>gcc -v dummy.c</command> 会输出预处理、编译和汇编阶段中的详细信息，包括 <command>gcc</command> 的包含文件搜索路径和顺序。
	Linux From Scratch 12.3/part3intro_toolchaintechnotes — Chinese (Simplified Han script)	Next comes glibc. The most important considerations for building glibc are the compiler, binary tools, and kernel headers. The compiler and binary tools are generally not an issue since glibc will always use those relating to the <parameter>--host</parameter> parameter passed to its configure script; e.g., in our case, the compiler will be <command>$LFS_TGT-gcc</command> and the <command>readelf</command> tool will be <command>$LFS_TGT-readelf</command>. The kernel headers can be a bit more complicated. Therefore, we take no risks and use the available configure switch to enforce the correct selection. After the run of <command>configure</command>, check the contents of the <filename>config.make</filename> file in the <filename class="directory">build</filename> directory for all important details. These items highlight an important aspect of the glibc package&mdash;it is very self-sufficient in terms of its build machinery, and generally does not rely on toolchain defaults.	下一步安装 Glibc。在构建 Glibc 时需要着重考虑编译器，二进制工具，以及内核头文件。编译器一般不成问题，Glibc 总是使用传递给配置脚本的 <parameter>--host</parameter> 参数相关的编译器。例如，在我们的例子中，使用的编译器是 <command>$LFS_TGT-gcc</command>。但二进制工具和内核头文件的问题比较复杂。安全起见，我们使用配置脚本提供的开关，保证正确的选择。在 <command>configure</command> 脚本运行完成后，可以检查 <filename>build</filename> 目录中的 <filename>config.make</filename> 文件，了解全部重要的细节。注意参数 <parameter>CC="$LFS_TGT-gcc"</parameter> (其中 <envar>$LFS_TGT</envar> 会被展开) 控制构建系统使用正确的二进制工具，而参数 <parameter>-nostdinc</parameter> 和 <parameter>-isystem</parameter> 控制编译器的包含文件搜索路径。这些事项凸显了 Glibc 软件包的一个重要性质 —— 它的构建机制是相当自给自足的，通常不依赖于工具链默认值。