Changeset 11d5dee


Ignore:
Timestamp:
07/27/2021 07:11:38 PM (11 months ago)
Author:
Bruce Dubbs <bdubbs@…>
Branches:
11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, arm, ml-11.0, multilib, trunk, xry111/clfs-ng, xry111/glibc-2.34, xry111/lfs-next
Children:
29779c4
Parents:
d1592b9
Message:

Minor instruction changes and text updates.
Move coreutils library from /usr/libexec to /usr/lib in both
Chapter 6 and Chapter 8.

Text updates in chapter08/pkgmgt.xml and chapter09/locale.xml.

Restore deletion of hanging test in chapter08/util-linux.xml.

Text changes in stripping and make instruction compatible with jhalfs.

Files:
6 edited

Legend:

Unmodified
Added
Removed
  • chapter06/coreutils.xml

    rd1592b9 r11d5dee  
    4747
    4848<screen><userinput remap="configure">./configure --prefix=/usr                     \
     49            --libexecdir=/usr/lib             \
    4950            --host=$LFS_TGT                   \
    5051            --build=$(build-aux/config.guess) \
  • chapter08/coreutils.xml

    rd1592b9 r11d5dee  
    7070FORCE_UNSAFE_CONFIGURE=1 ./configure \
    7171            --prefix=/usr            \
     72            --libexecdir=/usr/lib    \
    7273            --enable-no-install-program=kill,uptime</userinput></screen>
    7374
  • chapter08/pkgmgt.xml

    rd1592b9 r11d5dee  
    7070
    7171      <listitem> <para>If a package containing a shared library is updated, and
    72       if the name of the library changes, then any the packages dynamically
     72      if the name of the library changes, then any packages dynamically
    7373      linked to the library need to be recompiled in order to link against the
    7474      newer library.  (Note that there is no correlation between the package
     
    124124
    125125      <listitem>
    126         <para>If a binary or a shared library is overwrote, the processes
     126        <para>If a binary or a shared library is overwritten, the processes
    127127        using the code or data in the binary or library may crash.  The
    128128        correct way to update a binary or a shared library without causing
    129         the process to crash is: remove it first, then install the new
     129        the process to crash is to remove it first, then install the new
    130130        version into position. The <command>install</command> command
    131131        provided by <application>Coreutils</application> has already
    132132        implemented this and most packages use it to install binaries and
    133         libraries.  So you won't be troubled by this issue most of the time.
     133        libraries.  This means that you won't be troubled by this issue most of the time.
    134134        However, the install process of some packages (notably Mozilla JS
    135         in BLFS) just overwrites the file if it exists and causes crash, so
     135        in BLFS) just overwrites the file if it exists and causes a crash, so
    136136        it's safer to save your work and close unneeded running processes
    137137        before updating a package.</para>
  • chapter08/strippingagain.xml

    rd1592b9 r11d5dee  
    2525
    2626  <para>The debugging symbols for selected libraries are placed
    27   in separate files.  These debugging information is needed if running
     27  in separate files.  This debugging information is needed if running
    2828  regression tests that use <ulink
    2929  url='&blfs-book;/general/valgrind.html'>valgrind</ulink> or <ulink
     
    3131  </para>
    3232
    33   <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
     33  <para>Note that <command>strip</command> will overwrite the binary or library
     34  file it is processing.  This may crash the processes using code or data from
     35  the file.  If the process running <command>strip</command> itself is
     36  affected, the binary or library being stripped may be destroyed.  This may
     37  make the system completely unusable.  To avoid it, we'll copy some libraries
     38  and binaries into <filename class="directory">/tmp</filename>, strip them
    3939  there, and install them back with the <command>install</command> command.
    4040  Read the related entry in <xref linkend="pkgmgmt-upgrade-issues"/> for the
     
    8585for i in $(find /usr/lib -type f -name \*.so* ! -name \*dbg); do
    8686    case "$online_usrlib $save_usrlib" in
    87         *$(basename $i)* ) ;;
    88         * ) strip --strip-unneeded $i ;;
     87        *$(basename $i)* )
     88            ;;
     89        * ) strip --strip-unneeded $i
     90            ;;
    8991    esac
    9092done
     
    9294for i in $(find /usr/bin -type f); do
    9395    case "$online_usrbin" in
    94         *$(basename $i)* ) ;;
    95         * ) strip --strip-all $i ;;
     96        *$(basename $i)* )
     97            ;;
     98        * ) strip --strip-all $i
     99            ;;
    96100    esac
    97101done
  • chapter08/util-linux.xml

    rd1592b9 r11d5dee  
    9595<screen role="nodump"><userinput>bash tests/run.sh --srcdir=$PWD --builddir=$PWD</userinput></screen>
    9696    </warning>
    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>
     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>
    101102
    102103    <screen><userinput remap="test">rm tests/ts/lsns/ioctl_ns</userinput></screen>
    103104    </note>
    104 -->
     105
    105106<screen><userinput remap="test">chown -Rv tester .
    106107su tester -c "make -k check"</userinput></screen>
  • chapter09/locale.xml

    rd1592b9 r11d5dee  
    8181  before the telephone number in order to get into the country. If any of the
    8282  commands above fail with a message similar to the one shown below, this means
    83   that your locale was either not installed in Chapter&nbsp;6 or is not
     83  that your locale was either not installed in Chapter&nbsp;8 or is not
    8484  supported by the default installation of Glibc.</para>
    8585
Note: See TracChangeset for help on using the changeset viewer.