10.0
10.0-rc1
10.1
10.1-rc1
11.0
11.0-rc1
11.0-rc2
11.0-rc3
11.1
11.1-rc1
11.2
11.2-rc1
11.3
11.3-rc1
12.0
12.0-rc1
12.1
12.1-rc1
12.2-rc1
6.0
6.1
6.1.1
6.3
6.4
6.5
6.6
6.7
6.8
7.0
7.1
7.2
7.3
7.4
7.5
7.5-systemd
7.6
7.6-systemd
7.7
7.7-systemd
7.8
7.8-systemd
7.9
7.9-systemd
8.0
8.1
8.2
8.3
8.4
9.0
9.1
arm
bdubbs/gcc13
ml-11.0
multilib
renodr/libudev-from-systemd
s6-init
trunk
v4_0
v4_1
v5_0
v5_1
v5_1_1
xry111/arm64
xry111/arm64-12.0
xry111/clfs-ng
xry111/lfs-next
xry111/loongarch
xry111/loongarch-12.0
xry111/loongarch-12.1
xry111/mips64el
xry111/pip3
xry111/rust-wip-20221008
xry111/update-glibc
Line | |
---|
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/static:</userinput> This configure option
|
---|
8 | installs all of Bash's files under the $LFS/static directory, which becomes
|
---|
9 | the /static directory when chroot'ed or reboot'ed into LFS.</para>
|
---|
10 |
|
---|
11 | <para><userinput>--with-curses:</userinput> This causes bash to be
|
---|
12 | linked against the curses library instead of the default termcap
|
---|
13 | library which is becoming obsolete.</para>
|
---|
14 |
|
---|
15 | <para>It is not strictly necessary for the static bash to be linked
|
---|
16 | against libncurses (it can link against a static termcap for the time
|
---|
17 | being just fine because we will reinstall Bash in chapter 6 anyways,
|
---|
18 | where we will use libncurses), but it's a good test to make sure that
|
---|
19 | the Ncurses package has been installed properly. If not, you will get in
|
---|
20 | trouble later on in this chapter when you install the Texinfo package.
|
---|
21 | That package requires ncurses, and termcap can't reliably be used
|
---|
22 | there.</para>
|
---|
23 |
|
---|
24 | <para>The <userinput>&&</userinput>'s at the end of every line cause
|
---|
25 | the next command to be executed only if the previous command exits
|
---|
26 | with a return value of 0 indicating success. In case all of these
|
---|
27 | commands are copy&pasted on the shell, it is important to ensure
|
---|
28 | that if ./configure fails, make isn't executed and, likewise, if make
|
---|
29 | fails, that make install isn't executed, and so forth.</para>
|
---|
30 |
|
---|
31 | </sect2>
|
---|
32 |
|
---|
Note:
See
TracBrowser
for help on using the repository browser.