diff options
| author | Timothy Bauscher <timothy@linuxfromscratch.org> | 2002-09-18 18:31:39 +0000 |
|---|---|---|
| committer | Timothy Bauscher <timothy@linuxfromscratch.org> | 2002-09-18 18:31:39 +0000 |
| commit | 60ed866798672201b1e79c15a8f38e4f7f76a9a1 (patch) | |
| tree | f14e7aa45bfd86f16e0601212417a0d71edbf844 /chapter01/how.xml | |
| parent | 8d8ab633a0bf92e5f9f95518616120b4d82a5d5a (diff) | |
Fixed typos, removed old command explanation.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2114 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter01/how.xml')
| -rw-r--r-- | chapter01/how.xml | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/chapter01/how.xml b/chapter01/how.xml index fe743db27..5d0ec73f3 100644 --- a/chapter01/how.xml +++ b/chapter01/how.xml @@ -3,7 +3,7 @@ <?dbhtml filename="how.html" dir="chapter01"?> <para>We are going to build the LFS system by using a previously installed -Linux distribution such as Debian, SuSe, Slackware, Mandrake, RedHat, etc. +Linux distribution such as Debian, SuSE, Slackware, Mandrake, RedHat, etc. We will use the existing Linux system as the development platform, because we need tools like a compiler, linker, text editor, and other necessary development tools to build our system. Ordinarily, the required tools are @@ -19,12 +19,14 @@ packages that will form the basic development suite which is used to build the actual system, or needed to resolve circular dependencies. For example, you need a compiler to build a new compiler, and you need a shell in order to install a new shell. The packages in this chapter will be linked -statically. Static linking describes a method of compiling software so that +statically.</para> + +<para>Static linking describes a method of compiling software so that it does not require the presence of libraries when building is complete. The resulting program is able to function on its own. The program is able to do so because the pieces of the program that would normally remain in the libraries are copied from the libraries and built right into the program. -Ordinarily software is built with dynamic linking. This conserves storage +Ordinarily, software is built with dynamic linking. This conserves storage space and increases the efficiency of many programs. We statically link our software in chapter 5 because we will in theory be moving our development system to a virtual environment where the already mentioned |