| 1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071 | <sect2><title> </title><para> </para></sect2><sect2><title>Installation of Binutils</title><para>It is important that Binutils be the first package to get compiled,because both Glibc and GCC perform various tests on the available linker andassembler to determine which of their own features to enable.</para><note><para>Even though Binutils is an important toolchain package, we are notgoing to run the testsuite at this early stage. First, the testsuite frameworkis not yet in place and second, the programs from this first pass will soon beoverwritten by those installed in the second pass.</para></note><para>This package is known to behave badly when you have changed its defaultoptimization flags (including the -march and -mcpu options). Therefore, ifyou have defined any environment variables that override defaultoptimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting ormodifying them when building Binutils.</para><para>It is recommended by the Binutils installation documentation to buildBinutils outside of the source directory in a dedicated directory:</para><para><screen><userinput>mkdir ../binutils-buildcd ../binutils-build</userinput></screen></para><para>Next, prepare Binutils to be compiled:</para><para><screen><userinput>../binutils-&binutils-version;/configure \    --prefix=/tools --disable-nls</userinput></screen></para><para>The meaning of the configure switches:</para><itemizedlist><listitem><para><userinput>--prefix=/tools</userinput>: This tells theconfigure script to prepare to install the Binutils programs in the<filename>/tools</filename> directory.</para></listitem><listitem><para><userinput>--disable-nls</userinput>: This disablesinternationalization (a word often shortened to i18n). We don't need thisfor our static programs and <emphasis>nls</emphasis> often causes problemswhen linking statically.</para></listitem></itemizedlist><para>Continue with compiling the package:</para><para><screen><userinput>make configure-hostmake LDFLAGS="-all-static"</userinput></screen></para><para>The meaning of the make option:</para><itemizedlist><listitem><para><userinput>LDFLAGS="-all-static"</userinput>: This tellsthe linker that all the Binutils programs should be linkedstatically.</para></listitem></itemizedlist><para>And install the package:</para><para><screen><userinput>make install</userinput></screen></para><para>Now prepare the linker for the "locking in" of Glibc later on:</para><para><screen><userinput>make -C ld cleanmake -C ld LIB_PATH=/tools/lib</userinput></screen></para><caution><para>Do not yet remove the Binutils build and sourcedirectories. You will need them again in their current state a bit further onin this chapter.</para></caution></sect2>
 |