| 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-gcc-pass1" role="wrap" xreflabel="gcc-pass1">
|
|---|
| 9 | <?dbhtml filename="gcc-pass1.html"?>
|
|---|
| 10 |
|
|---|
| 11 | <sect1info condition="script">
|
|---|
| 12 | <productname>gcc-pass1</productname>
|
|---|
| 13 | <productnumber>&gcc-version;</productnumber>
|
|---|
| 14 | <address>&gcc-url;</address>
|
|---|
| 15 | </sect1info>
|
|---|
| 16 |
|
|---|
| 17 | <title>GCC-&gcc-version; - Pass 1</title>
|
|---|
| 18 |
|
|---|
| 19 | <indexterm zone="ch-tools-gcc-pass1">
|
|---|
| 20 | <primary sortas="a-GCC">GCC</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="../chapter08/gcc.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>&gcc-tmpp1-sbu;</seg>
|
|---|
| 37 | <seg>&gcc-tmpp1-du;</seg>
|
|---|
| 38 | </seglistitem>
|
|---|
| 39 | </segmentedlist>
|
|---|
| 40 |
|
|---|
| 41 | </sect2>
|
|---|
| 42 |
|
|---|
| 43 | <sect2 role="installation">
|
|---|
| 44 | <title>Installation of Cross GCC</title>
|
|---|
| 45 |
|
|---|
| 46 | <para>GCC requires the GMP, MPFR and MPC packages. As these packages may
|
|---|
| 47 | not be included in your host distribution, they will be built with
|
|---|
| 48 | GCC. Unpack each package into the GCC source directory and rename the
|
|---|
| 49 | resulting directories so the GCC build procedures will automatically
|
|---|
| 50 | use them:</para>
|
|---|
| 51 |
|
|---|
| 52 | <note><para>There are frequent misunderstandings about this chapter. The
|
|---|
| 53 | procedures are the same as every other chapter, as explained earlier (<xref
|
|---|
| 54 | linkend='buildinstr'/>). First, extract the gcc-&gcc-version; tarball from the sources
|
|---|
| 55 | directory, and then change to the directory created. Only then should you
|
|---|
| 56 | proceed with the instructions below.</para></note>
|
|---|
| 57 |
|
|---|
| 58 | <screen><userinput remap="pre">tar -xf ../mpfr-&mpfr-version;.tar.xz
|
|---|
| 59 | mv -v mpfr-&mpfr-version; mpfr
|
|---|
| 60 | tar -xf ../gmp-&gmp-version;.tar.xz
|
|---|
| 61 | mv -v gmp-&gmp-version; gmp
|
|---|
| 62 | tar -xf ../mpc-&mpc-version;.tar.gz
|
|---|
| 63 | mv -v mpc-&mpc-version; mpc</userinput></screen>
|
|---|
| 64 |
|
|---|
| 65 | <para>On ARM64 hosts, set the default directory name for
|
|---|
| 66 | 64-bit libraries to <quote>lib</quote>:</para>
|
|---|
| 67 |
|
|---|
| 68 | <screen><userinput remap="pre">sed -e '/lp64=/s/lib64/lib/' \
|
|---|
| 69 | -i.orig gcc/config/aarch64/t-aarch64-linux</userinput></screen>
|
|---|
| 70 |
|
|---|
| 71 | <para>The GCC documentation recommends building GCC
|
|---|
| 72 | in a dedicated build directory:</para>
|
|---|
| 73 |
|
|---|
| 74 | <screen><userinput remap="pre">mkdir -v build
|
|---|
| 75 | cd build</userinput></screen>
|
|---|
| 76 |
|
|---|
| 77 | <para>Prepare GCC for compilation:</para>
|
|---|
| 78 |
|
|---|
| 79 | <screen><userinput remap="configure">../configure \
|
|---|
| 80 | --target=$LFS_TGT \
|
|---|
| 81 | --prefix=$LFS/tools \
|
|---|
| 82 | --with-glibc-version=&glibc-version; \
|
|---|
| 83 | --with-sysroot=$LFS \
|
|---|
| 84 | --with-newlib \
|
|---|
| 85 | --without-headers \
|
|---|
| 86 | --enable-default-pie \
|
|---|
| 87 | --enable-default-ssp \
|
|---|
| 88 | --disable-nls \
|
|---|
| 89 | --disable-shared \
|
|---|
| 90 | --disable-multilib \
|
|---|
| 91 | --disable-decimal-float \
|
|---|
| 92 | --disable-threads \
|
|---|
| 93 | --disable-libatomic \
|
|---|
| 94 | --disable-libgomp \
|
|---|
| 95 | --disable-libquadmath \
|
|---|
| 96 | --disable-libssp \
|
|---|
| 97 | --disable-libvtv \
|
|---|
| 98 | --disable-libstdcxx \
|
|---|
| 99 | --enable-languages=c,c++</userinput></screen>
|
|---|
| 100 | <variablelist>
|
|---|
| 101 | <title>The meaning of the configure options:</title>
|
|---|
| 102 |
|
|---|
| 103 | <varlistentry>
|
|---|
| 104 | <term><parameter>--with-glibc-version=&glibc-version;</parameter></term>
|
|---|
| 105 | <listitem>
|
|---|
| 106 | <para>This option specifies the version of Glibc which will be
|
|---|
| 107 | used on the target. It is not relevant to the libc of the host
|
|---|
| 108 | distro because everything compiled by pass1 GCC will run in the
|
|---|
| 109 | chroot environment, which is isolated from libc of the host
|
|---|
| 110 | distro.</para>
|
|---|
| 111 | </listitem>
|
|---|
| 112 | </varlistentry>
|
|---|
| 113 |
|
|---|
| 114 | <varlistentry>
|
|---|
| 115 | <term><parameter>--with-newlib</parameter></term>
|
|---|
| 116 | <listitem>
|
|---|
| 117 | <para>Since a working C library is not yet available, this ensures
|
|---|
| 118 | that the inhibit_libc constant is defined when building libgcc. This prevents
|
|---|
| 119 | the compiling of any code that requires libc support.</para>
|
|---|
| 120 | </listitem>
|
|---|
| 121 | </varlistentry>
|
|---|
| 122 |
|
|---|
| 123 | <varlistentry>
|
|---|
| 124 | <term><parameter>--without-headers</parameter></term>
|
|---|
| 125 | <listitem>
|
|---|
| 126 | <para>When creating a complete cross-compiler, GCC requires
|
|---|
| 127 | standard headers compatible with the target system. For our
|
|---|
| 128 | purposes these headers will not be needed. This switch prevents
|
|---|
| 129 | GCC from looking for them.</para>
|
|---|
| 130 | </listitem>
|
|---|
| 131 | </varlistentry>
|
|---|
| 132 |
|
|---|
| 133 | <varlistentry>
|
|---|
| 134 | <term><parameter>--enable-default-pie and
|
|---|
| 135 | --enable-default-ssp</parameter></term>
|
|---|
| 136 | <listitem>
|
|---|
| 137 | <para>Those switches allow GCC to compile programs with
|
|---|
| 138 | some hardening security features (more information on those in
|
|---|
| 139 | the <xref linkend="pie-ssp-info"/> in chapter 8) by default. The
|
|---|
| 140 | are not strictly needed at this stage, since the compiler will
|
|---|
| 141 | only produce temporary executables. But it is cleaner to have the
|
|---|
| 142 | temporary packages be as close as possible to the final ones.
|
|---|
| 143 | </para>
|
|---|
| 144 | </listitem>
|
|---|
| 145 | </varlistentry>
|
|---|
| 146 |
|
|---|
| 147 | <varlistentry>
|
|---|
| 148 | <term><parameter>--disable-shared</parameter></term>
|
|---|
| 149 | <listitem>
|
|---|
| 150 | <para>This switch forces GCC to link its internal libraries
|
|---|
| 151 | statically. We need this because the shared libraries require Glibc,
|
|---|
| 152 | which is not yet installed on the target system.</para>
|
|---|
| 153 | </listitem>
|
|---|
| 154 | </varlistentry>
|
|---|
| 155 |
|
|---|
| 156 | <varlistentry>
|
|---|
| 157 | <term><parameter>--disable-multilib</parameter></term>
|
|---|
| 158 | <listitem>
|
|---|
| 159 | <para>On ARM64, LFS does not support a multilib configuration.</para>
|
|---|
| 160 | </listitem>
|
|---|
| 161 | </varlistentry>
|
|---|
| 162 |
|
|---|
| 163 | <varlistentry>
|
|---|
| 164 | <term><parameter>--disable-decimal-float, --disable-threads,
|
|---|
| 165 | --disable-libatomic, --disable-libgomp,
|
|---|
| 166 | --disable-libquadmath, --disable-libssp, --disable-libvtv,
|
|---|
| 167 | --disable-libstdcxx</parameter></term>
|
|---|
| 168 | <listitem>
|
|---|
| 169 | <para>These switches disable support for the decimal floating point
|
|---|
| 170 | extension, threading, libatomic, libgomp, libquadmath, libssp,
|
|---|
| 171 | libvtv, and the C++ standard library respectively. These features
|
|---|
| 172 | will fail to compile when building a cross-compiler and are not
|
|---|
| 173 | necessary for the task of cross-compiling the temporary libc.</para>
|
|---|
| 174 | </listitem>
|
|---|
| 175 | </varlistentry>
|
|---|
| 176 |
|
|---|
| 177 | <varlistentry>
|
|---|
| 178 | <term><parameter>--enable-languages=c,c++</parameter></term>
|
|---|
| 179 | <listitem>
|
|---|
| 180 | <para>This option ensures that only the C and C++ compilers are built.
|
|---|
| 181 | These are the only languages needed now.</para>
|
|---|
| 182 | </listitem>
|
|---|
| 183 | </varlistentry>
|
|---|
| 184 |
|
|---|
| 185 | </variablelist>
|
|---|
| 186 |
|
|---|
| 187 | <para>Compile GCC by running:</para>
|
|---|
| 188 |
|
|---|
| 189 | <screen><userinput remap="make">make</userinput></screen>
|
|---|
| 190 |
|
|---|
| 191 | <para>Install the package:</para>
|
|---|
| 192 |
|
|---|
| 193 | <screen><userinput remap="install">make install</userinput></screen>
|
|---|
| 194 |
|
|---|
| 195 | <para>This build of GCC has installed a couple of internal system
|
|---|
| 196 | headers. Normally one of them, <filename>limits.h</filename>, would in turn
|
|---|
| 197 | include the corresponding system <filename>limits.h</filename> header, in
|
|---|
| 198 | this case, <filename>$LFS/usr/include/limits.h</filename>. However, at the
|
|---|
| 199 | time of this build of GCC <filename>$LFS/usr/include/limits.h</filename>
|
|---|
| 200 | does not exist, so the internal header that has just been installed is a
|
|---|
| 201 | partial, self-contained file and does not include the extended features of
|
|---|
| 202 | the system header. This is adequate for building Glibc, but the full
|
|---|
| 203 | internal header will be needed later. Create a full version of the internal
|
|---|
| 204 | header using a command that is identical to what the GCC build system does
|
|---|
| 205 | in normal circumstances:</para>
|
|---|
| 206 |
|
|---|
| 207 | <screen><userinput remap="install">cd ..
|
|---|
| 208 | cat gcc/limitx.h gcc/glimits.h gcc/limity.h > \
|
|---|
| 209 | `dirname $($LFS_TGT-gcc -print-libgcc-file-name)`/install-tools/include/limits.h</userinput></screen>
|
|---|
| 210 | </sect2>
|
|---|
| 211 |
|
|---|
| 212 | <sect2 role="content">
|
|---|
| 213 | <title/>
|
|---|
| 214 |
|
|---|
| 215 | <para>Details on this package are located in
|
|---|
| 216 | <xref linkend="contents-gcc" role="."/></para>
|
|---|
| 217 |
|
|---|
| 218 | </sect2>
|
|---|
| 219 |
|
|---|
| 220 | </sect1>
|
|---|
