source: chapter05/binutils-pass1.xml@ dd30a4b

7.9-systemd 7.9-systemd-rc1 7.9-systemd-rc2 systemd
Last change on this file since dd30a4b was dd30a4b, checked in by DJ Lucas <dj@…>, 6 years ago

Merge from trunk r10991.

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

  • Property mode set to 100644
File size: 5.7 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../general.ent">
5 %general-entities;
6]>
7
8<sect1 id="ch-tools-binutils-pass1" role="wrap">
9 <?dbhtml filename="binutils-pass1.html"?>
10
11 <sect1info condition="script">
12 <productname>binutils</productname>
13 <productnumber>&binutils-version;</productnumber>
14 <address>&binutils-url;</address>
15 </sect1info>
16
17 <title>Binutils-&binutils-version; - Pass 1</title>
18
19 <indexterm zone="ch-tools-binutils-pass1">
20 <primary sortas="a-Binutils">Binutils</primary>
21 <secondary>tools, pass 1</secondary>
22 </indexterm>
23
24 <sect2 role="package">
25 <title/>
26
27 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
28 href="../chapter06/binutils.xml"
29 xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
30
31 <segmentedlist>
32 <segtitle>&buildtime;</segtitle>
33 <segtitle>&diskspace;</segtitle>
34
35 <seglistitem>
36 <seg>&binutils-ch5p1-sbu;</seg>
37 <seg>&binutils-ch5p1-du;</seg>
38 </seglistitem>
39 </segmentedlist>
40
41 </sect2>
42
43 <sect2 role="installation">
44 <title>Installation of Cross Binutils</title>
45
46 <note><para>Go back and re-read the notes in the previous section.
47 Understanding the notes labeled important will save you a lot
48 of problems later.</para></note>
49
50 <para>It is important that Binutils be the first package compiled
51 because both Glibc and GCC perform various tests on the available
52 linker and assembler to determine which of their own features to
53 enable.</para>
54
55 <para>The Binutils documentation recommends building Binutils
56 in a dedicated build directory:</para>
57
58<screen><userinput remap="pre">mkdir -v build
59cd build</userinput></screen>
60
61 <note>
62 <para>In order for the SBU values listed in the rest of the book
63 to be of any use, measure the time it takes to build this package from
64 the configuration, up to and including the first install. To achieve
65 this easily, wrap the commands in a <command>time</command>
66 command like this: <userinput>time { ./configure ... &amp;&amp; ...
67 &amp;&amp; make install; }</userinput>.</para>
68 </note>
69
70 <note><para>The approximate build SBU values and required disk space
71 in Chapter 5 does not include test suite data.</para></note>
72
73 <para>Now prepare Binutils for compilation:</para>
74
75<screen><userinput remap="configure">../configure --prefix=/tools \
76 --with-sysroot=$LFS \
77 --with-lib-path=/tools/lib \
78 --target=$LFS_TGT \
79 --disable-nls \
80 --disable-werror</userinput></screen>
81
82 <variablelist>
83 <title>The meaning of the configure options:</title>
84
85 <varlistentry>
86 <term><parameter>--prefix=/tools</parameter></term>
87 <listitem>
88 <para>This tells the configure script to prepare to install the
89 Binutils programs in the <filename class="directory">/tools</filename>
90 directory.</para>
91 </listitem>
92 </varlistentry>
93
94 <varlistentry>
95 <term><parameter>--with-sysroot=$LFS</parameter></term>
96 <listitem>
97 <para>For cross compilation, this tells the build system to look in
98 $LFS for the target system libraries as needed.</para>
99 </listitem>
100 </varlistentry>
101
102 <varlistentry>
103 <term><parameter>--with-lib-path=/tools/lib</parameter></term>
104 <listitem>
105 <para>This specifies which library path the linker should be
106 configured to use.</para>
107 </listitem>
108 </varlistentry>
109
110 <varlistentry>
111 <term><envar>--target=$LFS_TGT</envar></term>
112 <listitem>
113 <para>Because the machine description in the <envar>LFS_TGT</envar>
114 variable is slightly different than the value returned by the
115 <command>config.guess</command> script, this switch will tell the
116 <command>configure</command> script to adjust Binutil's build system
117 for building a cross linker. </para>
118 </listitem>
119 </varlistentry>
120
121 <varlistentry>
122 <term><parameter>--disable-nls</parameter></term>
123 <listitem>
124 <para>This disables internationalization as i18n is not needed for the
125 temporary tools.</para>
126 </listitem>
127 </varlistentry>
128
129 <varlistentry>
130 <term><parameter>--disable-werror</parameter></term>
131 <listitem>
132 <para>This prevents the build from stopping in the event that there
133 are warnings from the host's compiler.</para>
134 </listitem>
135 </varlistentry>
136
137 </variablelist>
138
139 <para>Continue with compiling the package:</para>
140
141<screen><userinput remap="make">make</userinput></screen>
142
143 <para>Compilation is now complete. Ordinarily we would now run the
144 test suite, but at this early stage the test suite framework (Tcl,
145 Expect, and DejaGNU) is not yet in place. The benefits of running the
146 tests at this point are minimal since the programs from this
147 first pass will soon be replaced by those from the second.</para>
148
149 <para>If building on x86_64, create a symlink to ensure the sanity of
150 the toolchain:</para>
151
152<screen><userinput remap="install">case $(uname -m) in
153 x86_64) mkdir -v /tools/lib &amp;&amp; ln -sv lib /tools/lib64 ;;
154esac</userinput></screen>
155
156 <para>Install the package:</para>
157
158<screen><userinput remap="install">make install</userinput></screen>
159
160 </sect2>
161
162 <sect2 role="content">
163 <title/>
164
165 <para>Details on this package are located in
166 <xref linkend="contents-binutils" role="."/></para>
167
168 </sect2>
169
170</sect1>
Note: See TracBrowser for help on using the repository browser.