Changes in / [16a1647:8d5322e]
- Files:
-
- 5 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/chroot.xml
r16a1647 r8d5322e 39 39 <para>From this point on, there is no need to use the 40 40 <envar>LFS</envar> variable any more because all work will be restricted 41 to the LFS file system; the <command>chroot</command> command tells the Bash shell that 42 <filename class="directory">$LFS</filename> is now the root 43 (<filename class="directory">/</filename>) directory.</para> 41 to the LFS file system; the <command>chroot</command> command runs the 42 Bash shell with the root 43 (<filename class="directory">/</filename>) directory set to 44 <filename class='directory'>$LFS</filename>.</para> 44 45 45 46 <para>Notice that <filename class="directory">/tools/bin</filename> is not -
chapter07/kernfs.xml
r16a1647 r8d5322e 42 42 If the host kernel supports &devtmpfs;, we can simply mount a 43 43 &devtmpfs; at <filename class='directory'>$LFS/dev</filename> and rely 44 on the kernel to populate it (i.e., the udev daemon will do the 45 necessary work automatically).</para> 44 on the kernel to populate it.</para> 46 45 47 46 <para>But some host kernels lack &devtmpfs; support; these … … 52 51 by bind mounting the host system's 53 52 <filename class="directory">/dev</filename> directory. A bind mount is 54 a special type of mount that generates a duplicate copy of a55 directory or mount pointat some other location. Use the following53 a special type of mount that makes a directory subtree or a file 54 visible at some other location. Use the following 56 55 command to do this.</para> 57 56 -
chapter08/glibc.xml
r16a1647 r8d5322e 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 … … 98 98 <term><parameter>--enable-kernel=&min-kernel;</parameter></term> 99 99 <listitem> 100 <para>This option tells the build system that this glibc may100 <para>This option tells the build system that this Glibc may 101 101 be used with kernels as old as &min-kernel;. This means generating 102 102 workarounds in case a system call introduced in a later version … … 225 225 <screen><userinput remap="install">make install</userinput></screen> 226 226 227 <para>Fix hardcoded path to the executable loader in227 <para>Fix a hardcoded path to the executable loader in the 228 228 <command>ldd</command> script:</para> 229 229 … … 243 243 244 244 <para>Next, install the locales that can make the system respond in a 245 different language. None of the locales are required, but if some of them246 are missing, the test suites of future packages wouldskip important247 test cases.</para>245 different language. None of these locales are required, but if some of them 246 are missing, the test suites of some packages will skip important 247 test cases.</para> 248 248 249 249 <para>Individual locales can be installed using the … … 298 298 character set.</para> 299 299 300 <para>Alternatively, install all locales listed in the300 <para>Alternatively, install all the locales listed in the 301 301 <filename>glibc-&glibc-version;/localedata/SUPPORTED</filename> file 302 302 (it includes every locale listed above and many more) at once with the … … 364 364 365 365 <sect3> 366 <title>Adding time zone data</title>366 <title>Adding Time Zone Data</title> 367 367 368 368 <para>Install and set up the time zone data with the following:</para> -
chapter08/introduction.xml
r16a1647 r8d5322e 21 21 may need it.</para> 22 22 23 <para>We do not recommend using optimizations. They can make23 <para>We do not recommend using customized 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 to26 compile w hen using optimization, try to compile it without optimization and27 see if that fixes the problem. Even if the package does compile when using25 difficulties, and problems when running the program. If a package refuses to 26 compile with a customized optimization, try to compile it without 27 optimization and see if that fixes the problem. Even if the package does compile when using a customized 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 in using compiler optimizations are often outweighed by the risks.33 achieved by customizing 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 fast and be stable 36 at the same time.</para> 35 optimizations.</para> 36 37 <para>On the other hand, we keep the optimizations enabled by the default 38 configuration of the packages. In addition, we sometimes explicitly enable an 39 optimized configuration provided by a package but not enabled by 40 default. The package maintainers have already tested these configurations 41 and consider them safe, so it's not likely they would break the build. 42 Generally the default configuration already enables <option>-O2</option> 43 or <option>-O3</option>, so the resulting system will still run very fast 44 without any customized optimization, and be stable at the same time.</para> 37 45 38 46 <para>Before the installation instructions, each installation page provides … … 43 51 descriptions) that the package installs.</para> 44 52 45 <note><para>The SBU values and required disk space include stest suite data53 <note><para>The SBU values and required disk space include test suite data 46 54 for all applicable packages in <xref linkend="chapter-building-system"/>. SBU 47 55 values have been calculated using a single CPU core (-j1) for all … … 49 57 50 58 <sect2> 51 <title>About libraries</title>59 <title>About Libraries</title> 52 60 53 61 <para>In general, the LFS editors discourage building and installing static 54 libraries. The original purpose for most static libraries hasbeen made62 libraries. Most static libraries have been made 55 63 obsolete in a modern Linux system. In addition, linking a static library 56 64 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 libraries65 to remove a security problem, every program that uses the static library will 66 need to be relinked with the new library. Since the use of static libraries 59 67 is not always obvious, the relevant programs (and the procedures needed to 60 68 do the linking) may not even be known.</para> 61 69 62 <para> In the procedures in this chapter, weremove or disable installation of70 <para>The procedures in this chapter remove or disable installation of 63 71 most static libraries. Usually this is done by passing a 64 72 <option>--disable-static</option> option to <command>configure</command>. 65 73 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 general74 Glibc and GCC, the use of static libraries remains an essential feature of the 67 75 package building process. </para> 68 76 69 <para>For a more complete discussion of libraries, see the discussion77 <para>For a more complete discussion of libraries, see 70 78 <ulink url="&blfs-book;introduction/libraries.html"> 71 79 Libraries: Static or shared?</ulink> in the BLFS book.</para> -
chapter08/pkgmgt.xml
r16a1647 r8d5322e 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. As well as the binary and library files, a 16 package manager will handle the installation of configuration files. Before 15 remove and upgrade packages. A good package manager will also handle the 16 configuration files specially to keep the user configuration when the 17 package is reinstalled or upgraded. Before 17 18 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 more19 any particular package manager. What it does provide is a roundup of the more 19 20 popular techniques and how they work. The perfect package manager for you may 20 21 be among these techniques, or it may be a combination of two or more of these … … 62 63 63 64 <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 to65 <para>If the Linux API headers or Glibc need to be upgraded to a newer 66 version, (e.g., from Glibc-2.31 to Glibc-2.32), it is safer to 66 67 rebuild LFS. Though you <emphasis>may</emphasis> be able to rebuild 67 68 all the packages in their dependency order, we do not recommend … … 203 204 reality it is installed in the 204 205 <filename class="directory">/usr/pkg</filename> hierarchy. Installing in 205 this manner is not usually a trivial task. For example, consider thatyou206 this manner is not usually a trivial task. For example, suppose you 206 207 are installing a package libfoo-1.1. The following instructions may 207 208 not install the package properly:</para> … … 322 323 another computer with the same architecture as the base system is as 323 324 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 325 the root directory (about 900MB uncompressed for a basic LFS build), copying 326 <!-- D. Bryant created LFS 11.2 in October 2022; 900MB is (roughly) the size of his rsync archive. --> 325 327 that file via network transfer or CD-ROM / USB stick to the new system, and expanding 326 328 it. After that, a few configuration files will have to be changed.
Note:
See TracChangeset
for help on using the changeset viewer.