mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-08-01 09:06:17 +01:00
removed stuff no longer pertinent after the /static implementation
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1943 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
parent
4ceb3a1a3e
commit
8cd994f474
@ -4,16 +4,9 @@
|
||||
<para><userinput>--enable-static-link:</userinput> This configure
|
||||
option causes bash to be linked statically.</para>
|
||||
|
||||
<para><userinput>--prefix=$LFS/usr:</userinput> This configure option installs
|
||||
all of Bash's files under the $LFS/usr directory, which becomes the /usr
|
||||
directory when chroot'ed or reboot'ed into LFS.</para>
|
||||
|
||||
<para><userinput>--bindir=$LFS/bin:</userinput> This installs the executable
|
||||
files in $LFS/bin. We do this because we want bash to be in /bin, not in
|
||||
/usr/bin. One reason being: the /usr partition might be on a separate
|
||||
partition which has to be mounted at some point. Before that partition is
|
||||
mounted you need and will want to have bash available (it will be hard to
|
||||
execute the boot scripts without a shell for instance).</para>
|
||||
<para><userinput>--prefix=$LFS/static:</userinput> This configure option
|
||||
installs all of Bash's files under the $LFS/static directory, which becomes
|
||||
the /static directory when chroot'ed or reboot'ed into LFS.</para>
|
||||
|
||||
<para><userinput>--with-curses:</userinput> This causes bash to be
|
||||
linked against the curses library instead of the default termcap
|
||||
@ -28,12 +21,6 @@ trouble later on in this chapter when you install the Texinfo package.
|
||||
That package requires ncurses, and termcap can't reliably be used
|
||||
there.</para>
|
||||
|
||||
<para><userinput>ln -sf bash $LFS/bin/sh:</userinput> This command creates
|
||||
the <filename class="symlink">sh</filename> symlink that points to bash. Most
|
||||
scripts run themselves via 'sh' (invoked by the #!/bin/sh as the first line
|
||||
in the scripts) which invokes a special bash mode. Bash will then behave
|
||||
(as closely as possible) as the original Bourne shell.</para>
|
||||
|
||||
<para>The <userinput>&&</userinput>'s at the end of every line cause
|
||||
the next command to be executed only if the previous command exits
|
||||
with a return value of 0 indicating success. In case all of these
|
||||
|
Loading…
Reference in New Issue
Block a user