mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-01-18 04:57:38 +00:00
185 lines
6.4 KiB
XML
185 lines
6.4 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
|
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
|
<!ENTITY % general-entities SYSTEM "../general.ent">
|
|
%general-entities;
|
|
]>
|
|
|
|
<sect1 id="ch-tools-binutils-pass1" role="wrap" xreflabel="binutils-pass1">
|
|
<?dbhtml filename="binutils-pass1.html"?>
|
|
|
|
<sect1info condition="script">
|
|
<productname>binutils-pass1</productname>
|
|
<productnumber>&binutils-version;</productnumber>
|
|
<address>&binutils-url;</address>
|
|
</sect1info>
|
|
|
|
<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>
|
|
|
|
<sect2 role="package">
|
|
<title/>
|
|
|
|
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
href="../chapter08/binutils.xml"
|
|
xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
|
|
|
|
<segmentedlist>
|
|
<segtitle>&buildtime;</segtitle>
|
|
<segtitle>&diskspace;</segtitle>
|
|
|
|
<seglistitem>
|
|
<seg>&binutils-tmpp1-sbu;</seg>
|
|
<seg>&binutils-tmpp1-du;</seg>
|
|
</seglistitem>
|
|
</segmentedlist>
|
|
|
|
</sect2>
|
|
|
|
<sect2 role="installation">
|
|
<title>Installation of Cross Binutils</title>
|
|
|
|
<note><para>Go back and re-read the notes in the section titled <xref
|
|
linkend="ch-tools-generalinstructions"/>.
|
|
Understanding the notes labeled important can save you a lot
|
|
of problems later.</para></note>
|
|
|
|
<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
|
|
in a dedicated build directory:</para>
|
|
|
|
<screen><userinput remap="pre">mkdir -v build
|
|
cd 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 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>
|
|
|
|
<screen><userinput remap="configure">../configure --prefix=$LFS/tools \
|
|
--with-sysroot=$LFS \
|
|
--target=$LFS_TGT \
|
|
--disable-nls \
|
|
--enable-gprofng=no \
|
|
--disable-werror \
|
|
--enable-new-dtags \
|
|
--enable-default-hash-style=gnu</userinput></screen>
|
|
|
|
<variablelist>
|
|
<title>The meaning of the configure options:</title>
|
|
|
|
<varlistentry>
|
|
<term><parameter>--prefix=$LFS/tools</parameter></term>
|
|
<listitem>
|
|
<para>This tells the configure script to prepare to install the
|
|
Binutils programs in the <filename
|
|
class="directory">$LFS/tools</filename> directory.</para>
|
|
</listitem>
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
<term><parameter>--with-sysroot=$LFS</parameter></term>
|
|
<listitem>
|
|
<para>For cross compilation, this tells the build system to look in
|
|
$LFS for the target system libraries as needed.</para>
|
|
</listitem>
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
<term><envar>--target=$LFS_TGT</envar></term>
|
|
<listitem>
|
|
<para>Because the machine description in the <envar>LFS_TGT</envar>
|
|
variable is slightly different than the value returned by the
|
|
<command>config.guess</command> script, this switch will tell the
|
|
<command>configure</command> script to adjust binutil's build system
|
|
for building a cross linker. </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>--enable-gprofng=no</parameter></term>
|
|
<listitem>
|
|
<para>This disables building gprofng which is not needed for the
|
|
temporary tools.</para>
|
|
</listitem>
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
<term><parameter>--disable-werror</parameter></term>
|
|
<listitem>
|
|
<para>This prevents the build from stopping in the event that there
|
|
are warnings from the host's compiler.</para>
|
|
</listitem>
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
<term><parameter>--enable-new-dtags</parameter></term>
|
|
<listitem>
|
|
<para>This makes the linker use the <quote>runpath</quote> tag for
|
|
embedding library search paths into executables and shared libraries,
|
|
instead of the traditional <quote>rpath</quote> tag. It makes
|
|
debugging dynamically linked executables easier and works around
|
|
potential issues in the test suite of some packages.</para>
|
|
</listitem>
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
<term><parameter>--enable-default-hash-style=gnu</parameter></term>
|
|
<listitem>
|
|
<para>By default, the linker would generate both the GNU-style
|
|
hash table and the classic ELF hash table for shared libraries and
|
|
dynamically linked executables. The hash tables are only intended
|
|
for a dynamic linker to perform symbol lookup. On LFS the dynamic
|
|
linker (provided by the Glibc package) will always use the
|
|
GNU-style hash table which is faster to query. So the classic
|
|
ELF hash table is completely useless. This makes the linker
|
|
only generate the GNU-style hash table by default, so we can avoid
|
|
wasting time to generate the classic ELF hash table when we build
|
|
the packages, or wasting disk space to store it.</para>
|
|
</listitem>
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
|
|
|
<para>Continue with compiling the package:</para>
|
|
|
|
<screen><userinput remap="make">make</userinput></screen>
|
|
|
|
<para>Install the package:</para>
|
|
|
|
<screen><userinput remap="install">make install</userinput></screen>
|
|
|
|
</sect2>
|
|
|
|
<sect2 role="content">
|
|
<title/>
|
|
|
|
<para>Details on this package are located in
|
|
<xref linkend="contents-binutils" role="."/></para>
|
|
|
|
</sect2>
|
|
|
|
</sect1>
|