diff options
| author | Gerard Beekmans <gerard@linuxfromscratch.org> | 2001-08-24 16:11:04 +0000 |
|---|---|---|
| committer | Gerard Beekmans <gerard@linuxfromscratch.org> | 2001-08-24 16:11:04 +0000 |
| commit | f66ac148d73e505d409b0ba0b6363ac7cebf4028 (patch) | |
| tree | 324529743d4e908600014116bd47a69255f2e0e4 /chapter05 | |
| parent | 38e86420aa5a07123a438ac2f503950797e21044 (diff) | |
Updated and clarified the text somewhat (hopefully)
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1017 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05')
| -rw-r--r-- | chapter05/fileutils-inst.xml | 13 |
1 files changed, 10 insertions, 3 deletions
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: +<para>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. + <screen><userinput>sed 's/\(.*\)\(fopen-safer\.c \)\\/\1\2atexit.c \\/' \</userinput> <userinput> lib/Makefile.in > tmp &&</userinput> <userinput>sed 's/\(.*\)\(idcache\$U\.\$.*\)\\/\1\2atexit$U.$(OBJEXT) \\/' \</userinput> @@ -21,9 +27,10 @@ those using glibc-2.2.3 are: <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 seds if you -didn't the first time or vice-versa.</para> +<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 +you didn't use them, or without the sed commands if you did use +them.</para> </sect2> |