lfs-book-i18n/zh_CN/prologue/architecture.po

msgid ""
msgstr ""
"X-Pootle-Revision: 9999999\n"
"X-Pootle-Path: /zh_CN/lfs/prologue/architecture.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 "LFS Target Architectures"
msgstr "LFS 的目标架构"

#. type: Content of: <sect1><para>
msgid ""
"The primary target architectures of LFS are the AMD/Intel x86 (32-bit)  and "
"x86_64 (64-bit) CPUs.  On the other hand, the instructions in this book are "
"also known to work, with some modifications, with the Power PC and ARM CPUs. "
"To build a system that utilizes one of these CPUs, the main prerequisite, in "
"addition to those on the next page, is an existing Linux system such as an "
"earlier LFS installation, Ubuntu, Red Hat/Fedora, SuSE, or other "
"distribution that targets the architecture that you have. Also note that a "
"32-bit distribution can be installed and used as a host system on a 64-bit "
"AMD/Intel computer."
msgstr ""
"LFS 的主要目标架构是 AMD/Intel 的 x86 (32 位) 和 x86_64 (64 位) CPU。此外，如"
"果对本书中的一些指令作适当的修改，它们也应该适用于 Power PC 和 ARM 架构的 "
"CPU。无论在其中哪种 CPU 上，构建 LFS 都至少需要一个现有的 Linux 系统，例如已"
"经构建好的 LFS 系统，Ubuntu，Rad Hat/Fedora，SuSE，或者其他支持您的硬件架构的"
"发行版，后文中还会介绍其他前提条件。另外，32 位发行版也能在 64 位的 AMD/"
"Intel 计算机上正常运行，并作为 LFS 的构建环境。"

#. type: Content of: <sect1><para>
msgid ""
"For building LFS, the gain of building on a 64-bit system compared to a 32-"
"bit system is minimal.  For example, in a test build of LFS-9.1 on a Core "
"i7-4790 CPU based system, using 4 cores, the following statistics were "
"measured:"
msgstr ""
"对于构建 LFS 来说，构建 64 位系统相较于 32 位系统而言只会获得很小的收益。例"
"如，在使用安装了 Core i7-4790 CPU 的系统测试构建 LFS-9.1 时，我们得到的实验数"
"据为："

#. type: Content of: <sect1><screen>
#, no-wrap
msgid ""
"<computeroutput>Architecture Build Time     Build Size\n"
"32-bit       239.9 minutes  3.6 GB\n"
"64-bit       233.2 minutes  4.4 GB</computeroutput>"
msgstr ""
"<computeroutput>架构        构建时间       系统大小\n"
"32 位       239.9 分钟     3.6 GB\n"
"64 位       233.2 分钟     4.4 GB</computeroutput>"

#. type: Content of: <sect1><para>
msgid ""
"As you can see, on the same hardware, the 64-bit build is only 3% faster and "
"is 22% larger than the 32-bit build. If you plan to use LFS as a LAMP "
"server, or a firewall, a 32-bit CPU may be largely sufficient. On the other "
"hand, several packages in BLFS now need more than 4GB of RAM to be built and/"
"or to run, so that if you plan to use LFS as a desktop, the LFS authors "
"recommend building on a 64-bit system."
msgstr ""
"可以看出，在相同的硬件上，64 位系统的构建仅仅比 32 位快 3%，但占用的磁盘空间"
"却比 32 位系统大 22%。如果您准备用 LFS 系统运行 LAMP 服务器，或者防火墙，那"
"么 32 位 CPU 足以满足需求。然而，BLFS 中的一些软件包在构建或运行过程中可能需"
"要超过 4GB 的内存，因此如果您准备将 LFS 作为桌面系统，LFS 作者推荐构建 64 位"
"系统。"

#. type: Content of: <sect1><para>
msgid ""
"The default 64-bit build that results from LFS is considered a <quote>pure</"
"quote> 64-bit system. That is, it supports 64-bit executables only. Building "
"a <quote>multi-lib</quote> system requires compiling many applications "
"twice, once for a 32-bit system and once for a 64-bit system.  This is not "
"directly supported in LFS because it would interfere with the educational "
"objective of providing the instructions needed for a straightforward base "
"Linux system. Some LFS/BLFS editors maintain a fork of LFS for multilib, "
"which is accessible at <ulink url=\"http://www.linuxfromscratch.org/~thomas/"
"multilib/index.html\"/>. But it is an advanced topic."
msgstr ""
"完全按照本书构建的 LFS 系统是一个<quote>纯粹的</quote> 64 位系统。换句话说，"
"它只能运行 64 位可执行程序。构建一个<quote>multi-lib</quote> 系统需要将许多应"
"用程序编译两次，一次编译为 32 位，另一次编译为 64 位。本书不提供这方面的内"
"容，因为本书的教学目的是提供简洁的基本 Linux 系统的构建方法，讨论 multilib 会"
"和这一目标发生冲突。一些 LFS/BLFS 编辑维护了 LFS 的 multilib 版本，可以在 "
"<ulink url=\"http://www.linuxfromscratch.org/~thomas/multilib/index.html\"/> "
"查阅。但这是一个比较复杂的主题。"