- Timestamp:
- 02/11/2004 10:02:32 PM (21 years ago)
- 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, 12.2, 12.2-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/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- cd1ddd7
- Parents:
- c91dd5b
- Location:
- chapter06
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/chapter06.xml
rc91dd5b ra0b689e 358 358 359 359 360 <sect1 id="ch-system- adjustingtoolchain">360 <sect1 id="ch-system-readjusting"> 361 361 <title>Re-adjusting the toolchain</title> 362 <?dbhtml filename="adjustingtoolchain.html" dir="chapter06"?> 363 364 <para>Now that the new C libraries have been installed, it's time to re-adjust 365 our toolchain. We'll adjust it so that it will link any newly compiled program 366 against the new C libraries. Basically, this is the reverse of what we did 367 in the "locking in" stage in the beginning of the previous chapter.</para> 368 369 <para>The first thing to do is to adjust the linker. For this we retained the 362 <?dbhtml filename="readjusting.html" dir="chapter06"?> 363 364 <para>Now that the new and final C libraries have been installed, it's time to 365 adjust our toolchain again. We'll adjust it so that it will link any newly 366 compiled program against these new libraries. This is in fact the same we did 367 in the "Adjusting" phase in the beginning of the previous chapter, even though 368 it looks like the reverse: then we guided the chain from the host's 369 <filename class="directory">{,/usr}/lib</filename> to the new 370 <filename class="directory">/tools/lib</filename>, now we guide it from that 371 same <filename class="directory">/tools/lib</filename> 372 to the LFS's <filename class="directory">{,/usr}/lib</filename>.</para> 373 374 <para>First we adjust the linker. For this we retained the 370 375 source and build directories from the second pass over Binutils. Install the 371 376 adjusted linker by running the following from within the … … 379 384 don't have access to them, don't worry, all is not lost. Just ignore the above 380 385 command. The result will be that the next package, Binutils, will link against 381 the Glibclibraries in <filename class="directory">/tools</filename> rather382 than <filename class="directory"> /usr</filename>. This is not ideal, however,383 our testing has shown that the resulting Binutils program binaries should be 384 identical.</para></note>386 the C libraries in <filename class="directory">/tools</filename> rather 387 than <filename class="directory">{,/usr}/lib</filename>. This is not ideal, 388 however, our testing has shown that the resulting Binutils program binaries 389 should be identical.</para></note> 385 390 386 391 <para>From now on every compiled program will link <emphasis>only</emphasis> -
chapter06/gcc.xml
rc91dd5b ra0b689e 91 91 <note><para>At this point it is strongly recommended to repeat the sanity check 92 92 we performed earlier in this chapter. Refer back to 93 <xref linkend="ch-system- adjustingtoolchain"/> and repeat the check. If the results93 <xref linkend="ch-system-readjusting"/> and repeat the check. If the results 94 94 are wrong, then most likely you erroneously applied the GCC Specs patch from 95 95 <xref linkend="chapter-temporary-tools"/>.</para></note>
Note:
See TracChangeset
for help on using the changeset viewer.