Now that the temporary C libraries have been installed, we want all the tools compiled in the rest of this chapter to be linked against these libraries. To accomplish this, we need to adjust the linker's scripts and the compiler's specs file. First install the adjusted linker scripts by running the following from within the binutils-build directory: make -C ld install-data-local These scripts were adjusted a little while back, at the end of the first pass of Binutils, and contain no mention of /lib, /usr/lib or /usr/local/lib. From this point onwards everything will link only against the libraries in /tools/lib. Now that the scripts are adjusted, you have to remove the Binutils build and source directories. The next thing to do is to amend our GCC specs file so that it points to the new dynamic linker. A simple sed will accomplish this: SPECFILE=/tools/lib/gcc-lib/*/*/specs sed -e 's@/lib/ld.so.1@/tools/lib/ld.so.1@g' \     -e 's@/lib/ld-linux.so.2@/tools/lib/ld-linux.so.2@g' \     $SPECFILE > tempspecfile mv tempspecfile $SPECFILE unset SPECFILE We recommend that you cut-and-paste the above rather than try and type it all in. Or you can edit the specs file by hand if you want to: just replace "/lib/ld-linux.so.2" with "/tools/lib/ld-linux.so.2" and "/lib/ld.so.1" with "/tools/lib/ld.so.1". Lastly, there is a possibility that some include files from the host system have found their way into GCC's private include dir. This can happen because of GCC's "fixincludes" process which runs as part of the GCC build. We'll explain more about this further on in this chapter. For now, run the following commands to eliminate this possibility. rm -f /tools/lib/gcc-lib/*/*/include/{pthread.h,bits/sigthread.h} It is imperative at this point to stop and ensure that the basic functionality of the new toolchain is working as expected. We are going to perform a simple sanity check: echo 'main(){}' > dummy.c gcc dummy.c readelf -l a.out | grep ': /tools' If everything is working correctly, the output of the last command will be: [Requesting program interpreter: /tools/lib/ld-linux.so.2] 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 /tools/lib 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: rm dummy.c a.out This completes the installation of the self-contained toolchain, which can now be used to build the rest of the temporary tools.