Ignore:
Timestamp:
02/19/2004 10:35:14 PM (20 years ago)
Author:
Alex Gronenwoud <alex@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
cd0c92d6
Parents:
e1c7e32
Message:

Small textual frobbings, and removing an unneeded {,share/}.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3256 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter06/chapter06.xml

    re1c7e32 r9da62ab  
    360360<para>Now that the new and final C libraries have been installed, it's time to
    361361adjust our toolchain again. We'll adjust it so that it will link any newly
    362 compiled program against these new libraries. This is in fact the same we did
    363 in the "Adjusting" phase in the beginning of the previous chapter, even though
    364 it looks like the reverse: then we guided the chain from the host's
    365 <filename class="directory">{,/usr}/lib</filename> to the new
     362compiled program against these new libraries. This is in fact the same thing we
     363did in the "Adjusting" phase in the beginning of the previous chapter, even
     364though it looks like the reverse: then we guided the chain from the host's
     365<filename class="directory">/{,usr/}lib</filename> to the new
    366366<filename class="directory">/tools/lib</filename>, now we guide it from that
    367367same <filename class="directory">/tools/lib</filename>
    368 to the LFS's <filename class="directory">{,/usr}/lib</filename>.</para>
     368to the LFS's <filename class="directory">/{,usr/}lib</filename>.</para>
    369369
    370370<para>First we adjust the linker. For this we retained the
     
    381381command. The result will be that the next package, Binutils, will link against
    382382the C libraries in <filename class="directory">/tools</filename> rather
    383 than <filename class="directory">{,/usr}/lib</filename>. This is not ideal,
     383than in <filename class="directory">/{,usr/}lib</filename>. This is not ideal,
    384384however, our testing has shown that the resulting Binutils program binaries
    385385should be identical.</para></note>
Note: See TracChangeset for help on using the changeset viewer.