- Timestamp:
- 08/19/2003 05:07:26 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, 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/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 85d2668
- Parents:
- 503e1a6
- Location:
- chapter06
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/adjustingtoolchain.xml
r503e1a6 r460ac758 3 3 <?dbhtml filename="adjustingtoolchain.html" dir="chapter06"?> 4 4 5 <para>Now that we have compiled all the necessary tools, it is time to 6 re-adjust our toolchain. We will set it up so that it will link any newly 7 compiled program against the new Glibc. Basically, this is the reverse of 8 what we did in the "Locking in" stage in the beginning of chapter 5.</para> 9 10 <para>The first thing to do is to adjust the linker scripts. For this we 11 retained the <filename class="directory">binutils-build</filename> 12 directory from the second pass over Binutils. Run the following:</para> 13 5 14 <para><screen><userinput>cd binutils-build 6 make -C ld INSTALL=/stage1/bin/install install-data-local 15 make -C ld INSTALL=/stage1/bin/install install-data-local</userinput></screen></para> 7 16 8 SPECFILE=/stage1/lib/gcc-lib/*/*/specs 17 <para>This installs the adjusted linker scripts. The linker scripts contain 18 no mention of <filename class="directory">/stage1/lib</filename> anymore. 19 From now on every compiled program will link <emphasis>only</emphasis> 20 against the libraries in <filename>/usr/lib</filename> and 21 <filename>/lib</filename>. The extra 22 <userinput>INSTALL=/stage1/bin/install</userinput> is needed because the 23 Makefile created during the second pass still contains the reference to 24 <filename>/usr/bin/install</filename>, which we obviously haven't installed 25 yet.</para> 26 27 <para>You can now remove the Binutils source and build directories.</para> 28 29 <para>The next thing to do is to amend our GCC specs file so that it points 30 to the new dynamic linker. Just like earlier on, we use a sed to accomplish 31 this:</para> 32 33 <para><screen><userinput>SPECFILE=/stage1/lib/gcc-lib/*/*/specs 9 34 sed -e 's@/stage1/lib/ld.so.1@/lib/ld.so.1@g' \ 10 35 -e 's@/stage1/lib/ld-linux.so.2@/lib/ld-linux.so.2@g' $SPECFILE > XX … … 12 37 unset SPECFILE</userinput></screen></para> 13 38 39 <para>Again, cutting and pasting the above is recommended. And just like 40 before, it is a good idea to check the linker scripts and the specs file o 41 ensure the intended changes were actually made.</para> 42 43 <para>Note that the linker scripts will still contain a reference to 44 <filename class="directory">/stage1/i686-pc-linux-gnu/lib</filename>. This 45 is unavoidable, but luckily does not present a problem. There are no 46 libraries in that location as all the temporary stage1 libraries are 47 located in <filename class="directory">/stage1/lib</filename>.</para> 48 14 49 </sect1> 15 50 -
chapter06/chapter06.xml
r503e1a6 r460ac758 15 15 &c6-manpages; 16 16 &c6-glibc; 17 &c6-adjustingtoolchain; 17 18 &c6-binutils; 18 19 &c6-gcc;
Note:
See TracChangeset
for help on using the changeset viewer.