Changeset 3f5b367 in clfs-sysroot for BOOK/final-system/common
- Timestamp:
- Jan 5, 2009, 1:20:31 AM (16 years ago)
- Branches:
- master
- Children:
- f74898c
- Parents:
- 7400ff8
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
BOOK/final-system/common/introduction.xml
r7400ff8 r3f5b367 11 11 <title>Introduction</title> 12 12 13 <para os="a">In this chapter, we enter the building site and start 14 constructing the CLFS system in earnest. The installation of this 15 software is straightforward. Although in many cases the installation 16 instructions could be made shorter and more generic, we have opted 17 to provide the full instructions for every package to minimize the 18 possibilities for mistakes. The key to learning what makes a Linux 19 system work is to know what each package is used for and why the user 20 (or the system) needs it. For every installed package, a summary of 21 its contents is given, followed by concise descriptions of each 22 program and library the package installed.</para> 13 <para os="a">In this chapter, we use the cross-compile tools to build 14 the final CLFS system. The installation of this software is 15 straightforward. Although in many cases the installation instructions 16 could be made shorter and more generic, we have opted to provide the full 17 instructions for every package to minimize the possibilities for mistakes. 18 The key to learning what makes a Linux system work is to know what each 19 package is used for and why the user (or the system) needs it. For every 20 installed package, a summary of its contents is given, followed by concise 21 descriptions of each program and library the package installed.</para> 23 22 24 23 <para os="b">If using compiler optimizations, please review the … … 40 39 41 40 <para os="c">The order that packages are installed in this chapter needs to 42 be strictly followed to ensure that no program accidentally acquires a 43 path referring to <filename class="directory">/tools</filename> 44 hard-wired into it. For the same reason, do not compile packages in 45 parallel. Compiling in parallel may save time (especially on dual-CPU 46 machines), but it could result in a program containing a hard-wired 47 path to <filename class="directory">/tools</filename>, which will 48 cause the program to stop working when that directory is 49 removed.</para> 41 be strictly followed to ensure that all package dependencies are 42 fulfilled.</para> 50 43 51 44 <para os="d">To keep track of which package installs particular files, a
Note:
See TracChangeset
for help on using the changeset viewer.