|
@@ -308,7 +308,7 @@ the LFS partition).</para>
|
|
|
<para>When logged in as <emphasis>root</emphasis>, making a single mistake
|
|
|
can damage or even wreck your system. Therefore we recommend that you
|
|
|
build the packages in this chapter as an unprivileged user. You could
|
|
|
-of course use your own user name, but to make it easier to set up a clean
|
|
|
+of course use your own user name, but to make it easier to set up a clean
|
|
|
work environment we'll create a new user <emphasis>lfs</emphasis> and
|
|
|
use this one during the installation process. As <emphasis>root</emphasis>,
|
|
|
issue the following commands to add the new user:</para>
|
|
@@ -382,7 +382,7 @@ export LFS LC_ALL PATH
|
|
|
feature: <userinput>bash</userinput> uses a hash table to remember the
|
|
|
full pathnames of executable files to avoid searching the PATH time and time
|
|
|
again to find the same executable. However, we'd like the new tools to be
|
|
|
-used as soon as they are installed. By switching off the hash function, our
|
|
|
+used as soon as they are installed. By switching off the hash function, our
|
|
|
"interactive" commands (<userinput>make</userinput>,
|
|
|
<userinput>patch</userinput>, <userinput>sed</userinput>,
|
|
|
<userinput>cp</userinput> and so forth) will always use
|
|
@@ -400,7 +400,7 @@ making their messages follow the conventions of a specified country. If your
|
|
|
host system uses a version of Glibc older than 2.2.4,
|
|
|
having LC_ALL set to something other than "POSIX" or "C" during this chapter
|
|
|
may cause trouble if you exit the chroot environment and wish to return later.
|
|
|
-By setting LC_ALL to "POSIX" (or "C", the two are equivalent) we ensure that
|
|
|
+By setting LC_ALL to "POSIX" (or "C", the two are equivalent) we ensure that
|
|
|
everything will work as expected in the chroot environment.</para>
|
|
|
|
|
|
<para>We prepend <filename>/tools/bin</filename> to the standard PATH so
|
|
@@ -454,7 +454,7 @@ Binutils build and source directories.</para>
|
|
|
to the new dynamic linker. A simple sed will accomplish this:</para>
|
|
|
|
|
|
<!-- Ampersands are needed to allow cut and paste -->
|
|
|
-
|
|
|
+
|
|
|
<screen><userinput>SPECFILE=/tools/lib/gcc-lib/*/*/specs &&
|
|
|
sed -e 's@ /lib/ld-linux.so.2@ /tools/lib/ld-linux.so.2@g' \
|
|
|
$SPECFILE > tempspecfile &&
|
|
@@ -476,7 +476,7 @@ name of your platform's dynamic linker in the above commands. Refer back to
|
|
|
<para>Lastly, there is a possibility that some include files from the host
|
|
|
system have found their way into GCC's private include dir. This can happen
|
|
|
because of GCC's "fixincludes" process which runs as part of the GCC build.
|
|
|
-We'll explain more about this further on in this chapter. For now, run the
|
|
|
+We'll explain more about this further on in this chapter. For now, run the
|
|
|
following commands to eliminate this possibility:</para>
|
|
|
|
|
|
<screen><userinput>rm -f /tools/lib/gcc-lib/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen>
|