- Timestamp:
- 09/29/2015 09:27:18 PM (9 years ago)
- Branches:
- 7.9-systemd
- Children:
- 6eb40d4
- Parents:
- 102c4bb6
- Location:
- chapter06
- Files:
-
- 10 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/adjusting.xml
r102c4bb6 rdbc347c5 43 43 as expected. To do this, perform the following sanity checks:</para> 44 44 45 <screen os="a"><userinput>echo ' main(){}' > dummy.c45 <screen os="a"><userinput>echo 'int main(){}' > dummy.c 46 46 cc dummy.c -v -Wl,--verbose &> dummy.log 47 47 readelf -l a.out | grep ': /lib'</userinput></screen> -
chapter06/diffutils.xml
r102c4bb6 rdbc347c5 57 57 58 58 <screen><userinput remap="test">make check</userinput></screen> 59 60 <para>The test-update-copyright.sh failure can be safely ignored.</para> 59 61 60 62 <para>Install the package:</para> -
chapter06/e2fsprogs.xml
r102c4bb6 rdbc347c5 45 45 <title>Installation of E2fsprogs</title> 46 46 47 <para>First, fix a potential security issue identified upstream:</para>47 <!-- <para>First, fix a potential security issue identified upstream:</para> 48 48 49 49 <screen><userinput remap="pre">sed -e '/int.*old_desc_blocks/s/int/blk64_t/' \ 50 50 -e '/if (old_desc_blocks/s/super->s_first_meta_bg/desc_blocks/' \ 51 -i lib/ext2fs/closefs.c</userinput></screen> 51 -i lib/ext2fs/closefs.c</userinput></screen> --> 52 52 53 53 <para>The E2fsprogs documentation recommends that the package be built in -
chapter06/glibc.xml
r102c4bb6 rdbc347c5 140 140 <listitem> 141 141 <para>The <emphasis>elf/tst-protected1a</emphasis> and 142 <emphasis>elf/tst-protected1 a</emphasis> tests are known to142 <emphasis>elf/tst-protected1b</emphasis> tests are known to 143 143 fail with the current stable version of binutils.</para> 144 144 </listitem> -
chapter06/grep.xml
r102c4bb6 rdbc347c5 57 57 <screen><userinput remap="test">make check</userinput></screen> 58 58 59 <para>The test-update-copyright.sh failure can be safely ignored.</para> 60 59 61 <para>Install the package:</para> 60 62 -
chapter06/introduction.xml
r102c4bb6 rdbc347c5 65 65 to remove a security problem, all programs that use the static library will 66 66 need to be relinked to the new library. Since the use of static libraries 67 is not always obvious, deciding whichprograms (and the procedures needed to67 is not always obvious, the relevant programs (and the procedures needed to 68 68 do the linking) may not even be known.</para> 69 69 70 <para>In the pr cedures in Chapter 6, we remove or disable installation of70 <para>In the procedures in Chapter 6, we remove or disable installation of 71 71 most static libraries. In a few cases, especially glibc and gcc, the use 72 72 of static libraries remains essential to the general package building -
chapter06/m4.xml
r102c4bb6 rdbc347c5 53 53 <screen><userinput remap="test">make check</userinput></screen> 54 54 55 <para>The test-update-copyright.sh failure can safely be ignored.</para> 56 55 57 <para>Install the package:</para> 56 58 -
chapter06/ncurses.xml
r102c4bb6 rdbc347c5 142 142 <para>The instructions above don't create non-wide-character Ncurses 143 143 libraries since no package installed by compiling from sources would 144 link against them at runtime. If you must have such libraries because 144 link against them at runtime. However, the only known binary-only 145 applications that link against non-wide-character Ncurses libraries 146 require version 5. If you must have such libraries because 145 147 of some binary-only application or to be compliant with LSB, build 146 148 the package again with the following commands:</para> … … 151 153 --without-normal \ 152 154 --without-debug \ 153 --without-cxx-binding 155 --without-cxx-binding \ 156 --with-abi-version=5 154 157 make sources libs 155 cp -av lib/lib*.so. 6* /usr/lib</userinput></screen>158 cp -av lib/lib*.so.5* /usr/lib</userinput></screen> 156 159 </note> 157 160 -
chapter06/pkgmgt.xml
r102c4bb6 rdbc347c5 251 251 <para>One of the advantages of an LFS system is that there are no files that 252 252 depend on the position of files on a disk system. Cloning an LFS build to 253 another computer with an architecture similar tothe base system is as253 another computer with the same architecture as the base system is as 254 254 simple as using <command>tar</command> on the LFS partition that contains 255 255 the root directory (about 250MB uncompressed for a base LFS build), copying … … 269 269 configuration.</para> 270 270 271 <note><para>There have been some reports of issues when copying between 272 similar but not identical architectures. For instance, the instruction set 273 for an Intel architecture is not identical with an AMD processor and later 274 versions of some processors may have instructions that are unavailable in 275 earlier versions.</para></note> 276 271 277 <para>Finally the new system has to be made bootable via <xref 272 278 linkend="ch-bootable-grub"/>.</para> -
chapter06/xz.xml
r102c4bb6 rdbc347c5 150 150 <term><command>lzegrep</command></term> 151 151 <listitem> 152 <para>Runs <command>egrep</command> on LZMA compressed files files</para>152 <para>Runs <command>egrep</command> on LZMA compressed files</para> 153 153 <indexterm zone="ch-system-xz lzegrep"> 154 154 <primary sortas="b-lzegrep">lzegrep</primary>
Note:
See TracChangeset
for help on using the changeset viewer.