[bc82645e] | 1 | <sect1 id="ch06-adjustingtoolchain">
|
---|
[1f30432] | 2 | <title>Re-adjusting the toolchain</title>
|
---|
[bc82645e] | 3 | <?dbhtml filename="adjustingtoolchain.html" dir="chapter06"?>
|
---|
| 4 |
|
---|
[1f30432] | 5 | <para>Now that the new C libraries have been installed, it's time to re-adjust
|
---|
| 6 | our toolchain. We'll adjust it so that it will link any newly compiled program
|
---|
| 7 | against the new C libraries. Basically, this is the reverse of what we did
|
---|
| 8 | in the "Locking in" stage in the beginning of the previous chapter.</para>
|
---|
[460ac758] | 9 |
|
---|
| 10 | <para>The first thing to do is to adjust the linker scripts. For this we
|
---|
[1f30432] | 11 | retained the source and build directories from the second pass over Binutils.
|
---|
| 12 | Install the adjusted linker scripts by running the following from within the
|
---|
| 13 | <filename class="directory">binutils-build</filename> directory:</para>
|
---|
[460ac758] | 14 |
|
---|
[1f30432] | 15 | <para><screen><userinput>make -C ld INSTALL=/stage1/bin/install install-data-local</userinput></screen></para>
|
---|
[460ac758] | 16 |
|
---|
[1f30432] | 17 | <para>The linker scripts now contain
|
---|
[460ac758] | 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>
|
---|
[a5b2aa9] | 28 |
|
---|
[460ac758] | 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
|
---|
[a5b2aa9] | 34 | sed -e 's@/stage1/lib/ld.so.1@/lib/ld.so.1@g' \
|
---|
[1f30432] | 35 | -e 's@/stage1/lib/ld-linux.so.2@/lib/ld-linux.so.2@g'
|
---|
| 36 | $SPECFILE > newspecfile
|
---|
| 37 | mv newspecfile $SPECFILE
|
---|
[585ce08] | 38 | unset SPECFILE</userinput></screen></para>
|
---|
[bc82645e] | 39 |
|
---|
[460ac758] | 40 | <para>Again, cutting and pasting the above is recommended. And just like
|
---|
[1f30432] | 41 | before, it is a good idea to check the linker scripts and the specs file to
|
---|
[460ac758] | 42 | ensure the intended changes were actually made.</para>
|
---|
| 43 |
|
---|
| 44 | <para>Note that the linker scripts will still contain a reference to
|
---|
| 45 | <filename class="directory">/stage1/i686-pc-linux-gnu/lib</filename>. This
|
---|
| 46 | is unavoidable, but luckily does not present a problem. There are no
|
---|
| 47 | libraries in that location as all the temporary stage1 libraries are
|
---|
| 48 | located in <filename class="directory">/stage1/lib</filename>.</para>
|
---|
| 49 |
|
---|
[bc82645e] | 50 | </sect1>
|
---|
| 51 |
|
---|