1
0

aboutsbus.po 5.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107
  1. msgid ""
  2. msgstr ""
  3. "Project-Id-Version: PACKAGE VERSION\n"
  4. "POT-Creation-Date: 2020-08-08 19:28+0800\n"
  5. "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
  6. "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
  7. "Language-Team: LANGUAGE <LL@li.org>\n"
  8. "Language: zh_CN\n"
  9. "MIME-Version: 1.0\n"
  10. "Content-Type: text/plain; charset=UTF-8\n"
  11. "Content-Transfer-Encoding: 8bit\n"
  12. "X-Generator: Translate Toolkit 2.2.5\n"
  13. #. type: Content of: <sect1><title>
  14. msgid "About SBUs"
  15. msgstr "关于 SBU"
  16. #. type: Content of: <sect1><para>
  17. msgid ""
  18. "Many people would like to know beforehand approximately how long it takes to "
  19. "compile and install each package. Because Linux From Scratch can be built on "
  20. "many different systems, it is impossible to provide accurate time estimates. "
  21. "The biggest package (Glibc) will take approximately 20 minutes on the "
  22. "fastest systems, but could take up to three days on slower systems! Instead "
  23. "of providing actual times, the Standard Build Unit (SBU) measure will be "
  24. "used instead."
  25. msgstr ""
  26. "许多人想在编译和安装各个软件包之前,了解这一过程大概需要多少时间。由于 Linux "
  27. "From Scratch 可以在许多不同系统上构建,我们无法直接给出估计时间。例如,最大的"
  28. "软件包 (Glibc) 在最快的系统上只要大约 20 分钟就能构建好,而在一些较慢的系统"
  29. "上需要 3 天!因此,我们不提供实际时间,而是以标准构建单位 (SBU) 衡量时间。"
  30. #. type: Content of: <sect1><para>
  31. msgid ""
  32. "The SBU measure works as follows. The first package to be compiled from this "
  33. "book is binutils in <xref linkend=\"chapter-cross-tools\"/>. The time it "
  34. "takes to compile this package is what will be referred to as the Standard "
  35. "Build Unit or SBU. All other compile times will be expressed relative to "
  36. "this time."
  37. msgstr ""
  38. "下面给出标准构建单位的测量方法。本书中构建的第一个软件包是 <xref linkend="
  39. "\"chapter-cross-tools\"/> 中的 Binutils,定义编译它需要的时间为标准构建单位,"
  40. "缩写为 SBU。其他软件包的编译时间用 SBU 为单位表示。"
  41. #. type: Content of: <sect1><para>
  42. msgid ""
  43. "For example, consider a package whose compilation time is 4.5 SBUs. This "
  44. "means that if a system took 10 minutes to compile and install the first pass "
  45. "of binutils, it will take <emphasis>approximately</emphasis> 45 minutes to "
  46. "build this example package. Fortunately, most build times are shorter than "
  47. "the one for binutils."
  48. msgstr ""
  49. "例如,考虑一个编译时间是 4.5 SBU 的软件包。如果在某个系统上,需要 10 分钟来编"
  50. "译和安装第一轮的 Binutils,那么<emphasis>大概</emphasis>需要 45 分钟才能构建"
  51. "这个软件包。幸运的是,多数软件包构建时间比 Binutils 少。"
  52. #. type: Content of: <sect1><para>
  53. msgid ""
  54. "In general, SBUs are not entirely accurate because they depend on many "
  55. "factors, including the host system's version of GCC. They are provided here "
  56. "to give an estimate of how long it might take to install a package, but the "
  57. "numbers can vary by as much as dozens of minutes in some cases."
  58. msgstr ""
  59. "一般来说,SBU 不是完全准确的。这是由于它受到许多因素的影响,包括宿主系统的 "
  60. "GCC 版本。SBU 只能用来估计安装一个软件包可能需要的时间,估计结果的误差在个别"
  61. "情况下可能达到几十分钟。"
  62. #. type: Content of: <sect1><note><para>
  63. msgid ""
  64. "For many modern systems with multiple processors (or cores) the compilation "
  65. "time for a package can be reduced by performing a \"parallel make\" by "
  66. "either setting an environment variable or telling the <command>make</"
  67. "command> program how many processors are available. For instance, an Intel "
  68. "i5-6500 CPU can support four simultaneous processes with:"
  69. msgstr ""
  70. "对于许多拥有多个处理器 (或处理器核心) 的现代系统,可以显著缩短软件包的编译时"
  71. "间,设置环境变量或者直接告诉 <command>make</command> 命令有多少个可用的处理"
  72. "器,即可进行并行构建。例如,一块 Intel i5-6500 CPU 可以支持 4 个同时运行的进"
  73. "程,可以设定:"
  74. #. type: Content of: <sect1><note><screen>
  75. #, no-wrap
  76. msgid "<userinput>export MAKEFLAGS='-j4'</userinput>"
  77. msgstr "<userinput>export MAKEFLAGS='-j4'</userinput>"
  78. #. type: Content of: <sect1><note><para>
  79. msgid "or just building with:"
  80. msgstr "或者直接用以下命令构建:"
  81. #. type: Content of: <sect1><note><screen>
  82. #, no-wrap
  83. msgid "<userinput>make -j4</userinput>"
  84. msgstr "<userinput>make -j4</userinput>"
  85. #. type: Content of: <sect1><note><para>
  86. msgid ""
  87. "When multiple processors are used in this way, the SBU units in the book "
  88. "will vary even more than they normally would. In some cases, the make step "
  89. "will simply fail. Analyzing the output of the build process will also be "
  90. "more difficult because the lines of different processes will be "
  91. "interleaved. If you run into a problem with a build step, revert back to a "
  92. "single processor build to properly analyze the error messages."
  93. msgstr ""
  94. "用这种方式使用多个处理器时,SBU 值将会发生变化,有时甚至变得比正常值还大。某"
  95. "些情况下,还会导致 make 命令失败。另外,分析构建过程的的输出也会变得困难,因"
  96. "为不同进程的输出行会交错在一起。如果在构建过程中出现问题,需要使用单处理器进"
  97. "行构建,才能更好地分析错误消息。"