123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101 |
- # SOME DESCRIPTIVE TITLE
- # Copyright (C) YEAR Free Software Foundation, Inc.
- # This file is distributed under the same license as the PACKAGE package.
- # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
- #
- #, fuzzy
- msgid ""
- msgstr ""
- "Project-Id-Version: PACKAGE VERSION\n"
- "POT-Creation-Date: 2020-06-17 12:44+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: \n"
- "MIME-Version: 1.0\n"
- "Content-Type: text/plain; charset=UTF-8\n"
- "Content-Transfer-Encoding: 8bit\n"
- #. type: Content of: <sect1><title>
- #: /home/xry111/svn-repos/LFS-BOOK/chapter04/aboutsbus.xml:11
- msgid "About SBUs"
- msgstr ""
- #. type: Content of: <sect1><para>
- #: /home/xry111/svn-repos/LFS-BOOK/chapter04/aboutsbus.xml:13
- msgid ""
- "Many people would like to know beforehand approximately how long it takes to "
- "compile and install each package. Because Linux From Scratch can be built on "
- "many different systems, it is impossible to provide accurate time "
- "estimates. The biggest package (Glibc) will take approximately 20 minutes on "
- "the fastest systems, but could take up to three days on slower systems! "
- "Instead of providing actual times, the Standard Build Unit (SBU) measure "
- "will be used instead."
- msgstr ""
- #. type: Content of: <sect1><para>
- #: /home/xry111/svn-repos/LFS-BOOK/chapter04/aboutsbus.xml:22
- msgid ""
- "The SBU measure works as follows. The first package to be compiled from this "
- "book is binutils in <xref linkend=\"chapter-cross-tools\"/>. The time it "
- "takes to compile this package is what will be referred to as the Standard "
- "Build Unit or SBU. All other compile times will be expressed relative to "
- "this time."
- msgstr ""
- #. type: Content of: <sect1><para>
- #: /home/xry111/svn-repos/LFS-BOOK/chapter04/aboutsbus.xml:28
- msgid ""
- "For example, consider a package whose compilation time is 4.5 SBUs. This "
- "means that if a system took 10 minutes to compile and install the first pass "
- "of binutils, it will take <emphasis>approximately</emphasis> 45 minutes to "
- "build this example package. Fortunately, most build times are shorter than "
- "the one for binutils."
- msgstr ""
- #. type: Content of: <sect1><para>
- #: /home/xry111/svn-repos/LFS-BOOK/chapter04/aboutsbus.xml:34
- msgid ""
- "In general, SBUs are not entirely accurate because they depend on many "
- "factors, including the host system's version of GCC. They are provided here "
- "to give an estimate of how long it might take to install a package, but the "
- "numbers can vary by as much as dozens of minutes in some cases."
- msgstr ""
- #. type: Content of: <sect1><note><para>
- #: /home/xry111/svn-repos/LFS-BOOK/chapter04/aboutsbus.xml:40
- msgid ""
- "For many modern systems with multiple processors (or cores) the compilation "
- "time for a package can be reduced by performing a \"parallel make\" by "
- "either setting an environment variable or telling the "
- "<command>make</command> program how many processors are available. For "
- "instance, an Intel i5-6500 CPU can support four simultaneous processes with:"
- msgstr ""
- #. type: Content of: <sect1><note><screen>
- #: /home/xry111/svn-repos/LFS-BOOK/chapter04/aboutsbus.xml:46
- #, no-wrap
- msgid "<userinput>export MAKEFLAGS='-j4'</userinput>"
- msgstr ""
- #. type: Content of: <sect1><note><para>
- #: /home/xry111/svn-repos/LFS-BOOK/chapter04/aboutsbus.xml:48
- msgid "or just building with:"
- msgstr ""
- #. type: Content of: <sect1><note><screen>
- #: /home/xry111/svn-repos/LFS-BOOK/chapter04/aboutsbus.xml:50
- #, no-wrap
- msgid "<userinput>make -j4</userinput>"
- msgstr ""
- #. type: Content of: <sect1><note><para>
- #: /home/xry111/svn-repos/LFS-BOOK/chapter04/aboutsbus.xml:52
- msgid ""
- "When multiple processors are used in this way, the SBU units in the book "
- "will vary even more than they normally would. In some cases, the make step "
- "will simply fail. Analyzing the output of the build process will also be "
- "more difficult because the lines of different processes will be "
- "interleaved. If you run into a problem with a build step, revert back to a "
- "single processor build to properly analyze the error messages."
- msgstr ""
|