|
|
@@ -359,13 +359,13 @@ file records the bad login attempts.</para>
|
|
|
|
|
|
<para>Now that the new and final C libraries have been installed, it's time to
|
|
|
adjust our toolchain again. We'll adjust it so that it will link any newly
|
|
|
-compiled program against these new libraries. This is in fact the same we did
|
|
|
-in the "Adjusting" phase in the beginning of the previous chapter, even though
|
|
|
-it looks like the reverse: then we guided the chain from the host's
|
|
|
-<filename class="directory">{,/usr}/lib</filename> to the new
|
|
|
+compiled program against these new libraries. This is in fact the same thing we
|
|
|
+did in the "Adjusting" phase in the beginning of the previous chapter, even
|
|
|
+though it looks like the reverse: then we guided the chain from the host's
|
|
|
+<filename class="directory">/{,usr/}lib</filename> to the new
|
|
|
<filename class="directory">/tools/lib</filename>, now we guide it from that
|
|
|
same <filename class="directory">/tools/lib</filename>
|
|
|
-to the LFS's <filename class="directory">{,/usr}/lib</filename>.</para>
|
|
|
+to the LFS's <filename class="directory">/{,usr/}lib</filename>.</para>
|
|
|
|
|
|
<para>First we adjust the linker. For this we retained the
|
|
|
source and build directories from the second pass over Binutils. Install the
|
|
|
@@ -380,7 +380,7 @@ source and build directories from the second pass in
|
|
|
don't have access to them, don't worry, all is not lost. Just ignore the above
|
|
|
command. The result will be that the next package, Binutils, will link against
|
|
|
the C libraries in <filename class="directory">/tools</filename> rather
|
|
|
-than <filename class="directory">{,/usr}/lib</filename>. This is not ideal,
|
|
|
+than in <filename class="directory">/{,usr/}lib</filename>. This is not ideal,
|
|
|
however, our testing has shown that the resulting Binutils program binaries
|
|
|
should be identical.</para></note>
|
|
|
|
Alex Gronenwoud