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 12.1
Last remote commit Add pt_BR translation e751a3b16e
Julien Lepiller authored 6 months ago
Weblate repository https://translate.linuxfromscratch.org/git/linux-from-scratch-12-1/index/
File mask lfs/*/part3intro/toolchaintechnotes.po
Translation file Download lfs/zh_CN/part3intro/toolchaintechnotes.po
Last change March 4, 2024, 7:25 a.m.
Last author None
3 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 65 2,338 15,634
Translated 32% 21 5% 127 5% 886
Needs editing 53% 35 69% 1,635 70% 10,967
Read-only 0% 0 0% 0 0% 0
Failing checks 23% 15 25% 604 27% 4,339
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 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 101 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

2,338
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
File “lfs/zh_CN/part3intro/toolchaintechnotes.po” was added. 8 months ago
User avatar None

String updated in the repository
Upon entering the chroot environment in <xref linkend="chapter-chroot-temporary-tools"/>, the temporary installations of programs needed for the proper operation of the toolchain are performed. From this point onwards, the core toolchain is self-contained and self-hosted. In <xref linkend="chapter-building-system"/>, final versions of all the packages needed for a fully functional system are built, tested, and installed.
在<xref linkend="chapter-chroot-temporary-tools"/>中，进入 chroot 环境后，首先安装 libstdc++。之后临时性地安装工具链的正常工作所必须的程序。还要构建测试其他程序时必须的程序。此后，核心工具链成为自包含的本地工具链。在<xref linkend="chapter-building-system"/>中，构建、测试并最后一次安装所有软件包，它们组成功能完整的系统。
8 months ago
User avatar None

Source string changed
Upon entering the chroot environment in <xref linkend="chapter-chroot-temporary-tools"/>, the first task is to install libstdc++. Then temporary installations of programs needed for the proper operation of the toolchain are performed. Programs needed for testing other programs are also built. From this point onwards, the core toolchain is self-contained and self-hosted. In <xref linkend="chapter-building-system"/>, final versions of all the packages needed for a fully functional system are built, tested, and installed.
8 months ago
User avatar None

String updated in the repository
At the end of <xref linkend="chapter-temporary-tools"/> the native LFS compiler is installed. First binutils-pass2 is built, in the same <envar>DESTDIR</envar> directory as the other programs, then the second pass of gcc is constructed, omitting some non-critical libraries. Due to some weird logic in gcc's configure script, <envar>CC_FOR_TARGET</envar> ends up as <command>cc</command> when the host is the same as the target, but different from the build system. This is why <parameter>CC_FOR_TARGET=$LFS_TGT-gcc</parameter> is declared explicitly as one of the configuration options.
在<xref linkend="chapter-temporary-tools"/>一节的末尾，构建 lfs 本地编译器。首先使用和其他程序相同的 <envar>DESTDIR</envar> 第二次构建 binutils，然后第二次构建 GCC，构建时忽略 libstdc++ 和其他不重要的库。由于 GCC 配置脚本的一些奇怪逻辑，<envar>CC_FOR_TARGET</envar> 变量在 host 系统和 target 相同，但与 build 不同时，被设定为 <command>cc</command>。因此我们必须显式地在配置选项中指定 <parameter>CC_FOR_TARGET=$LFS_TGT-gcc</parameter>。
8 months ago
User avatar None

Source string changed
At the end of <xref linkend="chapter-temporary-tools"/> the native lfsLFS compiler is installed. First binutils-pass2 is built, within the same <envar>DESTDIR</envar> installdirectory as the other programs, then the second pass of GCCgcc is constructed, omitting libstdc++ and other non-importantsome non-critical libraries. Due to some weird logic in GCCgcc's configure script, <envar>CC_FOR_TARGET</envar> ends up as <command>cc</command> when the host is the same as the target, but is different from the build system. This is why <parameter>CC_FOR_TARGET=$LFS_TGT-gcc</parameter> is putdeclared explicitly intoas one of the configureation options.
8 months ago
User avatar None

String updated in the repository
As mentioned above, the standard C++ library is compiled next, followed in <xref linkend="chapter-temporary-tools"/> by other programs that must be cross-compiled to break circular dependencies at build time. The install step of all those packages uses the <envar>DESTDIR</envar> variable to force installation in the LFS filesystem.
正如前文所述，接下来构建 C++ 标准库，然后是<xref linkend="chapter-temporary-tools"/>中那些需要自身才能构建的程序后。在安装这些软件包时使用 <envar>DESTDIR</envar> 变量，将它安装到 LFS 文件系统中。
8 months ago
User avatar None

Source string changed
As saimentioned above, the standard C++ library is compiled next, followed in <xref linkend="chapter-temporary-tools"/> by all other programs that need themselves to be built.must be cross-compiled to break circular dependencies at build time. The install step of all those packages uses the <envar>DESTDIR</envar> variable to have the programs landforce installation into the LFS filesystem.
8 months ago
User avatar None

String updated in the repository
Next comes glibc. The most important considerations for building glibc are the compiler, binary tools, and kernel headers. The compiler is generally not an issue since glibc will always use the compiler 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 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 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 软件包的一个重要性质 —— 它的构建机制是相当自给自足的，通常不依赖于工具链默认值。
8 months 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 is generally not an issue since Gglibc will always use the compiler 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 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.
8 months ago
User avatar None

String updated in the repository
Next up: sanitized Linux API headers. These allow the standard C library (glibc) to interface with features that the Linux kernel will provide.
下一步安装“净化的” (sanitized) Linux API 头文件。这允许 C 标准库 (Glibc) 与 Linux 内核提供的各种特性交互。
8 months ago
Browse all translation changes