Changeset 73aedd1d for chapter05/binutils-pass1.xml
- Timestamp:
- 11/01/2003 10:31:50 PM (21 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 49f4dd5
- Parents:
- 0b400add
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/binutils-pass1.xml
r0b400add r73aedd1d 8 8 &aa-binutils-shortdesc; 9 9 &aa-binutils-dep; 10 &c5-binutils-pass1-inst; 10 11 <sect2><title> </title><para> </para></sect2> 12 13 <sect2> 14 <title>Installation of Binutils</title> 15 16 <para>It is important that Binutils be the first package to get compiled, 17 because both Glibc and GCC perform various tests on the available linker and 18 assembler to determine which of their own features to enable.</para> 19 20 <note><para>Even though Binutils is an important toolchain package, we are not 21 going to run the test suite at this early stage. First, the test suite framework 22 is not yet in place and second, the programs from this first pass will soon be 23 overwritten by those installed in the second pass.</para></note> 24 25 <para>This package is known to behave badly when you have changed its default 26 optimization flags (including the -march and -mcpu options). Therefore, if 27 you have defined any environment variables that override default 28 optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting or 29 modifying them when building Binutils.</para> 30 31 <para>The Binutils documentation recommends building Binutils outside of the 32 source directory in a dedicated build directory:</para> 33 34 <screen><userinput>mkdir ../binutils-build 35 cd ../binutils-build</userinput></screen> 36 37 <note><para>If you want the SBU values listed in the rest of the book to be of 38 any use, you will have to measure the time it takes to build this package. To 39 achieve this easily, you could do something like: 40 <userinput>time { ./configure ... && ... && ... && make install; }</userinput>.</para></note> 41 42 <para>Now prepare Binutils for compilation:</para> 43 44 <screen><userinput>../binutils-&binutils-version;/configure \ 45 --prefix=/tools --disable-nls</userinput></screen> 46 47 <para>The meaning of the configure options:</para> 48 49 <itemizedlist> 50 <listitem><para><userinput>--prefix=/tools</userinput>: This tells the 51 configure script to prepare to install the Binutils programs in the 52 <filename>/tools</filename> directory.</para></listitem> 53 54 <listitem><para><userinput>--disable-nls</userinput>: This disables 55 internationalization (a word often shortened to i18n). We don't need this 56 for our static programs and <emphasis>nls</emphasis> often causes problems 57 when linking statically.</para></listitem> 58 </itemizedlist> 59 60 <para>Continue with compiling the package:</para> 61 62 <screen><userinput>make configure-host 63 make LDFLAGS="-all-static"</userinput></screen> 64 65 <para>The meaning of the make options:</para> 66 67 <itemizedlist> 68 <listitem><para><userinput>configure-host</userinput>: This forces all the 69 subdirectories to be configured immediately. A statically linked build will 70 fail without it. We therefore use this option to work around the 71 problem.</para></listitem> 72 73 <listitem><para><userinput>LDFLAGS="-all-static"</userinput>: This tells the 74 linker that all the Binutils programs should be linked statically. However, 75 strictly speaking, <userinput>"-all-static"</userinput> is first passed to the 76 <emphasis>libtool</emphasis> program which then passes 77 <userinput>"-static"</userinput> on to the linker.</para></listitem> 78 </itemizedlist> 79 80 <para>And install the package:</para> 81 82 <screen><userinput>make install</userinput></screen> 83 84 <para>Now prepare the linker for the "locking in" of Glibc later on:</para> 85 86 <screen><userinput>make -C ld clean 87 make -C ld LDFLAGS="-all-static" LIB_PATH=/tools/lib</userinput></screen> 88 89 <para>The meaning of the make options:</para> 90 91 <itemizedlist> 92 <listitem><para><userinput>-C ld clean</userinput>: This tells the make program 93 to remove all the compiled files, but only in the <filename>ld</filename> 94 subdirectory.</para></listitem> 95 96 <listitem><para><userinput>-C ld LDFLAGS="-all-static" LIB_PATH=/tools/lib</userinput>: 97 This option rebuilds everything in the <filename>ld</filename> subdirectory. 98 Specifying the LIB_PATH makefile variable on the command line allows us to 99 override the default value and have it point to our temporary tools location. 100 The value of this variable specifies the linker's default library search path. 101 You'll see how this preparation is used later on in the 102 chapter.</para></listitem> 103 </itemizedlist> 104 105 <!-- HACK - Force some whitespace to appease tidy --> 106 <literallayout></literallayout> 107 108 <warning><para>Do not yet remove the Binutils build and source directories. You 109 will need them again in their current state a bit further on in this 110 chapter.</para></warning> 111 112 <!-- HACK - Force some whitespace to appease tidy --> 113 <literallayout></literallayout> 114 115 </sect2> 11 116 12 117 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.