bash-static-exp.sgml 2.0 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455
  1. <sect2>
  2. <title>Command explanations</title>
  3. <para>
  4. <userinput>--enable-static-link:</userinput> This configure
  5. option causes Bash to be linked statically
  6. </para>
  7. <para>
  8. <userinput>--prefix=$LFS/usr:</userinput> This configure option installs
  9. all of Bash's files under the $LFS/usr directory, which becomes the /usr
  10. directory after you chroot into $LFS or when you reboot the system into LFS.
  11. </para>
  12. <para>
  13. <userinput>--bindir=$LFS/bin:</userinput> This installs the executable
  14. files in $LFS/bin. We do this because we want bash to be in /bin, not in
  15. /usr/bin. One reason being: your /usr partition might be on a seperate
  16. partition which has to be mounted at some point. Before that partition is
  17. mounted you need and will want to have bash available (it will be hard to
  18. execute the boot scripts without a shell for instance).
  19. </para>
  20. <para>
  21. <userinput>--disable-nls:</userinput> This disables the build of NLS
  22. (National Language Support). It's only a waste of time for now as Bash
  23. will be reinstalled in the next chapter.
  24. </para>
  25. <para>
  26. <userinput>--with-curses:</userinput> This causes Bash to be linked
  27. against the curses library instead of the default termcap library which
  28. is becoming obsolete.
  29. </para>
  30. <para>
  31. <userinput>ln -s bash sh:</userinput> This command creates the sh
  32. symlink that points to bash. Most scripts run themselves via 'sh'; sh
  33. being a symlink to the default system shell. Because programs and
  34. scripts don't know what shell you use by default (could be bash, ksh,
  35. korn, tch, csh and others) they use the common symlink sh which, if the
  36. system is properly setup, always points to the system's default shell.
  37. </para>
  38. <para>
  39. The <userinput>&amp;&amp;</userinput>'s at the end of every line cause
  40. the next command only to be executed when the previous command exists
  41. with a return value of 0 indicating success. In case you copy&amp;paste
  42. all of these commands on the shell you want to be ensured that if
  43. ./configure fails, make isn't being executed and likewise if make fails
  44. that make install isn't being executed, and so forth.
  45. </para>
  46. </sect2>