lfs-book-i18n/zh_CN/chapter08/introduction.po

msgid ""
msgstr ""
"X-Pootle-Revision: 9999999\n"
"X-Pootle-Path: /zh_CN/lfs/chapter08/introduction.po\n"
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2020-08-08 19:28+0800\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: zh_CN\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Translate Toolkit 2.2.5\n"

#. type: Content of: <sect1><title>
msgid "Introduction"
msgstr "概述"

#. type: Content of: <sect1><para>
msgid "In this chapter, we start constructing the LFS system in earnest."
msgstr "在本章中，我们将真正开始构造 LFS 系统。"

#. type: Content of: <sect1><para>
msgid ""
"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."
msgstr ""
"软件的安装过程是简单直接的。尽管很多时候可以把安装说明写得更短、更通用，我们"
"还是选择为每个包提供完整的安装流程，以尽量减小出错的可能。学习 Linux 系统工作"
"原理的关键就是要知道每个包的作用，以及您 (或者系统)  为什么需要它。"

#. type: Content of: <sect1><para>
msgid ""
"We do not recommend using 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 when "
"using optimization, try to compile it without optimization and see if that "
"fixes the problem. Even if the package does compile when using optimization, "
"there is the risk it may have been compiled incorrectly because of the "
"complex interactions between the code and 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 in using compiler optimizations are often outweighed by the risks.  "
"First-time builders of LFS are encouraged to build without custom "
"optimizations. The subsequent system will still run very fast and be stable "
"at the same time."
msgstr ""
"我们不推荐在编译中使用优化。编译优化可以使程序跑得稍微快一点，但也可能在编译"
"或运行的过程中带来问题。如果一个软件包在打开优化时无法编译，试着关闭优化再编"
"译它。即使一个软件包在打开优化时可以编译，由于源代码和编译工具的复杂相互作"
"用，仍然存在编译不正确的风险。另外请注意，除本书明确说明外，设定 <option>-"
"march</option> 和 <option>-mtune</option> 是未经验证的。它们可能在工具链软件"
"包 (Binutils、GCC 和 Glibc) 中引发问题。使用编译优化带来的微小性能增益往往不"
"值得冒编译错误的风险。我们建议第一次构建 LFS 的读者不要使用自定义的优化选项。"
"这样，得到的系统仍然会运行得很快，而且会很稳定。"

#. type: Content of: <sect1><para>
msgid ""
"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."
msgstr ""
"在提供安装过程的说明之前，每个页面都提供了软件包的基本信息，包括其内容的简要"
"描述，以及构建过程大概需要的时间和磁盘空间。在安装指令之后，有一个包含该软件"
"包提供的所有程序和库的清单 (以及对它们的简要描述)。"

#. type: Content of: <sect1><note><para>
msgid ""
"The SBU values and required disk space includes test suite data for all "
"applicable packages in <xref linkend=\"chapter-building-system\"/>. SBU "
"values have been calculated using a single CPU core (-j1) for all operations."
msgstr ""
"对于拥有可用的测试套件的软件包，<xref linkend=\"chapter-building-system\"/>中"
"给出的 SBU 值和需要的磁盘空间包含了运行测试套件需要的时间和磁盘空间。SBU 值根"
"据仅使用单个 CPU 核心 (-j1) 进行操作时测得的时间计算。"

#. type: Content of: <sect1><sect2><title>
msgid "About libraries"
msgstr "关于库"

#. type: Content of: <sect1><sect2><para>
msgid ""
"In general, the LFS editors discourage building and installing static "
"libraries.  The original purpose for most static libraries has 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, all programs that use the static library will "
"need to be relinked to 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."
msgstr ""
"一般来说，LFS 作者不推荐构建和安装静态库。它们是为了某些在现代 Linux 系统中早"
"已过时的原因而存在的。另外，将静态库链接到程序中可能是有害的。如果需要更新这"
"个库以解决安全问题，所有使用该静态库的程序都要重新链接到新版本的库。程序对静"
"态库的使用并不总是显然的，甚至可能无法查明有哪些程序需要重新链接 (以及如何重"
"新链接)。"

#. type: Content of: <sect1><sect2><para>
msgid ""
"In the procedures in this chapter, we 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 essential to the general package building "
"process."
msgstr ""
"在本章的安装过程中，我们删除或者禁止安装多数静态库。一般来说，传递 <option>--"
"disable-static</option> 选项给 <command>configure</command> 就可以禁用静态"
"库。然而，某些情况下需要其他手段。在极个别情况下，特别是对于 Glibc 和 GCC，静"
"态库对于一般的软件包构建过程仍然很关键，就不能禁用静态库。"

#. type: Content of: <sect1><sect2><para>
msgid ""
"For a more complete discussion of libraries, see the discussion <ulink url="
"\"&blfs-root;/view/&short-version;/introduction/libraries.html\"> Libraries: "
"Static or shared?</ulink> in the BLFS book."
msgstr ""
"关于库的更详细讨论，可以参阅 BLFS 手册中的 <ulink url=\"&blfs-root;/view/"
"&short-version;/introduction/libraries.html\">Libraries: Static or shared?</"
"ulink> 一节。"