gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-07-12 07:14:11 +01:00
Code Issues Packages Projects Releases Wiki Activity

reworded the glibc-2.2.3 fix. it had better be clear now

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1198 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Gerard Beekmans 2001-09-07 20:51:36 +00:00
parent ebedcc2a2e
commit 70cdda10ac
1 changed files with 17 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
chapter05/fileutils-inst.xml
View File

@ -2,18 +2,26 @@
<title>Installation of Fileutils</title> <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. These systems are often, but not segmentation faults on certain systems, if your distribution has
limited to, Linux systems that run Glibc-2.2.3 with an AMD CPU (Athlons Glibc-2.2.3 or higher installed. It also seems to happen mostly on machines
and Durons are the most reported used CPU's). If you are in this category, powered by an AMD CPU, but there is a case or two where an Intel system
run the following to sed commands before you compile this is affected as well. If your system falls under this category, try the
package.</para> following fix.</para>
<para>Note that in some cases using these sed commands will result in <para>Note that in some cases using these sed commands will result in
problems not being able to compile this at package at all. If that's the problems not being able to compile this at package at all, even when your
case, you'll need to remove the fileutils-&fileutils-version; directory system has and AMD CPU and has Glibc-2.2.3 (or higher) installed. If that's
and unpack it again from the tarball before continuing. the case, you'll need to remove the fileutils-&fileutils-version; directory
and unpack it again from the tarball before continuing. We believe this
may be the case when your distribution has altered Glibc-2.2.3 somehow,
but details are unavailable at the time.</para>
<screen><userinput>cp lib/Makefile.in lib/Makefile.in.backup &amp;&amp;</userinput> <para>To fix this package to compile properly on AMD/Glibc-2.2.3
machines, run the following commands. do <emphasis>not</emphasis>
attempt this fix your don't have Glibc-2.2.3 installed. It will more
than likely result in all kinds of compile time problems.</para>
<para><screen><userinput>cp lib/Makefile.in lib/Makefile.in.backup &amp;&amp;</userinput>
<userinput>sed -e 's/\(.*\)\(fopen-safer\.c \)\\/\1\2atexit.c \\/' \</userinput> <userinput>sed -e 's/\(.*\)\(fopen-safer\.c \)\\/\1\2atexit.c \\/' \</userinput>
<userinput>&nbsp;&nbsp;&nbsp;-e 's/\(.*\)\(idcache\$U\.\$.*\)\\/\1\2atexit$U.$(OBJEXT) \\/' \</userinput> <userinput>&nbsp;&nbsp;&nbsp;-e 's/\(.*\)\(idcache\$U\.\$.*\)\\/\1\2atexit$U.$(OBJEXT) \\/' \</userinput>
<userinput>&nbsp;&nbsp;&nbsp;lib/Makefile.in &gt; lib/Makefile.in~ &amp;&amp;</userinput> <userinput>&nbsp;&nbsp;&nbsp;lib/Makefile.in &gt; lib/Makefile.in~ &amp;&amp;</userinput>