Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
chapter08_gettext 94% 6 80 753 1 11 0 0
chapter08_glibc 72% 64 1,535 13,368 22 27 0 0
chapter08_gmp 88% 5 122 927 1 10 0 0
chapter08_gperf 96% 1 4 70 1 9 0 0
chapter08_grep 82% 6 57 508 2 13 0 0
chapter08_groff 93% 11 113 848 3 13 0 0
chapter08_grub 74% 28 340 2,390 9 13 0 0
chapter08_gzip 98% 1 4 70 1 12 0 0
chapter08_iana-etc 95% 1 4 70 1 4 0 0
chapter08_inetutils 93% 4 36 559 2 13 0 0
chapter08_intltool 97% 1 4 70 1 11 0 0
chapter08_introduction 36% 7 422 2,831 1 1 0 0
chapter08_iproute2 76% 19 208 1,706 3 10 0 0
chapter08_jinja2 0% 17 56 669 17 7 0 0
chapter08_kbd 97% 3 38 319 1 13 0 0
chapter08_kmod 86% 7 78 878 2 9 0 0
chapter08_less 91% 3 12 143 2 11 0 0
chapter08_libcap 78% 10 86 785 1 9 0 0
chapter08_libelf 65% 10 54 659 4 11 0 0
chapter08_libffi 76% 7 188 1,437 2 12 0 0
chapter08_libpipeline 96% 1 4 70 1 11 0 0
chapter08_libtool 82% 7 93 710 2 13 0 0
chapter08_libxcrypt 0% 35 234 2,412 35 11 0 0
chapter08_m4 92% 2 74 545 1 12 0 0
chapter08_make 92% 2 15 160 1 11 0 0
chapter08_man-db 92% 10 81 1,438 4 13 0 0
chapter08_man-pages 77% 5 38 377 2 4 0 0
chapter08_markupsafe 0% 18 68 796 18 7 0 0
chapter08_meson 65% 10 81 981 5 8 0 0
chapter08_mpc 89% 3 8 108 1 8 0 0
chapter08_mpfr 89% 3 16 143 1 7 0 0
chapter08_ncurses 77% 21 326 3,459 4 20 0 0
chapter08_ninja 80% 6 143 1,067 1 10 0 0
chapter08_openssl 71% 13 310 2,701 5 19 0 0
chapter08_patch 96% 1 4 70 1 11 0 0
chapter08_perl 92% 10 164 1,162 1 8 0 0
chapter08_pkgconf 0% 36 155 1,616 36 12 0 0
chapter08_pkgmgt 34% 34 1,997 14,233 10 1 0 0
chapter08_procps 85% 12 99 1,365 2 14 0 0
chapter08_psmisc 93% 3 13 143 2 11 0 0
chapter08_python 56% 25 662 5,205 9 15 0 0
chapter08_readline 83% 7 81 615 3 12 0 0
chapter08_sed 88% 3 18 226 1 9 0 0
chapter08_setuptools 0% 17 61 907 17 6 0 0
chapter08_shadow 76% 39 800 6,528 10 20 0 0
chapter08_stripping 0% 10 531 4,524 10 0 0 0
chapter08_sysklogd 90% 3 44 325 1 8 0 0
chapter08_systemd 67% 72 1,010 8,970 14 34 0 0
chapter08_sysvinit 88% 6 108 758 1 10 0 0
chapter08_tar 83% 5 99 748 2 12 0 0
chapter08_tcl 78% 11 170 1,472 2 11 0 0
chapter08_texinfo 96% 2 7 136 1 14 0 0
chapter08_udev 0% 72 618 6,987 72 18 0 0
chapter08_util-linux 87% 47 656 5,672 12 16 0 0
chapter08_vim 82% 13 354 2,794 2 14 0 0
chapter08_wheel 0% 22 85 951 22 6 0 0
chapter08_xml-parser 96% 1 4 70 1 9 0 0
chapter08_xz 96% 3 10 141 1 14 0 0
chapter08_zlib 85% 4 14 170 2 12 0 0
chapter08_zstd 81% 7 51 447 4 10 0 0
chapter09_bootscripts 92% 7 125 1,027 1 6 0 0
chapter09_chapter09 50% 1 1 14 1 0 0 0
chapter09_clock 96% 1 25 165 0 0 0 0
chapter09_consoled 85% 5 179 1,753 1 3 0 0
chapter09_etcshells 0 0 0 0 0 0 0
chapter09_inputrc 85% 1 126 928 0 0 0 0
chapter09_introduction 60% 6 248 1,563 0 1 0 0
chapter09_introductiond 100% 0 0 0 0 11 0 0
chapter09_locale 60% 14 641 4,981 5 8 0 0
chapter09_network 74% 11 472 3,135 3 4 0 0
chapter09_networkd 68% 20 595 5,486 8 12 0 0
chapter09_symlinks 55% 19 928 6,157 2 0 0 0
chapter09_systemd-custom 86% 7 206 1,995 0 6 0 0
chapter09_udev 60% 21 972 7,612 0 6 0 0
chapter09_usage 66% 35 2,143 15,997 3 14 0 0
chapter10_chapter10 50% 1 1 15 1 0 0 0
chapter10_fstab 87% 2 110 1,396 0 2 0 0
chapter10_grub 62% 11 701 5,695 5 5 0 0
chapter10_introduction 100% 0 0 0 0 1 0 0
chapter10_kernel 65% 34 857 6,209 18 10 0 0
chapter10_kernel_highmem 0% 2 18 280 2 0 0 0
chapter10_kernel_nvme 0% 2 18 266 2 0 0 0
chapter10_kernel_systemd 0% 2 333 4,480 2 0 0 0
chapter10_kernel_sysv 0% 2 234 2,962 2 0 0 0
chapter10_kernel_x2apic 0% 2 47 736 2 0 0 0
chapter11_afterlfs 0% 25 1,041 7,889 25 0 0 0
chapter11_chapter11 50% 1 1 15 1 1 0 0
chapter11_getcounted 0 0 0 0 0 0 0
chapter11_reboot 57% 12 202 1,432 5 4 0 0
chapter11_theend 84% 2 34 338 0 3 0 0
chapter11_whatnow 60% 6 82 611 5 0 0 0
index 0 0 0 0 0 0 0
Glossary Linux From Scratch 12.1 0 0 0 0 0 0 0
part3intro_generalinstructions 52% 12 379 2,395 5 1 0 0
part3intro_introduction 25% 3 177 1,118 0 1 0 0
part3intro_part3intro 0 0 0 0 0 0 0
part3intro_toolchaintechnotes 32% 44 2,211 14,748 9 15 0 0
prologue_architecture 33% 4 309 1,851 0 1 0 0
prologue_audience 37% 5 299 1,780 0 1 0 0
prologue_bookinfo 100% 0 0 0 0 1 0 0

Overview

Project website www.linuxfromscratch.org
Language Chinese (Simplified Han script)
Language code zh_Hans
Text direction Left to right
Case sensitivity Case-insensitive
Number of speakers 1,286,095,292
an hour ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 9,018 86,990 735,697
Translated 76% 6,886 47% 41,389 49% 363,587
Needs editing 14% 1,302 34% 29,838 32% 240,894
Read-only 0% 0 0% 0 0% 0
Failing checks 16% 1,455 15% 13,168 16% 122,269
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 9% 830 18% 15,763 17% 131,216
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 10,465 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 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
FebMarAprMayJunJulAugSepOctNovDecJan

Quick numbers

86,990
Hosted words
9,018
Hosted strings
76%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Resource updated
File “lfs/zh_CN/part3intro/toolchaintechnotes.po” was added. 11 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"/>中，构建、测试并最后一次安装所有软件包，它们组成功能完整的系统。
11 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.
11 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>。
11 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.
11 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 文件系统中。
11 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.
11 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 软件包的一个重要性质 —— 它的构建机制是相当自给自足的，通常不依赖于工具链默认值。
11 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.
11 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 内核提供的各种特性交互。
11 months ago
Browse all changes for this language