Changeset f57e3d1 for chapter06/adjustingtoolchain.xml
- Timestamp:
- 10/07/2003 12:41:12 AM (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_0, 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:
- f861982
- Parents:
- 04a3351
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/adjustingtoolchain.xml
r04a3351 rf57e3d1 18 18 source and build directories from the second pass in Chapter 5 or otherwise 19 19 accidentally deleted them or just don't have access to them, don't worry, all is 20 not lost. Just ignore th is step. The result will be that the next package,21 Binutils, will link against the Glibc libraries in20 not lost. Just ignore the above command. The result will be that the next 21 package, Binutils, will link against the Glibc libraries in 22 22 <filename class="directory">/tools</filename> rather than 23 23 <filename class="directory">/usr</filename>. This is not ideal, however, our … … 42 42 43 43 <para><screen><userinput>SPECFILE=/tools/lib/gcc-lib/*/*/specs 44 sed -e 's@/tools/lib/ld.so.1@/lib/ld.so.1@g' \ 45 -e 's@/tools/lib/ld-linux.so.2@/lib/ld-linux.so.2@g' \ 44 sed -e 's@/tools/lib/ld-linux.so.2@/lib/ld-linux.so.2@g' \ 46 45 $SPECFILE > newspecfile 47 46 mv newspecfile $SPECFILE … … 51 50 before, it is a good idea to check the specs file to ensure the intended 52 51 changes were actually made.</para> 52 53 <important><para>If you are working on a platform where the name of the dynamic 54 linker is something other than <filename>ld-linux.so.2</filename>, you 55 <emphasis>must</emphasis> substitute <filename>ld-linux.so.2</filename> with the 56 name of your platform's dynamic linker in the above commands. Refer back to the 57 "Toolchain technical notes" section if necessary.</para></important> 53 58 54 59 <caution><para>It is imperative at this point to stop and ensure that the
Note:
See TracChangeset
for help on using the changeset viewer.