source: chapter05/fileutils-inst.xml@ f1d11bf

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_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
Last change on this file since f1d11bf was 1d91cdf, checked in by Marc Heerdink <gimli@…>, 22 years ago

[Bug 261] Removed the --libexecdir configure option from fileutils' configure flags

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

  • Property mode set to 100644
File size: 2.1 KB
RevLine 
[6370fa6]1<sect2>
2<title>Installation of Fileutils</title>
3
[f66ac14]4<para>The programs from a statically linked fileutils package may cause
[70cdda10]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>
[f66ac14]10
[c15aead]11<para>Note that in some cases using these sed commands will result in
[5850fbfe]12problems not being able to compile this package at all, even when your
[0d11c30]13system has an AMD CPU and has Glibc-2.2.3 (or higher) installed. If that's
[70cdda10]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>
[c15aead]18
[70cdda10]19<para>To fix this package to compile properly on AMD/Glibc-2.2.3
[acb2801]20machines, run the following commands. Do <emphasis>not</emphasis>
[0ed57c8]21attempt this fix if you don't have Glibc-2.2.3 installed. It will more
[70cdda10]22than likely result in all kinds of compile time problems.</para>
23
[4d6fc2da]24<para><screen><userinput>cp lib/Makefile.in lib/Makefile.in.backup &amp;&amp;
25sed -e 's/\(.*\)\(fopen-safer\.c \)\\/\1\2atexit.c \\/' \
26&nbsp;&nbsp;&nbsp;-e 's/\(.*\)\(idcache\$U\.\$.*\)\\/\1\2atexit$U.$(OBJEXT) \\/' \
[8c5e7152]27&nbsp;&nbsp;&nbsp;lib/Makefile.in.backup &gt; lib/Makefile.in</userinput></screen></para>
[4d6fc2da]28
29<para>Install fileutils by running the following commands:</para>
30
31<para><screen><userinput>./configure --disable-nls \
[1d91cdf]32&nbsp;&nbsp;&nbsp;--prefix=$LFS/usr --bindir=$LFS/bin &amp;&amp;
[4d6fc2da]33make LDFLAGS=-static &amp;&amp;
34make install &amp;&amp;
35cd $LFS/usr/bin &amp;&amp;
36ln -sf ../../bin/install</userinput></screen></para>
[6370fa6]37
[ec710a3]38<para>Once you have installed fileutils, you can test whether the
39segmentation fault problem has been avoided by running
[f66ac14]40<userinput>$LFS/bin/ls</userinput>. If this works, then you are OK. If
41not, then you need to re-do the installation using the sed commands if
42you didn't use them, or without the sed commands if you did use
43them.</para>
[ec710a3]44
[6370fa6]45</sect2>
46
Note: See TracBrowser for help on using the repository browser.