Changes in / [64a306d:85cd74c2]
- Files:
-
- 8 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/changelog.xml
r64a306d r85cd74c2 47 47 48 48 <listitem> 49 <para>2021-07-27</para>50 <itemizedlist>51 <listitem>52 <para>[xry111] - Use workaround for Glibc NSS modules during53 stripping, to prevent bash from crash.</para>54 </listitem>55 </itemizedlist>56 </listitem>57 58 <listitem>59 49 <para>2021-07-26</para> 60 50 <itemizedlist> -
chapter06/coreutils.xml
r64a306d r85cd74c2 47 47 48 48 <screen><userinput remap="configure">./configure --prefix=/usr \ 49 --libexecdir=/usr/lib \50 49 --host=$LFS_TGT \ 51 50 --build=$(build-aux/config.guess) \ -
chapter08/coreutils.xml
r64a306d r85cd74c2 70 70 FORCE_UNSAFE_CONFIGURE=1 ./configure \ 71 71 --prefix=/usr \ 72 --libexecdir=/usr/lib \73 72 --enable-no-install-program=kill,uptime</userinput></screen> 74 73 -
chapter08/pkgmgt.xml
r64a306d r85cd74c2 70 70 71 71 <listitem> <para>If a package containing a shared library is updated, and 72 if the name of the library changes, then any packages dynamically72 if the name of the library changes, then any the packages dynamically 73 73 linked to the library need to be recompiled in order to link against the 74 74 newer library. (Note that there is no correlation between the package … … 124 124 125 125 <listitem> 126 <para>If a binary or a shared library is overwr itten, the processes126 <para>If a binary or a shared library is overwrote, the processes 127 127 using the code or data in the binary or library may crash. The 128 128 correct way to update a binary or a shared library without causing 129 the process to crash is toremove it first, then install the new129 the process to crash is: remove it first, then install the new 130 130 version into position. The <command>install</command> command 131 131 provided by <application>Coreutils</application> has already 132 132 implemented this and most packages use it to install binaries and 133 libraries. This means thatyou won't be troubled by this issue most of the time.133 libraries. So you won't be troubled by this issue most of the time. 134 134 However, the install process of some packages (notably Mozilla JS 135 in BLFS) just overwrites the file if it exists and causes acrash, so135 in BLFS) just overwrites the file if it exists and causes crash, so 136 136 it's safer to save your work and close unneeded running processes 137 137 before updating a package.</para> -
chapter08/shadow.xml
r64a306d r85cd74c2 98 98 <para>Fix a simple programming error by modifying a file with following command:</para> 99 99 100 <screen><userinput remap="pre">sed -e "224s/rounds /min_rounds/" -i libmisc/salt.c</userinput></screen>100 <screen><userinput remap="pre">sed -e "224s/rounds = SHA_ROUNDS_DEFAULT/min_&/" -i libmisc/salt.c</userinput></screen> 101 101 102 102 <para>Prepare Shadow for compilation:</para> -
chapter08/strippingagain.xml
r64a306d r85cd74c2 25 25 26 26 <para>The debugging symbols for selected libraries are placed 27 in separate files. Th isdebugging information is needed if running27 in separate files. These debugging information is needed if running 28 28 regression tests that use <ulink 29 29 url='&blfs-book;/general/valgrind.html'>valgrind</ulink> or <ulink … … 31 31 </para> 32 32 33 <para> Note that<command>strip</command> will overwrite the binary or library34 file it is processing. This may crash the processes using code or data from35 the file. If the process running <command>strip</command> itself is36 affected, the binary or library being stripped may be destroyed. This may37 make the system completely unusable. To avoid it, we'll copy some libraries38 andbinaries into <filename class="directory">/tmp</filename>, strip them33 <para>And, <command>strip</command> will overwrite the binary or library 34 file. This may crash the processes using code or data from the file. If 35 the process running <command>strip</command> itself is affected, the 36 binary or library being stripped may be destroyed. This may make the 37 system completely unusable. To avoid it, we'll copy some libraries and 38 binaries into <filename class="directory">/tmp</filename>, strip them 39 39 there, and install them back with the <command>install</command> command. 40 40 Read the related entry in <xref linkend="pkgmgmt-upgrade-issues"/> for the … … 82 82 libhistory.so.&readline-version; libncursesw.so.&ncurses-version; 83 83 libm-&glibc-version;.so libreadline.so.&readline-version; 84 libz.so.&zlib-version; 85 $(cd /usr/lib; find libnss*.so* -type f)" 84 libz.so.&zlib-version;" 86 85 87 86 for BIN in $online_usrbin; do … … 116 115 for i in $(find /usr/lib -type f -name \*.so* ! -name \*dbg); do 117 116 case "$online_usrlib $save_usrlib" in 118 *$(basename $i)* ) 119 ;; 120 * ) strip --strip-unneeded $i 121 ;; 117 *$(basename $i)* ) ;; 118 * ) strip --strip-unneeded $i ;; 122 119 esac 123 120 done</userinput><userinput arch="ml_32,ml_all"> … … 137 134 for i in $(find /usr/bin -type f); do 138 135 case "$online_usrbin" in 139 *$(basename $i)* ) 140 ;; 141 * ) strip --strip-all $i 142 ;; 136 *$(basename $i)* ) ;; 137 * ) strip --strip-all $i ;; 143 138 esac 144 139 done -
chapter08/util-linux.xml
r64a306d r85cd74c2 95 95 <screen role="nodump"><userinput>bash tests/run.sh --srcdir=$PWD --builddir=$PWD</userinput></screen> 96 96 </warning> 97 98 <note><para>There is one test that fails in the chroot envronment and 99 causes the tests to hang forever. The problem does not occur outside 100 of the chroot envronment. 101 To work around the problem, delete the test:</para> 97 <!-- 98 <note><para>There is one test that depends on the configuration of the kernel. 99 If CONFIG_USER_NS or CONFIG_PID_NS are not set, the tests will hang forever. 100 To work around the problem, delete one test:</para> 102 101 103 102 <screen><userinput remap="test">rm tests/ts/lsns/ioctl_ns</userinput></screen> 104 103 </note> 105 104 --> 106 105 <screen><userinput remap="test">chown -Rv tester . 107 106 su tester -c "make -k check"</userinput></screen> -
chapter09/locale.xml
r64a306d r85cd74c2 81 81 before the telephone number in order to get into the country. If any of the 82 82 commands above fail with a message similar to the one shown below, this means 83 that your locale was either not installed in Chapter 8or is not83 that your locale was either not installed in Chapter 6 or is not 84 84 supported by the default installation of Glibc.</para> 85 85
Note:
See TracChangeset
for help on using the changeset viewer.