&c5-introduction; &c5-whystatic; &c5-creatingstage1dir; &c5-addinguser; &c5-settingenviron; &c5-binutils-pass1; &c5-gcc-pass1; &c5-kernelheaders; &c5-glibc; &c5-lockingglibc; &c5-tcl; &c5-expect; &c5-dejagnu; &c5-gcc-pass2; &c5-binutils-pass2; &c5-gawk; &c5-coreutils; &c5-bzip2; &c5-gzip; &c5-diffutils; &c5-findutils; &c5-make; &c5-grep; &c5-sed; &c5-gettext; &c5-ncurses; &c5-patch; &c5-tar; &c5-texinfo; &c5-bash; &c5-utillinux; &c5-perl; Now that we have compiled all the necessary tools, it is time to re-adjust our toolchain. We will set it up so that it will link any newly compiled program against the new Glibc, which is the first thing to get compiled in the next chapter. Basically, this is the reverse of what we did in the "Locking in" stage in the beginning of this chapter. The first thing to do is to adjust the linker scripts. For this we retained the binutils-build directory from the second pass over Binutils. Do the following: cd binutils-build make -C ld INSTALL=/stage1/bin/install install-data-local This installs the adjusted linker scripts. The linker scripts now contain no mention of /stage1/lib. From now on every compiled program will link only against the libraries in /usr/lib and /lib. The extra INSTALL=/stage1/bin/install is needed because the Makefile created during the second pass still contains the reference to /usr/bin/install, which we obviously haven't installed yet. 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: CURRENTSPECFILE=/stage1/lib/gcc-lib/*/*/specs sed -e 's@/stage1/lib/ld.so.1@/lib/ld.so.1@g' \     -e 's@/stage1/lib/ld-linux.so.2@/lib/ld-linux.so.2@g' \     $CURRENTSPECFILE > newspecfile mv newspecfile $CURRENTSPECFILE unset CURRENTSPECFILE 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. Note that the linker scripts will still contain a reference to /stage1/i686-pc-linux-gnu/lib. This is unavoidable, but luckily does not present a problem. There are no libraries in that location as all the temporary stage1 libraries are located in /stage1/lib. If your LFS partition is rather small, you will be glad to learn that you can throw away some unnecessary things. The executables and libraries you have built so far contain about 130 MB of unneeded debugging symbols. Remove those symbols like this: strip --strip-unneeded /stage1/{,s}bin/* strip --strip-debug /stage1/lib/* The first of the above commands will skip some twenty files, reporting that it doesn't recognize their file format. Most of them are scripts instead of binaries. Take care not to use --strip-unneeded on the libraries -- they would be destroyed and you would have to build Glibc all over again. To save another couple of megabytes, you can throw away the documentation and some of the bigger unneeded programs: rm -r /stage1/share/{doc,info,man} rm /stage1/bin/{addr2line,gprof,nm,size,strings,strip} You will now need to have at least 700 MB of free space on your LFS filesystem to be able to build and install Glibc in the next phase.