Ignore:
Timestamp:
08/24/2001 04:11:04 PM (23 years ago)
Author:
Gerard Beekmans <gerard@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 12.2, 12.2-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v3_0, v3_1, v3_2, v3_3, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
8a985c27
Parents:
38e8642
Message:

Updated and clarified the text somewhat (hopefully)

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1017 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter05/fileutils-inst.xml

    r38e8642 rf66ac14  
    66segmentation faults once we enter chroot in Chapter 6.  The sed commands for
    77those using glibc-2.2.3 are:
     8
     9<para>The programs from a statically linked fileutils package may cause
     10segmentation faults on certain systems. These systems are often, but not
     11limited to, Linux systems that run Glibc-2.2.3 with an AMD CPU (Athlons
     12and Durons are the most reported used CPU's). If you are in this category,
     13run the following to sed commands before you compile this package.
    814
    915<screen><userinput>sed 's/\(.*\)\(fopen-safer\.c \)\\/\1\2atexit.c \\/' \</userinput>
     
    2228<para>Once you have installed fileutils, you can test whether the
    2329segmentation fault problem has been avoided by running
    24 <userinput>$LFS/bin/ls</userinput>.  If this works then you are OK, if
    25 not, then you need to re-do the installation using the seds if you
    26 didn't the first time or vice-versa.</para>
     30<userinput>$LFS/bin/ls</userinput>. If this works, then you are OK. If
     31not, then you need to re-do the installation using the sed commands if
     32you didn't use them, or without the sed commands if you did use
     33them.</para>
    2734
    2835</sect2>
Note: See TracChangeset for help on using the changeset viewer.