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