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.
The first thing to do is to adjust the linker. For this we retained the source and build directories from the second pass over Binutils. Install the adjusted linker by running the following from within the binutils-build directory:
make -C ld install |
From now on every compiled program will link only against the libraries in /usr/lib and /lib .
You can now remove the Binutils source and build directories.
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:
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 |
Again, cutting and pasting the above is recommended. And just like before, it is a good idea to check the specs file to ensure the intended changes were actually made.
| Caution | |||
It is imperative at this point to stop and ensure that the basic functionality of the adjusted toolchain is working as expected. We are going to perform a simple sanity check:
If everything is working correctly, the output of the last command will be:
If you did not receive the output as shown above then something is seriously wrong. You will need to investigate and retrace your steps to find out where the problem is and correct it. There is no point in continuing until this is done. Most likely, something went wrong with the specs file amendment above. Note especially that /lib now appears as the prefix of our dynamic linker. Of course, if you are working on a platform where the name of the dynamic linker is something other than ld-linux.so.2 then the output will be slightly different. Once you are satisfied that all is well, clean up the test files:
|