diff options
| author | Gerard Beekmans <gerard@linuxfromscratch.org> | 2002-04-19 18:27:01 +0000 |
|---|---|---|
| committer | Gerard Beekmans <gerard@linuxfromscratch.org> | 2002-04-19 18:27:01 +0000 |
| commit | e69a59f2e44d780a6ca26e71b96ab86e58b0fe58 (patch) | |
| tree | dcb4085cb3e4a2cf232de00b2e95a7a6f639a3c3 /chapter05/fileutils-inst.xml | |
| parent | 747f5dda8e125740a8f732e784903f017a84f80b (diff) | |
various fixes
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1840 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05/fileutils-inst.xml')
| -rw-r--r-- | chapter05/fileutils-inst.xml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/chapter05/fileutils-inst.xml b/chapter05/fileutils-inst.xml index 9bd395ac6..6d630b2c7 100644 --- a/chapter05/fileutils-inst.xml +++ b/chapter05/fileutils-inst.xml @@ -1,7 +1,7 @@ <sect2> <title>Installation of Fileutils</title> -<para>The programs from a statically linked fileutils package may cause +<para>The programs from a statically linked Fileutils package may cause segmentation faults on certain systems, if your distribution has Glibc-2.2.3 or higher installed. It also seems to happen mostly on machines powered by an AMD CPU, but there is a case or two where an Intel system @@ -26,7 +26,7 @@ sed -e 's/\(.*\)\(fopen-safer\.c \)\\/\1\2atexit.c \\/' \ -e 's/\(.*\)\(idcache\$U\.\$.*\)\\/\1\2atexit$U.$(OBJEXT) \\/' \ lib/Makefile.in.backup > lib/Makefile.in</userinput></screen></para> -<para>Install fileutils by running the following commands:</para> +<para>Install Fileutils by running the following commands:</para> <para><screen><userinput>./configure --disable-nls \ --prefix=$LFS/usr --bindir=$LFS/bin && @@ -35,7 +35,7 @@ make install && cd $LFS/usr/bin && ln -sf ../../bin/install</userinput></screen></para> -<para>Once you have installed fileutils, you can test whether the +<para>Once you have installed Fileutils, you can test whether the segmentation fault problem has been avoided by running <userinput>$LFS/bin/ls</userinput>. If this works, then you are OK. If not, then you need to re-do the installation using the sed commands if |