Ignore:
Timestamp:
09/07/2001 08:51:36 PM (23 years ago)
Author:
Gerard Beekmans <gerard@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v3_0, v3_1, v3_2, v3_3, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
0ed57c8
Parents:
ebedcc2
Message:

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

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1198 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter05/fileutils-inst.xml

    rebedcc2 r70cdda10  
    33
    44<para>The programs from a statically linked fileutils package may cause
    5 segmentation faults on certain systems. These systems are often, but not
    6 limited to, Linux systems that run Glibc-2.2.3 with an AMD CPU (Athlons
    7 and Durons are the most reported used CPU's). If you are in this category,
    8 run the following to sed commands before you compile this
    9 package.</para>
     5segmentation faults on certain systems, if your distribution has
     6Glibc-2.2.3 or higher installed. It also seems to happen mostly on machines
     7powered by an AMD CPU, but there is a case or two where an Intel system
     8is affected as well. If your system falls under this category, try the
     9following fix.</para>
    1010
    1111<para>Note that in some cases using these sed commands will result in
    12 problems not being able to compile this at package at all. If that's the
    13 case, you'll need to remove the fileutils-&fileutils-version; directory
    14 and unpack it again from the tarball before continuing.
     12problems not being able to compile this at package at all, even when your
     13system has and AMD CPU and has Glibc-2.2.3 (or higher) installed. If that's
     14the case, you'll need to remove the fileutils-&fileutils-version; directory
     15and unpack it again from the tarball before continuing. We believe this
     16may be the case when your distribution has altered Glibc-2.2.3 somehow,
     17but details are unavailable at the time.</para>
    1518
    16 <screen><userinput>cp lib/Makefile.in lib/Makefile.in.backup &amp;&amp;</userinput>
     19<para>To fix this package to compile properly on AMD/Glibc-2.2.3
     20machines, run the following commands. do <emphasis>not</emphasis>
     21attempt this fix your don't have Glibc-2.2.3 installed. It will more
     22than likely result in all kinds of compile time problems.</para>
     23
     24<para><screen><userinput>cp lib/Makefile.in lib/Makefile.in.backup &amp;&amp;</userinput>
    1725<userinput>sed -e 's/\(.*\)\(fopen-safer\.c \)\\/\1\2atexit.c \\/' \</userinput>
    1826<userinput>&nbsp;&nbsp;&nbsp;-e 's/\(.*\)\(idcache\$U\.\$.*\)\\/\1\2atexit$U.$(OBJEXT) \\/' \</userinput>
Note: See TracChangeset for help on using the changeset viewer.