source: chapter05/binutils-pass1.xml@ 8f192d8

6.1.1
Last change on this file since 8f192d8 was 8f192d8, checked in by Ken Moffat <ken@…>, 19 years ago

binutils and glibc patches, space/time updates

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/6.1.1/BOOK@7017 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 5.0 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
3 <!ENTITY % general-entities SYSTEM "../general.ent">
4 %general-entities;
5]>
6<sect1 id="ch-tools-binutils-pass1" role="wrap">
7<title>Binutils-&binutils-version; - Pass 1</title>
8<?dbhtml filename="binutils-pass1.html"?>
9
10<indexterm zone="ch-tools-binutils-pass1">
11<primary sortas="a-Binutils">Binutils</primary>
12<secondary>tools, pass 1</secondary></indexterm>
13
14<sect2 role="package"><title/>
15<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="../chapter06/binutils.xml" xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
16
17<segmentedlist>
18<segtitle>&buildtime;</segtitle>
19<segtitle>&diskspace;</segtitle>
20<seglistitem><seg>1.0 SBU</seg><seg>179 MB</seg></seglistitem>
21</segmentedlist>
22
23<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="../chapter06/binutils.xml" xpointer="xpointer(/sect1/sect2[1]/segmentedlist[2])"/>
24
25</sect2>
26
27<sect2 role="installation">
28<title>Installation of Binutils</title>
29
30<para>It is important that Binutils be the first package compiled
31because both Glibc and GCC perform various tests on the available
32linker and assembler to determine which of their own features to
33enable.</para>
34
35<para>This package is known to have issues when its default
36optimization flags (including the <parameter>-march</parameter> and
37<parameter>-mcpu</parameter> options) are changed. If any environment
38variables that override default optimizations have been defined, such
39as <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar>,
40unset them when building Binutils.</para>
41
42<para>If you are building from a host running Gcc-4 or later, it is necessary
43to patch the first build of this version of Binutils so that it can be
44compiled by the host system.</para>
45
46<screen><userinput>patch -Np1 -i ../binutils-&binutils-version;-gcc4-1.patch
47</userinput></screen>
48
49<para>The Binutils documentation recommends building Binutils outside of the
50source directory in a dedicated build directory:</para>
51
52<screen><userinput>mkdir ../binutils-build
53cd ../binutils-build</userinput></screen>
54
55<note><para>In order for the SBU values listed in the rest of the book
56to be of any use, measure the time it takes to build this package from
57the configuration, up to and including the first install. To achieve
58this easily, wrap the three commands in a <command>time</command>
59command like this: <userinput>time { ./configure ... &amp;&amp; make
60&amp;&amp; make install; }</userinput>.</para></note>
61
62<para>Now prepare Binutils for compilation:</para>
63
64<screen><userinput>../binutils-&binutils-version;/configure --prefix=/tools --disable-nls</userinput></screen>
65
66<para>The meaning of the configure options:</para>
67
68<variablelist>
69<varlistentry>
70<term><parameter>--prefix=/tools</parameter></term>
71<listitem><para>This tells the configure script to prepare to install the Binutils
72programs in the <filename class="directory">/tools</filename> directory.</para></listitem>
73</varlistentry>
74
75<varlistentry>
76<term><parameter>--disable-nls</parameter></term>
77<listitem><para>This disables internationalization as i18n is not needed for the
78temporary tools.</para></listitem>
79</varlistentry>
80</variablelist>
81
82<para>Continue with compiling the package:</para>
83
84<screen><userinput>make</userinput></screen>
85
86<para>Compilation is now complete. Ordinarily we would now run the
87test suite, but at this early stage the test suite framework (Tcl,
88Expect, and DejaGNU) is not yet in place. The benefits of running the
89tests at this point are minimal since the programs from this
90first pass will soon be replaced by those from the second.</para>
91
92<para>Install the package:</para>
93
94<screen><userinput>make install</userinput></screen>
95
96<para>Next, prepare the linker for the <quote>Adjusting</quote> phase
97later on:</para>
98
99<screen><userinput>make -C ld clean
100make -C ld LIB_PATH=/tools/lib</userinput></screen>
101
102<para>The meaning of the make parameters:</para>
103
104<variablelist>
105<varlistentry>
106<term><parameter>-C ld clean</parameter></term>
107<listitem><para>This tells the make program to remove all compiled
108files in the <filename class="directory">ld</filename>
109subdirectory.</para></listitem>
110</varlistentry>
111
112<varlistentry>
113<term><parameter>-C ld LIB_PATH=/tools/lib</parameter></term>
114<listitem><para>This option rebuilds everything in the
115<filename class="directory">ld</filename> subdirectory. Specifying
116the <envar>LIB_PATH</envar> Makefile variable on the command
117line allows us to override the default value
118and point it to the temporary tools location. The value of this variable
119specifies the linker's default library search path. This preparation
120is used later in the chapter.</para></listitem>
121</varlistentry>
122</variablelist>
123
124<warning><para><emphasis>Do not</emphasis> remove the Binutils
125build and source directories yet. These will be needed again in their
126current state later in this chapter.</para></warning>
127
128</sect2>
129
130<sect2 role="content"><title/>
131<para>Details on this package are located in <xref
132linkend="contents-binutils" role="."/></para>
133</sect2>
134
135</sect1>
136
Note: See TracBrowser for help on using the repository browser.