Clearified some issues about building in parallel

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@9339 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Bruce Dubbs 2010-07-18 22:09:01 +00:00
parent 06b8ac0652
commit cef11eaf85
3 changed files with 9 additions and 4 deletions

View File

@ -40,6 +40,11 @@
<listitem> <listitem>
<para>2010-07-18</para> <para>2010-07-18</para>
<itemizedlist> <itemizedlist>
<listitem>
<para>[bdubbs] - Updated discussion of building packages
in parallel. Fixes
<ulink url="&lfs-ticket-root;2712">#2712</ulink>.</para>
</listitem>
<listitem> <listitem>
<para>[bdubbs] - Updated dependencies for GRUB and Glibc. <para>[bdubbs] - Updated dependencies for GRUB and Glibc.
Thanks to splotz90 for the patch. Fixes Thanks to splotz90 for the patch. Fixes

View File

@ -45,7 +45,7 @@
<command>make</command> program how many processors are available. For <command>make</command> program how many processors are available. For
instance, a Core2Duo can support two simultaneous processes with:</para> instance, a Core2Duo can support two simultaneous processes with:</para>
<screen><userinput>set MAKEFLAGS='-j 2'</userinput></screen> <screen><userinput>export MAKEFLAGS='-j 2'</userinput></screen>
<para>or just building with:</para> <para>or just building with:</para>

View File

@ -39,9 +39,9 @@
<para>The order that packages are installed in this chapter needs to be <para>The order that packages are installed in this chapter needs to be
strictly followed to ensure that no program accidentally acquires a path strictly followed to ensure that no program accidentally acquires a path
referring to <filename class="directory">/tools</filename> hard-wired into referring to <filename class="directory">/tools</filename> hard-wired into
it. For the same reason, do not compile packages in parallel. Compiling in it. For the same reason, do not compile separate packages in parallel.
parallel may save time (especially on dual-CPU machines), but it could result Compiling in parallel may save time (especially on dual-CPU machines), but it
in a program containing a hard-wired path to <filename could result in a program containing a hard-wired path to <filename
class="directory">/tools</filename>, which will cause the program to stop class="directory">/tools</filename>, which will cause the program to stop
working when that directory is removed.</para> working when that directory is removed.</para>