<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-adjust our toolchain. We'll adjust it so that it will link any newly compiled program against the new C libraries. Basically, this is the reverse of what we did in 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 we retained 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 contain no 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 the Makefile created during the second pass still contains the reference to <filename>/usr/bin/install</filename>, which we obviously haven't installed yet.</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 points to the new dynamic linker. Just like earlier on, we use a sed to accomplish this:</para> <para><screen><userinput>SPECFILE=/tools/lib/gcc-lib/*/*/specs sed -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 > newspecfile mv newspecfile $SPECFILE unset SPECFILE</userinput></screen></para> <para>Again, cutting and pasting the above is recommended. And just like before, it is a good idea to check the linker scripts and the specs file to ensure 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>. This is unavoidable, but luckily does not present a problem. There are no libraries in that location as all the temporary tools libraries are located in <filename class="directory">/tools/lib</filename>.</para> </sect1>