ldso-inst.sgml 1.4 KB

12345678910111213141516171819202122232425262728293031323334353637383940
  1. <sect2>
  2. <title>Installation of Ld.so</title>
  3. <para>
  4. Install Ld.so by running the following commands:
  5. </para>
  6. <blockquote><literallayout>
  7. <userinput>cd util &amp;&amp;</userinput>
  8. <userinput>make ldd ldconfig &amp;&amp;</userinput>
  9. <userinput>cp ldd /bin &amp;&amp;</userinput>
  10. <userinput>cp ldconfig /sbin &amp;&amp;</userinput>
  11. <userinput>cd ../man &amp;&amp;</userinput>
  12. <userinput>cp ldd.1 /usr/share/man/man1 &amp;&amp;</userinput>
  13. <userinput>cp *.8 /usr/share/man/man8 &amp;&amp;</userinput>
  14. <userinput>rm /usr/bin/ldd &amp;&amp;</userinput>
  15. <userinput>hash -r</userinput>
  16. </literallayout></blockquote>
  17. <para>
  18. The <quote>hash -r</quote> command is to make bash forget about the
  19. locations of previously executed commands. If you have executed ldd
  20. before, bash expects it to be found in /usr/bin. Since we moved it to
  21. /bin, the cache needs to be purged so bash can find it in /bin when you
  22. want to execute it again.
  23. </para>
  24. <para>
  25. You might have noticed that we don't use the compiler optimizations for
  26. this package. The reason is that overriding the CFLAGS variable causes
  27. compilation problems. You would have to edit the Config.mk file and add
  28. the proper values to the CFLAGS variable and then compile the package.
  29. If you want to do that it's up to you. I don't think it's worth the
  30. trouble though. The ld and ldd programs usually are only rarely used.
  31. </para>
  32. </sect2>