Ignore:
Timestamp:
04/19/2002 06:27:01 PM (22 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, 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, 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/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
cdfd845
Parents:
747f5dda
Message:

various fixes

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter05/fileutils-inst.xml

    r747f5dda re69a59f  
    22<title>Installation of Fileutils</title>
    33
    4 <para>The programs from a statically linked fileutils package may cause
     4<para>The programs from a statically linked Fileutils package may cause
    55segmentation faults on certain systems, if your distribution has
    66Glibc-2.2.3 or higher installed. It also seems to happen mostly on machines
     
    2727&nbsp;&nbsp;&nbsp;lib/Makefile.in.backup &gt; lib/Makefile.in</userinput></screen></para>
    2828
    29 <para>Install fileutils by running the following commands:</para>
     29<para>Install Fileutils by running the following commands:</para>
    3030
    3131<para><screen><userinput>./configure --disable-nls \
     
    3636ln -sf ../../bin/install</userinput></screen></para>
    3737
    38 <para>Once you have installed fileutils, you can test whether the
     38<para>Once you have installed Fileutils, you can test whether the
    3939segmentation fault problem has been avoided by running
    4040<userinput>$LFS/bin/ls</userinput>. If this works, then you are OK. If
Note: See TracChangeset for help on using the changeset viewer.