Various textual corrections. Thanks Chris Staub.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@7317 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Jeremy Huntwork 2006-01-30 06:51:33 +00:00
parent 62d3362b8d
commit 28bb06349a
11 changed files with 33 additions and 25 deletions

View File

@ -326,7 +326,7 @@
<varlistentry>
<term><emphasis role="bold">LSB</emphasis></term>
<listitem>
<para>Linux Standards Base</para>
<para>Linux Standard Base</para>
</listitem>
</varlistentry>

View File

@ -43,6 +43,9 @@
<para>[jhuntwork] - Adjust binutils-pass1 so we don't need to hang on to its
source directories. Also use 'gcc -dumpmachine' instead of the MACHTYPE var.</para>
</listitem>
<listitem>
<para>[jhuntwork] - Various textual corrections. Thanks Chris Staub.
</listitem>
</itemizedlist>
</listitem>

View File

@ -46,12 +46,12 @@
<screen><userinput>./configure --prefix=/tools --without-bash-malloc</userinput></screen>
<variablelist>
<title>The meaning of the configure options:</title>
<title>The meaning of the configure option:</title>
<varlistentry>
<term><parameter>--without-bash-malloc</parameter></term>
<listitem>
<para>This options turns off the use of Bash's memory allocation
<para>This option turns off the use of Bash's memory allocation
(<function>malloc</function>) function which is known to cause
segmentation faults. By turning this option off, Bash will use
the <function>malloc</function> functions from Glibc which are

View File

@ -93,7 +93,7 @@ cd ../gcc-build</userinput></screen>
<screen><userinput>make bootstrap</userinput></screen>
<variablelist>
<title>The meaning of the make parameters:</title>
<title>The meaning of the make parameter:</title>
<varlistentry>
<term><parameter>bootstrap</parameter></term>

View File

@ -50,7 +50,7 @@
./configure --prefix=/tools --disable-shared</userinput></screen>
<variablelist>
<title>The meaning of the configure options:</title>
<title>The meaning of the configure option:</title>
<varlistentry>
<term><parameter>--disable-shared</parameter></term>

View File

@ -47,7 +47,7 @@
--disable-perl-regexp</userinput></screen>
<variablelist>
<title>The meaning of the configure options:</title>
<title>The meaning of the configure option:</title>
<varlistentry>
<term><parameter>--disable-perl-regexp</parameter></term>

View File

@ -52,10 +52,7 @@
<important>
<para>After installing each package, delete its source and build directories,
unless specifically instructed otherwise. Deleting the sources prevents
mis-configuration when the same package is reinstalled later. Only three
of the packages need to retain the source and build directories in order
for their contents to be used by later commands. Pay special attention to
these reminders.</para>
mis-configuration when the same package is reinstalled later.</para>
</important>
<para>Check one last time that the <envar>LFS</envar> environment

View File

@ -59,16 +59,25 @@ cd ../binutils-build</userinput></screen>
<screen><userinput>make tooldir=/usr</userinput></screen>
<para>Normally, the tooldir (the directory where the executables will ultimately
be located) is set to <filename
class="directory">$(exec_prefix)/$(target_alias)</filename>. For example, i686
machines would expand that to <filename
class="directory">/usr/i686-pc-linux-gnu</filename>. Because this is a custom
system, this target-specific directory in <filename
class="directory">/usr</filename> is not required. <filename
class="directory">$(exec_prefix)/$(target_alias)</filename> would be used if the
system was used to cross-compile (for example, compiling a package on an Intel
machine that generates code that can be executed on PowerPC machines).</para>
<variablelist>
<title>The meaning of the make parameter:</title>
<varlistentry>
<term><parameter>tooldir=/usr</parameter></term>
<listitem>
<para>Normally, the tooldir (the directory where the executables will
ultimately be located) is set to <filename
class="directory">$(exec_prefix)/$(target_alias)</filename>. For
example, i686 machines would expand that to <filename
class="directory">/usr/i686-pc-linux-gnu</filename>. Because this is
a custom system, this target-specific directory in <filename
class="directory">/usr</filename> is not required. <filename
class="directory">$(exec_prefix)/$(target_alias)</filename> would be
used if the system was used to cross-compile (for example, compiling a
package on an Intel machine that generates code that can be executed
on PowerPC machines).</para>
</listitem>
</varlistentry>
</variablelist>
<important><para>The test suite for Binutils in this section is
considered critical. Do not skip it under any

View File

@ -32,9 +32,8 @@ command:</para>
<para>The command uses <parameter>0:0</parameter> instead of
<parameter>root:root</parameter>, because <command>chown</command>
is unable to resolve the name <quote>root</quote> until the password
file has been created. This book assumes you ran this
<command>chown</command> command.</para>
is unable to resolve the name <quote>root</quote> until the
<filename>passwd</filename> file has been created.</para>
</sect1>

View File

@ -17,7 +17,7 @@ debug the software fully anymore.</para>
experience any difficulties. However, it is easy to make a typo and
render the new system unusable, so before running the
<command>strip</command> command, it is a good idea to make a
backup of the current situation.</para>
backup of the LFS system in its current state.</para>
<para>Before performing the stripping, take special care to ensure that
none of the binaries that are about to be stripped are running. If

View File

@ -113,7 +113,7 @@ url="&blfs-root;view/svn/postlfs/editors.html#postlfs-editors-vim"/>.</para>
</sect2>
<sect2 id="conf-vim" role="configuration"><title>Configuring Vim</title>
<indexterm zone="conf-vim"><primary sortas="e-/etc/vim">/etc/vim</primary></indexterm>
<indexterm zone="conf-vim"><primary sortas="e-/etc/vimrc">/etc/vimrc</primary></indexterm>
<para>By default, <command>vim</command> runs in vi-incompatible mode. This may
be new to users who have used other editors in the past. The