1
0

aboutsbus.po 5.5 KB

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