Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
appendices_acknowledgments 96% 3 22 318 1 1 0 0
appendices_acronymlist 98% 2 6 80 2 0 0 0
appendices_creat-comm 97% 1 2 28 1 0 0 0
appendices_dependencies 54% 135 1,111 12,519 46 25 0 0
appendices_license 75% 1 2 10 1 0 0 0
appendices_mit-lic 83% 1 2 11 0 0 0 0
appendices_scripts 98% 1 2 10 1 0 0 0
appendices_udev-rules 60% 2 20 149 1 0 0 0
chapter01_askforhelp 54% 11 519 3,348 3 1 0 0
chapter01_changelog 69% 51 565 5,550 5 2 0 0
chapter01_chapter01 50% 1 1 14 1 1 0 0
chapter01_how 25% 9 399 2,782 1 0 0 0
chapter01_resources 64% 5 152 1,022 1 2 0 0
chapter01_whatsnew 42% 32 47 844 6 20 0 0
chapter02_aboutlfs 55% 4 287 1,995 0 1 0 0
chapter02_chapter02 50% 1 1 14 1 0 0 0
chapter02_creatingfilesystem 68% 5 252 1,548 1 1 0 0
chapter02_creatingpartition 58% 12 682 4,674 3 3 0 0
chapter02_hostreqs 56% 14 842 6,057 5 3 0 0
chapter02_introduction 100% 0 0 0 0 1 0 0
chapter02_mounting 43% 9 295 2,045 1 1 0 0
chapter02_stages 23% 10 269 1,947 0 5 0 0
chapter03_chapter03 50% 1 1 14 1 0 0 0
chapter03_introduction 55% 9 373 2,489 2 1 0 0
chapter03_packages 90% 34 329 2,964 3 0 0 0
chapter03_patches 67% 9 36 584 0 0 0 0
chapter04_aboutsbus 14% 6 330 1,933 1 1 0 0
chapter04_abouttestsuites 50% 3 140 952 0 0 0 0
chapter04_addinguser 54% 10 326 2,320 1 3 0 0
chapter04_chapter04 50% 1 1 14 1 0 0 0
chapter04_creatingminlayout 14% 6 236 1,667 1 2 0 0
chapter04_introduction 50% 1 77 493 0 1 0 0
chapter04_settingenviron 36% 26 917 7,540 7 6 0 0
chapter05_binutils-pass1 81% 7 155 1,282 1 9 0 0
chapter05_chapter05 50% 1 1 14 1 0 0 0
chapter05_gcc-pass1 71% 13 436 3,624 4 8 0 0
chapter05_glibc 64% 20 421 3,383 5 15 0 0
chapter05_introduction 100% 0 0 0 0 1 0 0
chapter05_libstdc__ 70% 9 213 1,643 2 9 0 0
chapter05_linux-headers 96% 2 20 232 1 5 0 0
chapter06_bash 95% 1 10 221 0 7 0 0
chapter06_binutils-pass2 75% 7 119 1,161 2 12 0 0
chapter06_chapter06 50% 1 1 14 1 0 0 0
chapter06_coreutils 86% 3 53 730 0 8 0 0
chapter06_diffutils 94% 1 7 148 0 8 0 0
chapter06_file 62% 9 131 1,154 6 8 0 0
chapter06_findutils 94% 1 9 224 0 8 0 0
chapter06_gawk 94% 1 7 146 0 9 0 0
chapter06_gcc-pass2 63% 14 330 3,333 7 13 0 0
chapter06_grep 94% 1 7 148 0 8 0 0
chapter06_gzip 100% 0 0 0 0 8 0 0
chapter06_introduction 50% 2 81 601 0 2 0 0
chapter06_m4 100% 0 0 0 0 8 0 0
chapter06_make 100% 0 0 0 0 8 0 0
chapter06_ncurses 60% 18 294 2,817 4 14 0 0
chapter06_patch 100% 0 0 0 0 8 0 0
chapter06_sed 94% 1 7 148 0 8 0 0
chapter06_tar 94% 1 7 182 0 8 0 0
chapter06_xz 89% 2 16 144 1 8 0 0
chapter07_bison 100% 0 0 0 0 8 0 0
chapter07_changingowner 0 0 0 0 0 0 0
chapter07_chapter07 50% 1 1 14 1 0 0 0
chapter07_chroot 22% 7 325 2,571 1 3 0 0
chapter07_cleanup 0% 31 745 5,085 31 0 0 0
chapter07_createfiles 60% 12 466 4,954 2 4 0 0
chapter07_creatingdirs 41% 7 323 2,510 1 1 0 0
chapter07_gettext 100% 0 0 0 0 5 0 0
chapter07_introduction 25% 3 154 1,050 0 1 0 0
chapter07_kernfs 30% 14 489 3,390 6 3 0 0
chapter07_perl 69% 8 121 1,493 3 8 0 0
chapter07_python 91% 2 84 646 1 7 0 0
chapter07_texinfo 100% 0 0 0 0 8 0 0
chapter07_util-linux 77% 7 138 1,510 3 11 0 0
chapter08_aboutdebug 50% 4 117 718 0 0 0 0
chapter08_acl 89% 4 77 747 1 13 0 0
chapter08_attr 92% 3 42 311 1 12 0 0
chapter08_autoconf 93% 3 49 412 2 17 0 0
chapter08_automake 87% 5 61 494 3 11 0 0
chapter08_bash 73% 12 175 1,582 4 13 0 0
chapter08_bc 81% 7 49 433 2 9 0 0
chapter08_binutils 79% 25 242 2,395 8 16 0 0
chapter08_bison 97% 1 4 70 1 13 0 0
chapter08_bzip2 89% 8 60 637 2 13 0 0
chapter08_chapter08 50% 1 1 14 1 0 0 0
chapter08_check 93% 2 6 122 1 9 0 0
chapter08_cleanup 0% 10 151 1,129 10 0 0 0
chapter08_coreutils 93% 24 328 2,431 3 18 0 0
chapter08_dbus 84% 10 128 1,518 4 15 0 0
chapter08_dejagnu 68% 9 46 513 4 9 0 0
chapter08_diffutils 94% 2 14 129 1 11 0 0
chapter08_e2fsprogs 79% 30 397 3,953 7 16 0 0
chapter08_expat 94% 2 10 179 1 14 0 0
chapter08_expect 81% 7 138 1,195 4 9 0 0
chapter08_file 96% 1 4 70 1 12 0 0
chapter08_findutils 90% 4 95 732 1 12 0 0
chapter08_flex 90% 4 64 674 1 15 0 0
chapter08_flit-core 0% 30 170 1,766 30 8 0 0
chapter08_gawk 77% 10 99 1,020 4 15 0 0
chapter08_gcc 61% 69 1,063 8,425 30 20 0 0
chapter08_gdbm 93% 3 57 419 1 11 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
3 minutes 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,457 15% 13,114 16% 121,956
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 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 0 changes 0 changes
MarAprMayJunJulAugSepOctNovDecJanFeb

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