Next batch of fixes for Bug 675 - missing command descriptions.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2880 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Greg Schafer 2003-09-24 23:48:45 +00:00
parent 978d0bffc4
commit 3a788f0c79
9 changed files with 67 additions and 13 deletions

View File

@ -10,7 +10,7 @@ patch:</para>
<para>Now prepare Bash for compilation:</para>
<para><screen><userinput>./configure --prefix=/tools --with-curses</userinput></screen></para>
<para><screen><userinput>./configure --prefix=/tools</userinput></screen></para>
<para>Compile the program:</para>

View File

@ -35,6 +35,7 @@ cd ../binutils-build</userinput></screen></para>
<listitem><para><userinput>--prefix=/tools</userinput>: This tells the
configure script to prepare to install the Binutils programs in the
<filename>/tools</filename> directory.</para></listitem>
<listitem><para><userinput>--disable-nls</userinput>: This disables
internationalization (a word often shortened to i18n). We don't need this
for our static programs and <emphasis>nls</emphasis> often causes problems
@ -69,14 +70,15 @@ make -C ld LIB_PATH=/tools/lib</userinput></screen></para>
<itemizedlist>
<listitem><para><userinput>-C ld clean</userinput>: This tells the make program
to remove all the compiled files only in the <filename>ld</filename>
to remove all the compiled files, but only in the <filename>ld</filename>
subdirectory.</para></listitem>
<listitem><para><userinput>-C ld LIB_PATH=/tools/lib</userinput>: This option
rebuilds everything in the <filename>ld</filename> subdirectory. Specifying the
LIB_PATH makefile variable on the command line allows us to override the default
value and have it point to our temporary tools location. This preparation will
be utilised later on in the chapter.</para></listitem>
value and have it point to our temporary tools location. The value of this
variable specifies the linker's default library search path. You'll see how this
preparation is utilised later on in the chapter.</para></listitem>
</itemizedlist>
<caution><para>Do not yet remove the Binutils build and source

View File

@ -17,6 +17,15 @@ cd ../binutils-build</userinput></screen></para>
<para><screen><userinput>../binutils-&binutils-version;/configure --prefix=/tools \
&nbsp;&nbsp;&nbsp;&nbsp;--enable-shared --with-lib-path=/tools/lib</userinput></screen></para>
<para>The meaning of the new configure option:</para>
<itemizedlist>
<listitem><para><userinput>--with-lib-path=/tools/lib</userinput>: This tells
the configure script to specify the default library search path. We don't want
the library search path to contain library directories from the host
system.</para></listitem>
</itemizedlist>
<para>Before starting to build Binutils, remember to unset any environment
variables that override the default optimization flags.</para>

View File

@ -17,10 +17,18 @@ following command will do so:</para>
<para><screen><userinput>make RUN_EXPENSIVE_TESTS=yes check</userinput></screen></para>
<para>The meaning of the make option:</para>
<itemizedlist>
<listitem><para><userinput>RUN_EXPENSIVE_TESTS=yes</userinput>: This tells the
test suite to run several additional tests that are considered relatively
expensive on some platforms. Hovever, they are generally not a problem on
Linux.</para></listitem>
</itemizedlist>
<para>And install the package:</para>
<para><screen><userinput>make install</userinput></screen></para>
</sect2>

View File

@ -14,6 +14,19 @@ GCC test suite run.</para>
<para><screen><userinput>./configure --prefix=/tools --with-tcl=/tools/lib --with-x=no</userinput></screen></para>
<para>The meaning of the configure options:</para>
<itemizedlist>
<listitem><para><userinput>--with-tcl=/tools/lib</userinput>: This ensures that
the configure script finds the Tcl installation in our temporary tools location.
We don't want it to find an existing one that may possibly reside on the host
system.</para></listitem>
<listitem><para><userinput>--with-x=no</userinput>: This tells the configure
script not to search for Tk (the Tcl GUI component) or the X Window System
libraries, both of which may possibly reside on the host system.</para></listitem>
</itemizedlist>
<para>Build the package:</para>
<para><screen><userinput>make</userinput></screen></para>

View File

@ -23,6 +23,16 @@ following command will do so:</para>
<para><screen><userinput>TZ=UTC make test</userinput></screen></para>
<para>The meaning of the make option:</para>
<itemizedlist>
<listitem><para><userinput>TZ=UTC</userinput>: This sets the time zone to
Coordinated Universal Time (UTC) also known as Greenwich Mean Time (GMT), but
only for the duration of the test suite run. This ensures the clock tests are
exercised correctly. More information on the TZ environment variable is
available later on in Chapter 7.</para></listitem>
</itemizedlist>
<para>Sometimes, package test suites will give false failures. You can
consult the LFS Wiki at <ulink url="http://wiki.linuxfromscratch.org"/>
to verify that these failures are normal. This applies to all tests
@ -32,7 +42,7 @@ throughout the book.</para>
<para><screen><userinput>make install</userinput></screen></para>
<para>Make a link:</para>
<para>Make a necessary symbolic link:</para>
<para><screen><userinput>ln -s tclsh8.4 /tools/bin/tclsh</userinput></screen></para>
<caution><para>Do not remove the

View File

@ -5,7 +5,7 @@
<para>Please note that unpacking the MAKEDEV-&makedev-version;.bz2 file
doesn't create a directory for you to <userinput>cd</userinput> into, as
the file contains one shell script.</para>
the file only contains a single shell script.</para>
<para>Install the MAKEDEV script:</para>
@ -17,6 +17,18 @@ chmod 754 /dev/MAKEDEV</userinput></screen></para>
<para><screen><userinput>cd /dev
./MAKEDEV -v generic-nopty</userinput></screen></para>
<para>The meaning of the option:</para>
<itemizedlist>
<listitem><para><userinput>-v generic-nopty</userinput>: The
<userinput>-v</userinput> parameter tells the MAKEDEV script to run in verbose
mode. The <userinput>generic-nopty</userinput> parameter instructs MAKEDEV to
create a generic selection of commonly used device special files, except for the
ptyXX and ttyXX range of files. We don't need those files because we are going
to use Unix98 PTYs via the <emphasis>devpts</emphasis> file
system.</para></listitem>
</itemizedlist>
<para>If a device you need is missing, try running
<userinput>./MAKEDEV -v &lt;device&gt;</userinput>. Alternatively, you may
create devices via the <emphasis>mknod</emphasis> program. Please refer to

View File

@ -3,8 +3,8 @@
"/usr/share/docbook/docbookx.dtd" [
<!ENTITY version "20030923">
<!ENTITY releasedate "September 23rd, 2003">
<!ENTITY version "20030924">
<!ENTITY releasedate "September 24th, 2003">
<!ENTITY nbsp " ">
<!ENTITY ftp-root "ftp://ftp.linuxfromscratch.org">