Changeset 939cf0da for general/genlib/genlib.xml
- Timestamp:
- 01/12/2005 07:40:39 PM (19 years ago)
- 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, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 5a7a0e5
- Parents:
- d992ab5
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/genlib/genlib.xml
rd992ab5 r939cf0da 14 14 duplicate code (and risk introducing bugs), it just has to call 15 15 functions from the libraries installed on the system. The most obvious 16 example of a set of libraries is <application> glibc</application> which is16 example of a set of libraries is <application>Glibc</application> which is 17 17 installed during the <acronym>LFS</acronym> book. This contains all of 18 18 the <application>C</application> library functions which programs use.</para> … … 27 27 <para>Generally, you only need to install libraries when you are 28 28 installing software that needs the functionality they supply. In 29 the <acronym>BLFS</acronym> book, each package is presented with a list of (known)30 dependencies. Thus, you can figure out which libraries you need to have 31 before installing that program. If you are installing something without 32 using <acronym>BLFS</acronym> instructions, usually the <filename>README</filename>33 or <filename>INSTALL</filename> file will contain details of the34 program's requirements.</para>29 the <acronym>BLFS</acronym> book, each package is presented with a list of 30 (known) dependencies. Thus, you can figure out which libraries you need to 31 have before installing that program. If you are installing something without 32 using <acronym>BLFS</acronym> instructions, usually the 33 <filename>README</filename> or <filename>INSTALL</filename> file will contain 34 details of the program's requirements.</para> 35 35 36 36 <para>There are certain libraries which nearly <emphasis>everyone</emphasis> … … 38 38 explain why you may want to install them.</para> 39 39 40 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="openssl.xml"/>41 40 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="pcre.xml"/> 42 41 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="popt.xml"/>
Note:
See TracChangeset
for help on using the changeset viewer.