Overview

Project website www.linuxfromscratch.org
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository git@git.linuxfromscratch.org:fr-lfs
Repository branch trunk
Last remote commit Automatic BLFS commit based on fd232b0552b1d249230e0e138c76734f210ed387 25809a687f
Julien Lepiller authored 3 hours ago
Last commit in Weblate Translated using Weblate (Portuguese (Brazil)) 985f4f35e0
User avatar jamenson authored 35 minutes ago
Weblate repository https://translate.linuxfromscratch.org/git/faq/faq/
File mask lfs/*/part3intro/toolchaintechnotes.po
Translation file Download lfs/zh_CN/part3intro/toolchaintechnotes.po
Last change Dec. 6, 2024, 4:19 p.m.
Last author None
a week ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 65 2,307 15,431
Translated 32% 21 5% 127 5% 886
Needs editing 53% 35 69% 1,604 69% 10,764
Read-only 0% 0 0% 0 0% 0
Failing checks 24% 16 30% 707 32% 5,055
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 13% 9 24% 576 24% 3,781
Last 12 months Previous

Activity in last 12 months

0 changes 69 changes 0 changes 0 changes 102 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 5 changes 0 changes 2 changes 0 changes 0 changes 0 changes 0 changes 0 changes 3 changes
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

Quick numbers

2,307
Hosted words
65
Hosted strings
32%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+32%
—
Contributors
—
User avatar None

Resource updated
The “lfs/zh_CN/part3intro/toolchaintechnotes.po” file was changed. a month ago
User avatar None

String added in the repository
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 软件包的一个重要性质 —— 它的构建机制是相当自给自足的，通常不依赖于工具链默认值。
a month ago
User avatar None

Source string changed
The next package installed is GNext comes glibc. The most important considerations for building Gglibc are the compiler, binary tools, and kernel headers. The compiler isand binary tools are generally not an issue since Gglibc will always use the compilerose 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>. The binary tools and 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 switches to enforce the correct selections. 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. Note the use of <parameter>CC="$LFS_TGT-gcc"</parameter> (with <envar>$LFS_TGT</envar> expanded) to control which binary tools are used and the use of the <parameter>-nostdinc</parameter> and <parameter>-isystem</parameter> flags to control the compiler's include search path. These items highlight an important aspect of the Gglibc package&mdash;it is very self-sufficient in terms of its build machinery, and generally does not rely on toolchain defaults.
a month ago
User avatar admin

Resource updated
The “lfs/zh_CN/part3intro/toolchaintechnotes.po” file was changed. 4 months ago
User avatar admin

Resource updated
The “lfs/zh_CN/part3intro/toolchaintechnotes.po” file was changed. 4 months ago
User avatar admin

Resource updated
The “lfs/zh_CN/part3intro/toolchaintechnotes.po” file was changed. 5 months ago
User avatar None

String added in the repository
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> 文件中找到。
5 months ago
User avatar None

Source string changed
AYou 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 Gpackage 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 will beis <filename class="libraryfile">ld-linux.so.2</filename>; it's (<filename class="libraryfile">ld-linux-x86-64.so.2</filename> foron 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 the <filename>shlib-versions</filename> file in the root of the Glibc source tree<ulink url='https://sourceware.org/glibc/wiki/ABIList'>a Glibc wiki page</ulink>.
5 months ago
User avatar admin

Resource updated
The “lfs/zh_CN/part3intro/toolchaintechnotes.po” file was changed. a year ago
User avatar None

String updated in the repository
is the machine where we build programs. Note that this machine is also referred to as the <quote>host.</quote>
指构建程序时使用的机器。注意在某些其他章节，这台机器被称为<quote>host</quote>(宿主)。
a year ago
Browse all translation changes