The testsuite for Binutils in this chapter is considered critical. Do not skip it under any circumstances. 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. It is recommended by the Binutils installation documentation to build Binutils outside of the source directory: mkdir ../binutils-build cd ../binutils-build Now prepare Binutils for compilation: ../binutils-&binutils-version;/configure \     --prefix=/usr --enable-shared Compile the package: make tooldir=/usr Normally, the tooldir (the directory where the executables end up) is set to $(exec_prefix)/$(target_alias), which expands into, for example, /usr/i686-pc-linux-gnu. Since we only build for our own system, we don't need this target specific directory in /usr. That setup would be used if the system was used to cross-compile (for example compiling a package on an Intel machine that generates code that can be executed on PowerPC machines). Test the results: make check Install the package: make tooldir=/usr install