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 daabb2ab98ba18982452da5fd8b6e27e7fac1cff 416c8c8069
Julien Lepiller authored 10 hours ago
Last commit in Weblate Translated using Weblate (Portuguese (Brazil)) 237c99a959
User avatar jamenson authored 6 hours ago
Weblate repository https://translate.linuxfromscratch.org/git/faq/faq/
File mask lfs/*/chapter08/introduction.po
Translation file Download lfs/zh_CN/chapter08/introduction.po
Last change Jan. 19, 2024, 4:22 a.m.
Last author Weblate Admin
2 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 11 559 3,705
Translated 36% 4 24% 137 23% 874
Needs editing 54% 6 60% 338 60% 2,257
Read-only 0% 0 0% 0 0% 0
Failing checks 9% 1 1% 1 1% 12
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 9% 1 15% 84 15% 574
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 12 changes 0 changes 0 changes 19 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
Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov

Quick numbers

559
Hosted words
11
Hosted strings
36%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+36%
—
Contributors
—
User avatar admin

Resource updated
The “lfs/zh_CN/chapter08/introduction.po” file was changed. 11 months ago
User avatar None

String updated in the repository
For a more complete discussion of libraries, see <ulink url="&blfs-book;introduction/libraries.html"> Libraries: Static or shared?</ulink> in the BLFS book.
关于库的更详细讨论，可以参阅 BLFS 手册中的 <ulink url="&blfs-root;/view/&short-version;/introduction/libraries.html">Libraries: Static or shared?</ulink> 一节。
11 months ago
User avatar None

String updated in the repository
The procedures in this chapter remove or disable installation of most static libraries. Usually this is done by passing a <option>--disable-static</option> option to <command>configure</command>. In other cases, alternate means are needed. In a few cases, especially Glibc and GCC, the use of static libraries remains an essential feature of the package building process.
在本章的安装过程中，我们删除或者禁止安装多数静态库。一般来说，传递 <option>--disable-static</option> 选项给 <command>configure</command> 就可以禁用静态库。然而，某些情况下需要其他手段。在极个别情况下，特别是对于 Glibc 和 GCC，静态库对于一般的软件包构建过程仍然很关键，就不能禁用静态库。
11 months ago
User avatar None

String updated in the repository
In general, the LFS editors discourage building and installing static libraries. Most static libraries have been made obsolete in a modern Linux system. In addition, linking a static library into a program can be detrimental. If an update to the library is needed to remove a security problem, every program that uses the static library will need to be relinked with the new library. Since the use of static libraries is not always obvious, the relevant programs (and the procedures needed to do the linking) may not even be known.
一般来说，LFS 作者不推荐构建和安装静态库。它们是为了某些在现代 Linux 系统中早已过时的原因而存在的。另外，将静态库链接到程序中可能是有害的。如果需要更新这个库以解决安全问题，所有使用该静态库的程序都要重新链接到新版本的库。程序对静态库的使用并不总是显然的，甚至可能无法查明有哪些程序需要重新链接 (以及如何重新链接)。
11 months ago
User avatar None

String updated in the repository
About Libraries
关于库
11 months ago
User avatar None

String updated in the repository
The SBU values and required disk space include test suite data for all applicable packages in <xref linkend="chapter-building-system"/>. SBU values have been calculated using four CPU cores (-j4) for all operations unless specified otherwise.
对于拥有可用的测试套件的软件包，<xref linkend="chapter-building-system"/>中给出的 SBU 值和需要的磁盘空间包含了运行测试套件需要的时间和磁盘空间。SBU 值根据仅使用单个 CPU 核心 (-j1) 进行操作时测得的时间计算。
11 months ago
User avatar None

String updated in the repository
Before the installation instructions, each installation page provides information about the package, including a concise description of what it contains, approximately how long it will take to build, and how much disk space is required during this building process. Following the installation instructions, there is a list of programs and libraries (along with brief descriptions) that the package installs.
在提供安装过程的说明之前，每个页面都提供了软件包的基本信息，包括其内容的简要描述，以及构建过程大概需要的时间和磁盘空间。在安装指令之后，有一个包含该软件包提供的所有程序和库的清单 (以及对它们的简要描述)。
11 months ago
User avatar None

String updated in the repository
On the other hand, we keep the optimizations enabled by the default configuration of the packages. In addition, we sometimes explicitly enable an optimized configuration provided by a package but not enabled by default. The package maintainers have already tested these configurations and consider them safe, so it's not likely they would break the build. Generally the default configuration already enables <option>-O2</option> or <option>-O3</option>, so the resulting system will still run very fast without any customized optimization, and be stable at the same time.
 
11 months ago
User avatar None

String updated in the repository
We do not recommend using customized optimizations. They can make a program run slightly faster, but they may also cause compilation difficulties, and problems when running the program. If a package refuses to compile with a customized optimization, try to compile it without optimization and see if that fixes the problem. Even if the package does compile when using a customized optimization, there is the risk it may have been compiled incorrectly because of the complex interactions between the code and the build tools. Also note that the <option>-march</option> and <option>-mtune</option> options using values not specified in the book have not been tested. This may cause problems with the toolchain packages (Binutils, GCC and Glibc). The small potential gains achieved by customizing compiler optimizations are often outweighed by the risks. First-time builders of LFS are encouraged to build without custom optimizations.
我们不推荐在编译中使用优化。编译优化可以使程序跑得稍微快一点，但也可能在编译或运行的过程中带来问题。如果一个软件包在打开优化时无法编译，试着关闭优化再编译它。即使一个软件包在打开优化时可以编译，由于源代码和编译工具的复杂相互作用，仍然存在编译不正确的风险。另外请注意，除本书明确说明外，设定 <option>-march</option> 和 <option>-mtune</option> 是未经验证的。它们可能在工具链软件包 (Binutils、GCC 和 Glibc) 中引发问题。使用编译优化带来的微小性能增益往往不值得冒编译错误的风险。我们建议第一次构建 LFS 的读者不要使用自定义的优化选项。这样，得到的系统仍然会运行得很快，而且会很稳定。
11 months ago
User avatar None

String updated in the repository
The installation of this software is straightforward. Although in many cases the installation instructions could be made shorter and more generic, we have opted to provide the full instructions for every package to minimize the possibilities for mistakes. The key to learning what makes a Linux system work is to know what each package is used for and why you (or the system) may need it.
软件的安装过程是简单直接的。尽管很多时候可以把安装说明写得更短、更通用，我们还是选择为每个包提供完整的安装流程，以尽量减小出错的可能。学习 Linux 系统工作原理的关键就是要知道每个包的作用，以及您 (或者系统) 为什么需要它。
11 months ago
Browse all translation changes