diff options
| author | Marc Heerdink <gimli@linuxfromscratch.org> | 2002-02-11 12:12:38 +0000 |
|---|---|---|
| committer | Marc Heerdink <gimli@linuxfromscratch.org> | 2002-02-11 12:12:38 +0000 |
| commit | fe578632b8625be8010741894d4538d02812a8ae (patch) | |
| tree | b6f0204c8a0a86dea834a8f79276486625ed2097 /chapter05/whystatic.xml | |
| parent | 901193ca623c34da030ddbe470eb038f79254474 (diff) | |
Fixed some typo's
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1567 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05/whystatic.xml')
| -rw-r--r-- | chapter05/whystatic.xml | 27 |
1 files changed, 13 insertions, 14 deletions
diff --git a/chapter05/whystatic.xml b/chapter05/whystatic.xml index a0d611469..b784b5bfd 100644 --- a/chapter05/whystatic.xml +++ b/chapter05/whystatic.xml @@ -8,22 +8,21 @@ based to one of the LFS mailing lists.</para> <para>When making (compiling) a program, rather than having to rewrite all the functions for dealing with the kernel, hardware, files, etc. every time you write a new program, all these basic functions are instead kept in libraries. -glibc, which you install later, is one of these major libraries, which contain -code for all the basic functions programs use, like opening files, printing -information on the screen, and getting feedback from the user. When the -program is compiled, these libraries of code are linked together with the new -program, so that it can use any of the functions that the library +glibc, which you install later, is one of these major libraries, which +contains code for all the basic functions programs use, like opening files, +printing information on the screen, and getting feedback from the user. When +the program is compiled, these libraries of code are linked together with the +new program, so that it can use any of the functions that the library has.</para> -<para>However, these libraries can be very large (for example, libc.a -from can often be around 2.5MB), so you may not want a separate copy of -each library attached to the -program. Just imagine if you had a simple command like ls with an extra 2.5MB -attached to it! Instead of making the library an actual part of the -program, or Statically Linked, the library is kept a separate file, -which is loaded only when the program needs it. This is what we call Dynamically -Linked, as the library is loaded and unloaded dynamically, as the program needs -it.</para> +<para>However, these libraries can be very large (for example, libc.a from +can often be around 2.5MB), so you may not want a separate copy of each +library attached to the program. Just imagine if you had a simple command +like ls with an extra 2.5MB attached to it! Instead of making the library +an actual part of the program, or statically linked, the library is kept a +separate file, which is loaded only when the program needs it. This is what +we call dynamically linked, as the library is loaded and unloaded dynamically, +as the program needs it.</para> <para>So now we have a 1kb file and a 2.5MB file, but we still haven't saved any space (except maybe RAM until the library is needed). The REAL advantage to |