| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051 | <sect1 id="ch06-adjustingtoolchain"><title>Re-adjusting the toolchain</title><?dbhtml filename="adjustingtoolchain.html" dir="chapter06"?><para>Now that the new C libraries have been installed, it's time to re-adjustour toolchain. We'll adjust it so that it will link any newly compiled programagainst the new C libraries. Basically, this is the reverse of what we didin the "Locking in" stage in the beginning of the previous chapter.</para><para>The first thing to do is to adjust the linker scripts. For this weretained the source and build directories from the second pass over Binutils.Install the adjusted linker scripts by running the following from within the<filename class="directory">binutils-build</filename> directory:</para><para><screen><userinput>make -C ld install-data-local</userinput></screen></para><para>The linker scripts now containno mention of <filename class="directory">/tools/lib</filename> anymore.From now on every compiled program will link <emphasis>only</emphasis>against the libraries in <filename>/usr/lib</filename> and<filename>/lib</filename>. The extra<userinput>INSTALL=/tools/bin/install</userinput> is needed because theMakefile created during the second pass still contains the reference to<filename>/usr/bin/install</filename>, which we obviously haven't installedyet.</para><para>You can now remove the Binutils source and build directories.</para><para>The next thing to do is to amend our GCC specs file so that it pointsto the new dynamic linker. Just like earlier on, we use a sed to accomplishthis:</para><para><screen><userinput>SPECFILE=/tools/lib/gcc-lib/*/*/specssed -e 's@/tools/lib/ld.so.1@/lib/ld.so.1@g' \    -e 's@/tools/lib/ld-linux.so.2@/lib/ld-linux.so.2@g' \    $SPECFILE > newspecfilemv newspecfile $SPECFILEunset SPECFILE</userinput></screen></para><para>Again, cutting and pasting the above is recommended. And just likebefore, it is a good idea to check the linker scripts and the specs file toensure the intended changes were actually made.</para><para>Note that the linker scripts will still contain a reference to<filename class="directory">/tools/i686-pc-linux-gnu/lib</filename>. Thisis unavoidable, but luckily does not present a problem. There are nolibraries in that location as all the temporary tools libraries arelocated in <filename class="directory">/tools/lib</filename>.</para></sect1>
 |