%general-entities; ]> binutils-pass1 &binutils-version;

&binutils-url;

Binutils tools, pass 1 Go back and re-read the notes in the section titled . Understanding the notes labeled important can save you a lot of problems later. It is important that Binutils be the first package compiled because both Glibc and GCC perform various tests on the available linker and assembler to determine which of their own features to enable. The Binutils documentation recommends building Binutils in a dedicated build directory: mkdir -v build cd build In order for the SBU values listed in the rest of the book to be of any use, measure the time it takes to build this package from the configuration, up to and including the first install. To achieve this easily, wrap the commands in a time command like this: time { ../configure ... && make && make install; }. Now prepare Binutils for compilation: ../configure --prefix=$LFS/tools \ --with-sysroot=$LFS \ --target=$LFS_TGT \ --disable-nls \ --disable-werror --prefix=$LFS/tools This tells the configure script to prepare to install the binutils programs in the $LFS/tools directory. --with-sysroot=$LFS For cross compilation, this tells the build system to look in $LFS for the target system libraries as needed. --target=$LFS_TGT Because the machine description in the LFS_TGT variable is slightly different than the value returned by the config.guess script, this switch will tell the configure script to adjust binutil's build system for building a cross linker. --disable-nls This disables internationalization as i18n is not needed for the temporary tools. --disable-werror This prevents the build from stopping in the event that there are warnings from the host's compiler. Continue with compiling the package: make Install the package: make install -j1 -j1 An issue in the building system may cause the installation to fail with -j N in MAKEFLAGS. Override it to workaround this issue.