Changeset 76c0b78 for chapter05


Ignore:
Timestamp:
02/05/2002 12:44:06 AM (22 years ago)
Author:
Mark Hymers <markh@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v3_2, v3_3, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
bdc08c1
Parents:
2d416d6
Message:

spelling / phrasing fixes

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1547 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter05/whystatic.xml

    r2d416d6 r76c0b78  
    77
    88<para>When making (compiling) a program, rather than having to rewrite all the
    9 functions for dealing with the kernel, hardware, files, etc. everytime you
     9functions for dealing with the kernel, hardware, files, etc. every time you
    1010write a new program, all these basic functions are instead kept in libraries.
    1111glibc, which you install later, is one of these major libraries, which contain
     
    1717
    1818<para>However, these libraries can be very large (for example, libc.a
    19 from can often be around 2.5MB), so you may not want a seperate copy of
     19from can often be around 2.5MB), so you may not want a separate copy of
    2020each library attached to the
    2121program. Just imagine if you had a simple command like ls with an extra 2.5MB
    2222attached to it! Instead of making the library an actual part of the
    23 program, or Statically Linked, the library is kept a seperate file,
     23program, or Statically Linked, the library is kept a separate file,
    2424which is loaded only when the program needs it. This is what we call Dynamically
    2525Linked, as the library is loaded and unloaded dynamically, as the program needs
     
    5151main set of system libraries, glibc. Once this is made we start rebuilding
    5252all the programs we just did in Chapter 5, but this time dynamically linked,
    53 so that we can take advantage of the space saving opportunites.</para>
     53so that we can take advantage of the space saving opportunities.</para>
    5454
    5555<para>And there you have it, that's why you need to use those weird
Note: See TracChangeset for help on using the changeset viewer.