diff -Nur BOOK/chapter04/aboutsbus.xml BOOK.20100708/chapter04/aboutsbus.xml
old
|
new
|
|
45 | 45 | <command>make</command> program how many processors are available. For |
46 | 46 | instance, a Core2Duo can support two simultaneous processes with:</para> |
47 | 47 | |
48 | | <screen><userinput>set MAKEFLAGS='-j 2'</userinput></screen> |
| 48 | <screen><userinput>export MAKEFLAGS='-j 2'</userinput></screen> |
49 | 49 | |
50 | 50 | <para>or just building with:</para> |
51 | 51 | |
diff -Nur BOOK/chapter06/introduction.xml BOOK.20100708/chapter06/introduction.xml
old
|
new
|
|
39 | 39 | <para>The order that packages are installed in this chapter needs to be |
40 | 40 | strictly followed to ensure that no program accidentally acquires a path |
41 | 41 | referring to <filename class="directory">/tools</filename> hard-wired into |
42 | | it. For the same reason, do not compile packages in parallel. Compiling in |
43 | | parallel may save time (especially on dual-CPU machines), but it could result |
44 | | in a program containing a hard-wired path to <filename |
45 | | class="directory">/tools</filename>, which will cause the program to stop |
46 | | working when that directory is removed.</para> |
| 42 | it. A program containing a hard-wired path to <filename class="directory"> |
| 43 | /tools</filename> will cause the program to stop working when that directory |
| 44 | is removed. So, you must start compile a package after its previous package |
| 45 | has been built over in order.</para> |
47 | 46 | |
48 | 47 | <para>Before the installation instructions, each installation page provides |
49 | 48 | information about the package, including a concise description of what it |