From f66ac148d73e505d409b0ba0b6363ac7cebf4028 Mon Sep 17 00:00:00 2001 From: Gerard Beekmans Date: Fri, 24 Aug 2001 16:11:04 +0000 Subject: Updated and clarified the text somewhat (hopefully) git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1017 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter05/fileutils-inst.xml | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) (limited to 'chapter05/fileutils-inst.xml') diff --git a/chapter05/fileutils-inst.xml b/chapter05/fileutils-inst.xml index bd8a39378..cc6de3d64 100644 --- a/chapter05/fileutils-inst.xml +++ b/chapter05/fileutils-inst.xml @@ -6,6 +6,12 @@ glibc-2.2.3 you need to apply two seds in order to prevent them giving segmentation faults once we enter chroot in Chapter 6. The sed commands for those using glibc-2.2.3 are: +The programs from a statically linked fileutils package may cause +segmentation faults on certain systems. These systems are often, but not +limited to, Linux systems that run Glibc-2.2.3 with an AMD CPU (Athlons +and Durons are the most reported used CPU's). If you are in this category, +run the following to sed commands before you compile this package. + sed 's/\(.*\)\(fopen-safer\.c \)\\/\1\2atexit.c \\/' \    lib/Makefile.in > tmp && sed 's/\(.*\)\(idcache\$U\.\$.*\)\\/\1\2atexit$U.$(OBJEXT) \\/' \ @@ -21,9 +27,10 @@ those using glibc-2.2.3 are: Once you have installed fileutils, you can test whether the segmentation fault problem has been avoided by running -$LFS/bin/ls. If this works then you are OK, if -not, then you need to re-do the installation using the seds if you -didn't the first time or vice-versa. +$LFS/bin/ls. If this works, then you are OK. If +not, then you need to re-do the installation using the sed commands if +you didn't use them, or without the sed commands if you did use +them. -- cgit v1.2.3-54-g00ecf