Changeset e1d7dec for general/genlib/genlib.xml

Timestamp:

09/14/2003 08:28:20 PM (21 years ago)

Author:

Larry Lawrence <larry@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.0, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, v5_0, v5_0-pre1, v5_1, v5_1-pre1, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

461626e

Parents:

b3ae387

Message:

update libungif intro

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@1073 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• general/genlib/genlib.xml (modified) (1 diff)

general/genlib/genlib.xml

@@ -7 +7 @@
 duplicate code (and risk introducing bugs), it just has to call
 functions from the libraries installed on the system.  The most obvious
-example of a set of libraries is glibc which is installed during the LFS
-book.  This contains all of the C library functions which programs
-use.</para>
+example of a set of libraries is <application>glibc</application> which is 
+installed during the <acronym>LFS</acronym> book.  This contains all of
+the <application>C</application> library functions which programs use.</para>
 
-<para>There are two types of library, static and shared.  Shared
-libraries (usually <filename>libXXX.so</filename>) are loaded into memory from the shared
-copy at runtime (hence the name).  Static libraries
-(<filename>libXXX.a</filename>) are
-actually linked into the program executable file itself, thus making the
-program file larger.  Quite often, you will find both static and shared
-copies of the same library on your system.</para>
+<para>There are two types of library, static and shared.  Shared libraries 
+(usually <filename>libXXX.so</filename>) are loaded into memory from the shared
+copy at runtime (hence the name).  Static libraries (<filename>libXXX.a
+</filename>) are actually linked into the program executable file itself, thus 
+making the program file larger.  Quite often, you will find both static and 
+shared copies of the same library on your system.</para>
 
 <para>Generally, you only need to install libraries when you are
 installing software which requires functionality which they supply.  In
-the BLFS book, each package is listed with a list of (known)
+the <acronym>BLFS</acronym> book, each package is listed with a list of (known)
 dependencies.  Thus, you can figure out which libraries you need to have
 before installing that program.  If you are installing something without
-using BLFS instructions, usually the <filename>README</filename>  or
-<filename>INSTALL</filename> file will contain details of the programs
-requirements.</para>
+using <acronym>BLFS</acronym> instructions, usually the <filename>README
+</filename>  or <filename>INSTALL</filename> file will contain details of the 
+programs requirements.</para>
 
-<para>There are certain libraries which nearly
-<emphasis>everyone</emphasis> will need at some point.  In this chapter
-we list these and some others and explain why you may want to install
-them.</para>
+<para>There are certain libraries which nearly <emphasis>everyone</emphasis> 
+will need at some point.  In this chapter we list these and some others and 
+explain why you may want to install them.</para>
 
 &openssl;