Fix spelling

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1324 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Mark Hymers 2001-10-24 10:20:53 +00:00
parent 3448e74e91
commit ef94a94b1d
10 changed files with 14 additions and 11 deletions

View File

@ -7,7 +7,7 @@
sh from the bash package
as from the binutils package
ld from the binutils packag
ld from the binutils package
strip from the binutils package
bison from the bison package

View File

@ -23,6 +23,9 @@
</para></listitem>
<listitem><para>October 24th, 2001 [markh]: General: Fixed a bundle of
spelling errors which were reported.</para></listitem>
<listitem><para>October 12th, 2001 [markh]: Chapter 5 - Kernel: Added
explanation as to why we copy the kernel headers rather than symlink
them.</para></listitem>

View File

@ -36,7 +36,7 @@ help us to see the possible other causes of your problem.</para>
<para>When something goes wrong during the stage where the configure
script is run, look at the last lines of the
<filename>config.log</filename>. This file contains possible errors
encoutered during configure which aren't always printed to the screen.
encountered during configure which aren't always printed to the screen.
Include those relevant lines if you decide to ask for help.</para>
</sect2>

View File

@ -27,7 +27,7 @@ true in a _loong_ time.</screen>
<para>The relevant part here is where he states that the headers should
be the ones which <emphasis>glibc was compiled against</emphasis>. These are
the headers which should remain accessable and so by copying them, we ensure
the headers which should remain accessible and so by copying them, we ensure
that we follow these guidelines. Also note that as long as you don't have
those symlinks, it is perfectly alright to have the kernel sources
in <filename>/usr/src/linux</filename>.</para>

View File

@ -3,7 +3,7 @@
<para>Before Sh-utils is installed, the sh-utils patch file may need to
be applied. This patch is needed to avoid a conflict of variable names
with certain Glibc verions (usually glibc-2.1.x) when compiling sh-utils
with certain Glibc versions (usually glibc-2.1.x) when compiling sh-utils
statically. It is however safe to apply the patch even if you are
running a different glibc version, so if you aren't sure, it's
best to apply it.</para>

View File

@ -2,7 +2,7 @@
<title>Command explanations</title>
<para><userinput>patch -Np1 -i ../findutils-4.1.patch</userinput>: This
patch is to fix some compliation errors by
patch is to fix some compilation errors by
avoiding a variable conflict and changing some bad syntax.</para>
</sect2>

View File

@ -14,7 +14,7 @@ will have Glibc default to using /lib and /usr/lib which is fine).</para>
<para><userinput>sed 's%\$(PERL)%/usr/bin/perl%'
malloc/Makefile &gt; tmp~:</userinput> This sed command
searches through <filename>malloc/Makefile</filename> and
converts all occurances of <filename>$(PERL)</filename> to
converts all occurences of <filename>$(PERL)</filename> to
<filename>/usr/bin/perl</filename>. The output is then written to the
file <filename>tmp~</filename>. This is done because Glibc can't
autodetect perl since it hasn't been installed yet.</para>
@ -26,7 +26,7 @@ when using sed, we can't write straight back to this file so we need to
use a temporary file in between.</para>
<para><userinput>sed 's/root/0' login/Makefile &gt;
tmp~:</userinput> This sed command replaces all occurances of
tmp~:</userinput> This sed command replaces all occurences of
<filename>root</filename> in
<filename>login/Makefile</filename> with 0. This is
because as we don't have glibc on the LFS system yet, usernames can't

View File

@ -14,7 +14,7 @@ system when /usr may not be mounted.</para>
<para><userinput>chmod 755 *.5.2:</userinput> Shared libraries should be
executable. Ncurses install routine doesn't set the permissions
properly so we do it manaully instead.</para>
properly so we do it manually instead.</para>
<para><userinput>ln -sf libncurses.a libcurses.a:</userinput> Some
programs try to link using -lcurses instead of -lncurses. This symlink

View File

@ -4,8 +4,8 @@
<!ENTITY book SYSTEM "book/book.xml">
<!ENTITY version "20011015">
<!ENTITY releasedate "October 15th, 2001">
<!ENTITY version "20011024">
<!ENTITY releasedate "October 24th, 2001">
<!ENTITY ftp-root "ftp://ftp.linuxfromscratch.org">
<!ENTITY http-root "http://ftp.linuxfromscratch.org">

View File

@ -29,7 +29,7 @@ They're just sitting there taking up (precious) disk space. It's not
hard to get an LFS system installed under 100 MB. Does that still sound
like a lot? A few of us have been working on creating a very small
embedded LFS system. We installed a system that was just enough to run
the Apache web server; total disk space usage was aproximately 8 MB.
the Apache web server; total disk space usage was approximately 8 MB.
With further stripping, that can be brought down to 5 MB or less. Try
that with a generic Debian or Redhat distribution.</para>