Changeset 091d624d
- Timestamp:
- 11/17/2022 06:08:13 PM (23 months ago)
- Branches:
- 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 12.2, 12.2-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/update-glibc
- Children:
- 2760113
- Parents:
- ebecd08
- Location:
- chapter08
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/glibc.xml
rebecd08 r091d624d 44 44 <title>Installation of Glibc</title> 45 45 46 <para>First, fix an issue building Glibc with parallel jobs and make-4.446 <para>First, fix an issue building Glibc with parallel jobs and Make-4.4 47 47 or later:</para> 48 48 … … 83 83 <term><parameter>--disable-werror</parameter></term> 84 84 <listitem> 85 <para>This option disables the - Werror option passed to85 <para>This option disables the -werror option passed to 86 86 GCC. This is necessary for running the test suite.</para> 87 87 </listitem> … … 91 91 <term><parameter>--enable-kernel=&min-kernel;</parameter></term> 92 92 <listitem> 93 <para>This option tells the build system that this glibc may93 <para>This option tells the build system that this Glibc may 94 94 be used with kernels as old as &min-kernel;. This means generating 95 95 workarounds in case a system call introduced in a later version … … 218 218 <screen><userinput remap="install">make install</userinput></screen> 219 219 220 <para>Fix hardcoded path to the executable loader in220 <para>Fix a hardcoded path to the executable loader in the 221 221 <command>ldd</command> script:</para> 222 222 … … 236 236 237 237 <para>Next, install the locales that can make the system respond in a 238 different language. None of the locales are required, but if some of them239 are missing, the test suites of future packages wouldskip important240 test cases.</para>238 different language. None of these locales are required, but if some of them 239 are missing, the test suites of some packages will skip important 240 test cases.</para> 241 241 242 242 <para>Individual locales can be installed using the … … 291 291 character set.</para> 292 292 293 <para>Alternatively, install all locales listed in the293 <para>Alternatively, install all the locales listed in the 294 294 <filename>glibc-&glibc-version;/localedata/SUPPORTED</filename> file 295 295 (it includes every locale listed above and many more) at once with the … … 327 327 328 328 <sect3> 329 <title>Adding nsswitch.conf</title>329 <title>Adding Nsswitch.conf</title> 330 330 331 331 <para>The <filename>/etc/nsswitch.conf</filename> file needs to be created … … 357 357 358 358 <sect3> 359 <title>Adding time zone data</title>359 <title>Adding Time Zone Data</title> 360 360 361 361 <para>Install and set up the time zone data with the following:</para> -
chapter08/introduction.xml
rebecd08 r091d624d 23 23 <para>We do not recommend using optimizations. They can make 24 24 a program run slightly faster, but they may also cause compilation 25 difficulties and problems when running the program. If a package refuses to25 difficulties, and problems when running the program. If a package refuses to 26 26 compile when using optimization, try to compile it without optimization and 27 27 see if that fixes the problem. Even if the package does compile when using 28 28 optimization, there is the risk it may have been compiled incorrectly because 29 of the complex interactions between the code and build tools. Also note that29 of the complex interactions between the code and the build tools. Also note that 30 30 the <option>-march</option> and <option>-mtune</option> options using values 31 31 not specified in the book have not been tested. This may cause problems with 32 32 the toolchain packages (Binutils, GCC and Glibc). The small potential gains 33 achieved inusing compiler optimizations are often outweighed by the risks.33 achieved by using compiler optimizations are often outweighed by the risks. 34 34 First-time builders of LFS are encouraged to build without custom 35 optimizations. The subsequent system will still run very fastand be stable35 optimizations. The resulting system will still run very fast, and be stable 36 36 at the same time.</para> 37 37 … … 43 43 descriptions) that the package installs.</para> 44 44 45 <note><para>The SBU values and required disk space include stest suite data45 <note><para>The SBU values and required disk space include test suite data 46 46 for all applicable packages in <xref linkend="chapter-building-system"/>. SBU 47 47 values have been calculated using a single CPU core (-j1) for all … … 49 49 50 50 <sect2> 51 <title>About libraries</title>51 <title>About Libraries</title> 52 52 53 53 <para>In general, the LFS editors discourage building and installing static 54 libraries. The original purpose for most static libraries hasbeen made54 libraries. Most static libraries have been made 55 55 obsolete in a modern Linux system. In addition, linking a static library 56 56 into a program can be detrimental. If an update to the library is needed 57 to remove a security problem, all programs that usethe static library will58 need to be relinked tothe new library. Since the use of static libraries57 to remove a security problem, every program that uses the static library will 58 need to be relinked with the new library. Since the use of static libraries 59 59 is not always obvious, the relevant programs (and the procedures needed to 60 60 do the linking) may not even be known.</para> 61 61 62 <para> In the procedures in this chapter, weremove or disable installation of62 <para>The procedures in this chapter remove or disable installation of 63 63 most static libraries. Usually this is done by passing a 64 64 <option>--disable-static</option> option to <command>configure</command>. 65 65 In other cases, alternate means are needed. In a few cases, especially 66 glibc and gcc, the use of static libraries remains essential to the general66 Glibc and GCC, the use of static libraries remains an essential feature of the 67 67 package building process. </para> 68 68 69 <para>For a more complete discussion of libraries, see the discussion69 <para>For a more complete discussion of libraries, see 70 70 <ulink url="&blfs-book;introduction/libraries.html"> 71 71 Libraries: Static or shared?</ulink> in the BLFS book.</para> -
chapter08/pkgmgt.xml
rebecd08 r091d624d 13 13 <para>Package Management is an often requested addition to the LFS Book. A 14 14 Package Manager tracks the installation of files, making it easier to 15 remove and upgrade packages. A s well as the binary and library files, a16 package manager will handle the installation of configurationfiles. Before15 remove and upgrade packages. A good package manager will handle the 16 installation of configuration files, and also install the executable files. Before 17 17 you begin to wonder, NO—this section will not talk about nor recommend 18 any particular package manager. What it providesis a roundup of the more18 any particular package manager. What it does provide is a roundup of the more 19 19 popular techniques and how they work. The perfect package manager for you may 20 20 be among these techniques, or it may be a combination of two or more of these … … 62 62 63 63 <listitem> 64 <para>If Linux API headers or glibc need to be upgraded to a newer65 version, (e.g., from glibc-2.31 to glibc-2.32), it is safer to64 <para>If the Linux API headers or Glibc need to be upgraded to a newer 65 version, (e.g., from Glibc-2.31 to Glibc-2.32), it is safer to 66 66 rebuild LFS. Though you <emphasis>may</emphasis> be able to rebuild 67 67 all the packages in their dependency order, we do not recommend … … 203 203 reality it is installed in the 204 204 <filename class="directory">/usr/pkg</filename> hierarchy. Installing in 205 this manner is not usually a trivial task. For example, consider thatyou205 this manner is not usually a trivial task. For example, suppose you 206 206 are installing a package libfoo-1.1. The following instructions may 207 207 not install the package properly:</para> … … 322 322 another computer with the same architecture as the base system is as 323 323 simple as using <command>tar</command> on the LFS partition that contains 324 the root directory (about 250MB uncompressed for a base LFS build), copying 324 the root directory (about 900MB uncompressed for a basic LFS build), copying 325 <!-- D. Bryant created LFS 11.2 in October 2022; 900MB is (roughly) the size of his rsync archive. --> 325 326 that file via network transfer or CD-ROM / USB stick to the new system, and expanding 326 327 it. After that, a few configuration files will have to be changed.
Note:
See TracChangeset
for help on using the changeset viewer.