a few typo fixes

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@917 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Mark Hymers 2001-08-07 09:48:59 +00:00
parent 59250de15e
commit 9960acdb67
2 changed files with 10 additions and 11 deletions

View File

@ -5,12 +5,12 @@
null device to compile properly. All other devices will be created in the
next section.</para>
<para><userinput>touch /etc/ld.so.conf</userinput> One of the final steps of
the Glibc installation is running ldconfig to update the dynamic loader
cache. If this file isn't present Glibc will abort with an error that it
can't read the file. So we create an empty file for it (the empty file
will have Glibc default to using /lib and
/usr/lib which is fine right now).</para>
<para><userinput>touch /etc/ld.so.conf</userinput> One of the final steps
of the Glibc installation is running ldconfig to update the dynamic loader
cache. If this file doesn't exist, the installation will abort with an error
that it can't read the file, so we simply create an empty file (the empty file
will have Glibc default to using /lib and /usr/lib which is fine
right now).</para>
<para><userinput>sed s/"\$(PERL)"/"\/usr\/bin\/perl"/
../glibc-2.2.3/malloc/Makefile &gt; tmp~:</userinput> This sed command

View File

@ -36,13 +36,12 @@ would do.</para>
*** some features will be disabled.
*** Check the INSTALL file for required versions.</screen></blockquote>
<para>This warning refers to the missing msgfmt program from the gettext
package. But there is nothing to worry about: Glib will still be
installed the same way as when msgfmt is present. It can safely be
ignored in our case.</para>
<para> This warning refers to the missing msgfmt program from the
gettext package, but it can safely be ignored in our case. The glibc
installation will not be affected.</para>
<para>The last two commands make you exit and re-enter the chroot'ed
environment and re-entering it. This is done to get rid of the "I have
environment. This is done to get rid of the "I have
no name!" message in the command prompt, which was caused by bash's
inability to resolve a userid to a username (which in turn was caused by
the missing Glibc installation).</para>