diff options
Diffstat (limited to 'chapter05/whystatic.xml')
| -rw-r--r-- | chapter05/whystatic.xml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/chapter05/whystatic.xml b/chapter05/whystatic.xml index e0fc14a6b..b383455b0 100644 --- a/chapter05/whystatic.xml +++ b/chapter05/whystatic.xml @@ -29,13 +29,13 @@ saved any space (except maybe RAM until the library is needed). The <emphasis>real</emphasis> advantage of dynamically linked libraries is that we only need one copy of the library. If <filename>ls</filename> and <filename>rm</filename> both use the same library, then we don't need two -copies of the library, as they can both get the code from the same file. +copies of the library, as they can both get the code from the same file. Even when in memory, the two programs share the same code, rather than loading duplicates into memory. So not only are we saving hard disk space, but also precious RAM.</para> <para>If dynamic linking saves so much room, then why are we making everything -statically linked? Well, that's because when you chroot into your brand new +statically linked? Well, that's because when you chroot into your brand new (but very incomplete) LFS environment, these dynamic libraries won't be available because they are somewhere else in your old directory tree (<filename>/usr/lib</filename> for example) which won't be accessible @@ -52,7 +52,7 @@ all the programs we just did in Chapter 5, but this time dynamically linked, so that we can take advantage of the space saving opportunities.</para> <para>And there you have it, that's why you need to use those weird -<userinput>-static</userinput> flags. If you try building everything +<userinput>-static</userinput> flags. If you try building everything without them, you'll see very quickly what happens when you chroot into your newly crippled LFS system.</para> |