%general-entities; ]> Binutils-&binutils-version; - Pass 2 Binutils tools, pass 2 <segmentedlist> <segtitle>&buildtime;</segtitle> <segtitle>&diskspace;</segtitle> <seglistitem><seg>1.5 SBU</seg><seg>108 MB</seg></seglistitem> </segmentedlist> </sect2> <sect2 role="installation"> <title>Re-installation of Binutils Create a separate build directory again: mkdir ../binutils-build cd ../binutils-build Now prepare Binutils for compilation: ../binutils-&binutils-version;/configure --prefix=/tools \ --enable-shared --with-lib-path=/tools/lib The meaning of the new configure option: --with-lib-path=/tools/lib This tells the configure script to specify the library search path during the compilation of Binutils, resulting in /tools/lib to be passed to the linker. This prevents the linker from searching through library directories on the host. Before starting to build Binutils, remember to unset any environment variables that override the default optimization flags. Compile the package: make Compilation is now complete. As discussed earlier, we don't recommend running the test suites for the temporary tools here in this chapter. If nevertheless you want to run the Binutils test suite, the following command will do so: make -k check Except for a few known failures, the binutils tests should all pass. The exceptions to this rule are as follows: * 5 FAIL (unexpected failure) for visibility * 1 FAIL for selective4 * 1 FAIL for selective5 And install the package: make install Now prepare the linker for the "Re-adjusting" phase in the next chapter: make -C ld clean make -C ld LIB_PATH=/usr/lib:/lib Do not yet remove the Binutils source and build directories. You will need these directories again in the next chapter in the state they are in now. <para>The details on this package are found in <xref linkend="contents-binutils"/>.</para> </sect2> </sect1>