diff options
Diffstat (limited to 'chapter05/binutils-pass1.xml')
| -rw-r--r-- | chapter05/binutils-pass1.xml | 201 |
1 files changed, 116 insertions, 85 deletions
diff --git a/chapter05/binutils-pass1.xml b/chapter05/binutils-pass1.xml index 5ce27d0b6..4435cfca0 100644 --- a/chapter05/binutils-pass1.xml +++ b/chapter05/binutils-pass1.xml @@ -1,122 +1,153 @@ <?xml version="1.0" encoding="ISO-8859-1"?> -<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [ +<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" + "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [ <!ENTITY % general-entities SYSTEM "../general.ent"> %general-entities; ]> + <sect1 id="ch-tools-binutils-pass1" role="wrap"> -<title>Binutils-&binutils-version; - Pass 1</title> -<?dbhtml filename="binutils-pass1.html"?> + <?dbhtml filename="binutils-pass1.html"?> + + <title>Binutils-&binutils-version; - Pass 1</title> + + <indexterm zone="ch-tools-binutils-pass1"> + <primary sortas="a-Binutils">Binutils</primary> + <secondary>tools, pass 1</secondary> + </indexterm> -<indexterm zone="ch-tools-binutils-pass1"> -<primary sortas="a-Binutils">Binutils</primary> -<secondary>tools, pass 1</secondary></indexterm> + <sect2 role="package"> + <title/> -<sect2 role="package"><title/> -<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="../chapter06/binutils.xml" xpointer="xpointer(/sect1/sect2[1]/para[1])"/> + <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" + href="../chapter06/binutils.xml" + xpointer="xpointer(/sect1/sect2[1]/para[1])"/> -<segmentedlist> -<segtitle>&buildtime;</segtitle> -<segtitle>&diskspace;</segtitle> -<seglistitem><seg>1.0 SBU</seg><seg>170 MB</seg></seglistitem> -</segmentedlist> + <segmentedlist> + <segtitle>&buildtime;</segtitle> + <segtitle>&diskspace;</segtitle> -<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="../chapter06/binutils.xml" xpointer="xpointer(/sect1/sect2[1]/segmentedlist[2])"/> + <seglistitem> + <seg>1.0 SBU</seg> + <seg>170 MB</seg> + </seglistitem> + </segmentedlist> -</sect2> + <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" + href="../chapter06/binutils.xml" + xpointer="xpointer(/sect1/sect2[1]/segmentedlist[2])"/> -<sect2 role="installation"> -<title>Installation of Binutils</title> + </sect2> -<para>It is important that Binutils be the first package compiled -because both Glibc and GCC perform various tests on the available -linker and assembler to determine which of their own features to -enable.</para> + <sect2 role="installation"> + <title>Installation of Binutils</title> -<para>The Binutils documentation recommends building Binutils outside of the -source directory in a dedicated build directory:</para> + <para>It is important that Binutils be the first package compiled + because both Glibc and GCC perform various tests on the available + linker and assembler to determine which of their own features to + enable.</para> + + <para>The Binutils documentation recommends building Binutils outside of the + source directory in a dedicated build directory:</para> <screen><userinput>mkdir -v ../binutils-build cd ../binutils-build</userinput></screen> -<note><para>In order for the SBU values listed in the rest of the book -to be of any use, measure the time it takes to build this package from -the configuration, up to and including the first install. To achieve -this easily, wrap the three commands in a <command>time</command> -command like this: <userinput>time { ./configure ... && make -&& make install; }</userinput>.</para></note> + <note> + <para>In order for the SBU values listed in the rest of the book + to be of any use, measure the time it takes to build this package from + the configuration, up to and including the first install. To achieve + this easily, wrap the three commands in a <command>time</command> + command like this: <userinput>time { ./configure ... && make + && make install; }</userinput>.</para> + </note> -<para>Now prepare Binutils for compilation:</para> + <para>Now prepare Binutils for compilation:</para> <screen><userinput>../binutils-&binutils-version;/configure --prefix=/tools --disable-nls</userinput></screen> -<para>The meaning of the configure options:</para> + <variablelist> + <title>The meaning of the configure options:</title> + + <varlistentry> + <term><parameter>--prefix=/tools</parameter></term> + <listitem> + <para>This tells the configure script to prepare to install the + Binutils programs in the <filename class="directory">/tools</filename> + directory.</para> + </listitem> + </varlistentry> -<variablelist> -<varlistentry> -<term><parameter>--prefix=/tools</parameter></term> -<listitem><para>This tells the configure script to prepare to install the Binutils -programs in the <filename class="directory">/tools</filename> directory.</para></listitem> -</varlistentry> + <varlistentry> + <term><parameter>--disable-nls</parameter></term> + <listitem> + <para>This disables internationalization as i18n is not needed for the + temporary tools.</para> + </listitem> + </varlistentry> -<varlistentry> -<term><parameter>--disable-nls</parameter></term> -<listitem><para>This disables internationalization as i18n is not needed for the -temporary tools.</para></listitem> -</varlistentry> -</variablelist> + </variablelist> -<para>Continue with compiling the package:</para> + <para>Continue with compiling the package:</para> <screen><userinput>make</userinput></screen> -<para>Compilation is now complete. Ordinarily we would now run the -test suite, but at this early stage the test suite framework (Tcl, -Expect, and DejaGNU) is not yet in place. The benefits of running the -tests at this point are minimal since the programs from this -first pass will soon be replaced by those from the second.</para> + <para>Compilation is now complete. Ordinarily we would now run the + test suite, but at this early stage the test suite framework (Tcl, + Expect, and DejaGNU) is not yet in place. The benefits of running the + tests at this point are minimal since the programs from this + first pass will soon be replaced by those from the second.</para> -<para>Install the package:</para> + <para>Install the package:</para> <screen><userinput>make install</userinput></screen> -<para>Next, prepare the linker for the <quote>Adjusting</quote> phase -later on:</para> + <para>Next, prepare the linker for the <quote>Adjusting</quote> phase + later on:</para> <screen><userinput>make -C ld clean make -C ld LIB_PATH=/tools/lib</userinput></screen> -<para>The meaning of the make parameters:</para> - -<variablelist> -<varlistentry> -<term><parameter>-C ld clean</parameter></term> -<listitem><para>This tells the make program to remove all compiled -files in the <filename class="directory">ld</filename> -subdirectory.</para></listitem> -</varlistentry> - -<varlistentry> -<term><parameter>-C ld LIB_PATH=/tools/lib</parameter></term> -<listitem><para>This option rebuilds everything in the -<filename class="directory">ld</filename> subdirectory. Specifying -the <envar>LIB_PATH</envar> Makefile variable on the command -line allows us to override the default value -and point it to the temporary tools location. The value of this variable -specifies the linker's default library search path. This preparation -is used later in the chapter.</para></listitem> -</varlistentry> -</variablelist> - -<warning><para><emphasis>Do not</emphasis> remove the Binutils -build and source directories yet. These will be needed again in their -current state later in this chapter.</para></warning> - -</sect2> - -<sect2 role="content"><title/> -<para>Details on this package are located in <xref -linkend="contents-binutils" role="."/></para> -</sect2> + <variablelist> + <title>The meaning of the make parameters:</title> + + <varlistentry> + <term><parameter>-C ld clean</parameter></term> + <listitem> + <para>This tells the make program to remove all compiled + files in the <filename class="directory">ld</filename> + subdirectory.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><parameter>-C ld LIB_PATH=/tools/lib</parameter></term> + <listitem> + <para>This option rebuilds everything in the <filename + class="directory">ld</filename> subdirectory. Specifying the + <envar>LIB_PATH</envar> Makefile variable on the command line + allows us to override the default value and point it to the + temporary tools location. The value of this variable specifies + the linker's default library search path. This preparation is + used later in the chapter.</para> + </listitem> + </varlistentry> + + </variablelist> + + <warning> + <para><emphasis>Do not</emphasis> remove the Binutils build and source + directories yet. These will be needed again in their current state later + in this chapter.</para> + </warning> + + </sect2> + + <sect2 role="content"> + <title/> + + <para>Details on this package are located in + <xref linkend="contents-binutils" role="."/></para> + + </sect2> </sect1> - |