| 1 | <sect2>
|
|---|
| 2 | <title>Command explanations</title>
|
|---|
| 3 |
|
|---|
| 4 | <para><userinput>--enable-static-link:</userinput> This configure
|
|---|
| 5 | option causes Bash to be linked statically</para>
|
|---|
| 6 |
|
|---|
| 7 | <para><userinput>--prefix=$LFS/usr:</userinput> This configure option installs
|
|---|
| 8 | all of Bash's files under the $LFS/usr directory, which becomes the /usr
|
|---|
| 9 | directory when chroot'ed or reboot'ed into LFS.</para>
|
|---|
| 10 |
|
|---|
| 11 | <para><userinput>--bindir=$LFS/bin:</userinput> This installs the executable
|
|---|
| 12 | files in $LFS/bin. We do this because we want bash to be in /bin, not in
|
|---|
| 13 | /usr/bin. One reason being: the /usr partition might be on a separate
|
|---|
| 14 | partition which has to be mounted at some point. Before that partition is
|
|---|
| 15 | mounted you need and will want to have bash available (it will be hard to
|
|---|
| 16 | execute the boot scripts without a shell for instance).</para>
|
|---|
| 17 |
|
|---|
| 18 | <para><userinput>--with-curses:</userinput> This causes Bash to be
|
|---|
| 19 | linked against the curses library instead of the default termcap
|
|---|
| 20 | library which is becoming obsolete.</para>
|
|---|
| 21 |
|
|---|
| 22 | <para>It is not strictly necessary for the static bash to be linked
|
|---|
| 23 | against libncurses (it can link against a static termcap for the time
|
|---|
| 24 | being just fine because we will reinstall Bash in chapter 6 anyways,
|
|---|
| 25 | where we will use libncurses), but it's a good test to make sure that
|
|---|
| 26 | the ncurses package has been installed properly. If not, you will get in
|
|---|
| 27 | trouble later on in this chapter when you install the Texinfo package.
|
|---|
| 28 | That package requires ncurses and termcap can't reliably be used
|
|---|
| 29 | there.</para>
|
|---|
| 30 |
|
|---|
| 31 | <para><userinput>ln -sf bash $LFS/bin/sh:</userinput> This command creates
|
|---|
| 32 | the <filename class="symlink">sh</filename> symlink that points to bash. Most
|
|---|
| 33 | scripts run themselves via 'sh' (invoked by the #!/bin/sh as the first line
|
|---|
| 34 | in the scripts) which invokes a special bash mode. Bash will then behave
|
|---|
| 35 | (as closely as possible) as the original Bourne shell.</para>
|
|---|
| 36 |
|
|---|
| 37 | <para>The <userinput>&&</userinput>'s at the end of every line cause
|
|---|
| 38 | the next command to be executed only if the previous command exists
|
|---|
| 39 | with a return value of 0 indicating success. In case all of these
|
|---|
| 40 | commands are copy&pasted on the shell, it is important to be ensured
|
|---|
| 41 | that if ./configure fails, make isn't being executed and, likewise, if make
|
|---|
| 42 | fails, that make install isn't being executed, and so forth.</para>
|
|---|
| 43 |
|
|---|
| 44 | </sect2>
|
|---|
| 45 |
|
|---|
