It is important that Binutils be the first package to get compiled, because both Glibc and GCC perform various tests on the available linker and assembler to determine which of their own features to enable. Even though Binutils is an important toolchain package, we are not going to run the test suite at this early stage. First, the test suite framework is not yet in place and second, the programs from this first pass will soon be overwritten by those installed in the second pass. This package is known to behave badly when you have changed its default optimization flags (including the -march and -mcpu options). Therefore, if you have defined any environment variables that override default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting or modifying them when building Binutils. The Binutils documentation recommends building Binutils outside of the source directory in a dedicated build directory: mkdir ../binutils-build cd ../binutils-build Next, prepare Binutils to be compiled: ../binutils-&binutils-version;/configure \     --prefix=/tools --disable-nls The meaning of the configure switches: --prefix=/tools: This tells the configure script to prepare to install the Binutils programs in the /tools directory. --disable-nls: This disables internationalization (a word often shortened to i18n). We don't need this for our static programs and nls often causes problems when linking statically. Continue with compiling the package: make configure-host make LDFLAGS="-all-static" The meaning of the make option: LDFLAGS="-all-static": This tells the linker that all the Binutils programs should be linked statically. And install the package: make install Now prepare the linker for the "locking in" of Glibc later on: make -C ld clean make -C ld LIB_PATH=/tools/lib Do not yet remove the Binutils build and source directories. You will need them again in their current state a bit further on in this chapter.