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 after the user chroot'ed into $LFS or when he rebooted
|
---|
10 | the system into LFS.</para>
|
---|
11 |
|
---|
12 | <para><userinput>--bindir=$LFS/bin:</userinput> This installs the executable
|
---|
13 | files in $LFS/bin. We do this because we want bash to be in /bin, not in
|
---|
14 | /usr/bin. One reason being: the /usr partition might be on a separate
|
---|
15 | partition which has to be mounted at some point. Before that partition is
|
---|
16 | mounted a user needs and will want to have bash available (it will be hard to
|
---|
17 | execute the boot scripts without a shell for instance).</para>
|
---|
18 |
|
---|
19 | <para><userinput>ln -s bash sh:</userinput> This command creates the sh
|
---|
20 | symlink that points to bash. Most scripts run themselves via 'sh'
|
---|
21 | (invoked by the #!/bin/sh as the first line in the scripts) which
|
---|
22 | invokes a special bash mode. Bash will then behave (as closely as
|
---|
23 | possible) as the original Bourne shell.</para>
|
---|
24 |
|
---|
25 | <para>The <userinput>&&</userinput>'s at the end of every line cause
|
---|
26 | the next command to be executed only if the previous command exists
|
---|
27 | with a return value of 0 indicating success. In case all of these
|
---|
28 | commands are copy&pasted
|
---|
29 | on the shell, is is important to be ensured that if
|
---|
30 | ./configure fails, make isn't being executed and, likewise, if make fails,
|
---|
31 | that make install isn't being executed, and so forth.</para>
|
---|
32 |
|
---|
33 | </sect2>
|
---|
34 |
|
---|