gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-18 19:29:21 +01:00
Code Issues Packages Projects Releases Wiki Activity

Updated and clarified the text somewhat (hopefully)

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1017 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Gerard Beekmans 2001-08-24 16:11:04 +00:00
parent 38e86420aa
commit f66ac148d7
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
chapter05/fileutils-inst.xml
View File

@ -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 segmentation faults once we enter chroot in Chapter 6. The sed commands for
those using glibc-2.2.3 are: 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> <screen><userinput>sed 's/\(.*\)\(fopen-safer\.c \)\\/\1\2atexit.c \\/' \</userinput>
<userinput>&nbsp;&nbsp;&nbsp;lib/Makefile.in &gt; tmp &amp;&amp;</userinput> <userinput>&nbsp;&nbsp;&nbsp;lib/Makefile.in &gt; tmp &amp;&amp;</userinput>
<userinput>sed 's/\(.*\)\(idcache\$U\.\$.*\)\\/\1\2atexit$U.$(OBJEXT) \\/' \</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 <para>Once you have installed fileutils, you can test whether the
segmentation fault problem has been avoided by running segmentation fault problem has been avoided by running
<userinput>$LFS/bin/ls</userinput>. If this works then you are OK, if <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 not, then you need to re-do the installation using the sed commands if
didn't the first time or vice-versa.</para> you didn't use them, or without the sed commands if you did use
them.</para>
</sect2> </sect2>