|
@@ -3,14 +3,17 @@
|
|
|
|
|
|
<para>Before you attempt to install Bash, you have to check to make sure
|
|
<para>Before you attempt to install Bash, you have to check to make sure
|
|
your distribution has the <filename>/usr/lib/libcurses.a</filename> and
|
|
your distribution has the <filename>/usr/lib/libcurses.a</filename> and
|
|
-<filename>/usr/lib/libncurses.a</filename> files. If both of the files
|
|
|
|
-are missing, you have to install the ncurses development package. This
|
|
|
|
-package is often call something like <emphasis>ncurses-dev</emphasis>.</para>
|
|
|
|
-
|
|
|
|
-<para>If this package is already installed, or you just did it, check
|
|
|
|
-for the two files again. Often the <filename>libcurses.a</filename> file
|
|
|
|
-is (still) missing. If so, then create <filename>libcurses.a</filename>
|
|
|
|
-as a symlink by running the following commands:</para>
|
|
|
|
|
|
+<filename>/usr/lib/libncurses.a</filename> files. If your host
|
|
|
|
+distribution is an LFS system, all files will be present if you followed
|
|
|
|
+the instructions of the book version you read exactly.</para>
|
|
|
|
+
|
|
|
|
+<para>If both of the files are missing, you have to install the ncurses
|
|
|
|
+development package. This package is often call something like
|
|
|
|
+<emphasis>ncurses-dev</emphasis>. If this package is already installed,
|
|
|
|
+or you just did it, check for the two files again. Often the
|
|
|
|
+<filename>libcurses.a</filename> file is (still) missing. If so, then
|
|
|
|
+create <filename>libcurses.a</filename> as a symlink by running the
|
|
|
|
+following commands:</para>
|
|
|
|
|
|
<para><screen><userinput>cd /usr/lib &&</userinput>
|
|
<para><screen><userinput>cd /usr/lib &&</userinput>
|
|
<userinput>ln -s libncurses.a libcurses.a</userinput></screen></para>
|
|
<userinput>ln -s libncurses.a libcurses.a</userinput></screen></para>
|