fileutils-inst.xml 1.9 KB

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