fileutils-inst.xml 1.8 KB

1234567891011121314151617181920212223242526272829303132333435363738394041
  1. <sect2>
  2. <title>Installation of Fileutils</title>
  3. <para>The programs from a statically linked Fileutils package may cause
  4. segmentation faults on certain systems, if your distribution has
  5. Glibc-2.2.3 installed. It seems to happen mostly on machines
  6. powered by an AMD CPU, but there is a case or two where an Intel system
  7. is affected as well. If your system falls in this category, apply the
  8. patch.</para>
  9. <para>Note that in some cases using this patch will result in not being
  10. able to compile this package at all, even when your system has an AMD CPU
  11. and has Glibc-2.2.3 (or higher) installed. If that's the case, you'll need
  12. to remove the fileutils-&fileutils-version; directory and unpack it again
  13. from the tarball before continuing. We believe this may be the case when
  14. your distribution has altered Glibc-2.2.3 somehow, but details are
  15. unavailable at this time.</para>
  16. <para>To fix this package to compile properly on AMD/Glibc-2.2.3
  17. machines, run the following command. Do <emphasis>not</emphasis>
  18. attempt this fix if you don't have Glibc-2.2.3 installed. It will more
  19. than likely result in all kinds of compile time problems.</para>
  20. <para><screen><userinput>patch -Np1 -i ../fileutils-&fileutils-patch-version;.patch</userinput></screen></para>
  21. <para>Install Fileutils by running the following commands:</para>
  22. <para><screen><userinput>LDFLAGS=-static \
  23. &nbsp;&nbsp;&nbsp;&nbsp;./configure --disable-nls --prefix=$LFS/static &amp;&amp;
  24. make &amp;&amp;
  25. make install</userinput></screen></para>
  26. <para>Once you have installed Fileutils, you can test whether the
  27. segmentation fault problem has been avoided by running
  28. <userinput>$LFS/static/bin/ls</userinput>. If this works, then you are OK. If
  29. not, then you need to re-do the installation with the patch if
  30. you didn't use it, or without the patch if you did use
  31. it.</para>
  32. </sect2>