[673b0d8] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
[1770019] | 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
---|
[673b0d8] | 3 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
| 4 | %general-entities;
|
---|
| 5 | ]>
|
---|
[9652249] | 6 | <sect1 id="ch-tools-gcc-pass1" role="wrap">
|
---|
[673b0d8] | 7 | <title>GCC-&gcc-version; - Pass 1</title>
|
---|
| 8 | <?dbhtml filename="gcc-pass1.html"?>
|
---|
[bc82645e] | 9 |
|
---|
[81fd230] | 10 | <indexterm zone="ch-tools-gcc-pass1">
|
---|
| 11 | <primary sortas="a-GCC">GCC</primary>
|
---|
| 12 | <secondary>tools, pass 1</secondary></indexterm>
|
---|
| 13 |
|
---|
[9652249] | 14 | <sect2 role="package"><title/>
|
---|
[81fd230] | 15 | <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="../chapter06/gcc.xml" xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
|
---|
[5888299] | 16 |
|
---|
[9652249] | 17 | <segmentedlist>
|
---|
| 18 | <segtitle>&buildtime;</segtitle>
|
---|
| 19 | <segtitle>&diskspace;</segtitle>
|
---|
| 20 | <seglistitem><seg>4.4 SBU</seg><seg>300 MB</seg></seglistitem>
|
---|
| 21 | </segmentedlist>
|
---|
[673b0d8] | 22 |
|
---|
[81fd230] | 23 | <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="../chapter06/gcc.xml" xpointer="xpointer(/sect1/sect2[1]/segmentedlist[2])"/>
|
---|
| 24 |
|
---|
[9652249] | 25 | </sect2>
|
---|
[73aedd1d] | 26 |
|
---|
[9652249] | 27 | <sect2 role="installation">
|
---|
[73aedd1d] | 28 | <title>Installation of GCC</title>
|
---|
| 29 |
|
---|
[81fd230] | 30 | <para>Unpack only the gcc-core tarball because neither the C++
|
---|
| 31 | compiler nor the test suite will be needed here.</para>
|
---|
| 32 |
|
---|
| 33 | <para>This package is known to have issues when its default
|
---|
| 34 | optimization flags (including the <parameter>-march</parameter> and
|
---|
| 35 | <parameter>-mcpu</parameter> options) are changed. If any environment
|
---|
| 36 | variables that override default optimizations have been defined, such
|
---|
| 37 | as <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar>,
|
---|
| 38 | unset them when building GCC.</para>
|
---|
| 39 |
|
---|
| 40 | <para>The GCC documentation recommends building GCC outside of the
|
---|
| 41 | source directory in a dedicated build directory:</para>
|
---|
[3d36131c] | 42 |
|
---|
[73aedd1d] | 43 | <screen><userinput>mkdir ../gcc-build
|
---|
| 44 | cd ../gcc-build</userinput></screen>
|
---|
| 45 |
|
---|
[d27a27b] | 46 | <para>Prepare GCC for compilation:</para>
|
---|
[73aedd1d] | 47 |
|
---|
[81fd230] | 48 | <screen><userinput>../gcc-&gcc-version;/configure --prefix=/tools \
|
---|
| 49 | --libexecdir=/tools/lib --with-local-prefix=/tools \
|
---|
| 50 | --disable-nls --enable-shared --enable-languages=c</userinput></screen>
|
---|
| 51 |
|
---|
| 52 | <para>The meaning of the configure options:</para>
|
---|
| 53 |
|
---|
| 54 | <variablelist>
|
---|
| 55 | <varlistentry>
|
---|
| 56 | <term><parameter>--with-local-prefix=/tools</parameter></term>
|
---|
| 57 | <listitem><para>The purpose of this switch is to remove <filename class="directory">/usr/local/include</filename>
|
---|
| 58 | from <command>gcc</command>'s include search path. This is not absolutely
|
---|
| 59 | essential, however, it helps to minimize the influence of the host
|
---|
| 60 | system.</para>
|
---|
| 61 | </listitem>
|
---|
| 62 | </varlistentry>
|
---|
| 63 |
|
---|
| 64 | <varlistentry>
|
---|
| 65 | <term><parameter>--enable-shared</parameter></term>
|
---|
| 66 | <listitem><para>This switch may seem counter-intuitive at first.
|
---|
| 67 | However, this switch allows the building of
|
---|
| 68 | <filename class="libraryfile">libgcc_s.so.1</filename> and
|
---|
| 69 | <filename class="libraryfile">libgcc_eh.a</filename>, and having
|
---|
| 70 | <filename class="libraryfile">libgcc_eh.a</filename> available ensures that the configure
|
---|
| 71 | script for Glibc (the next package we compile) produces the proper
|
---|
| 72 | results. Note that the GCC binaries will still be linked statically
|
---|
| 73 | because this is controlled by the <parameter>-static</parameter> value of
|
---|
| 74 | the <envar>BOOT_LDFLAGS</envar> variable in the next
|
---|
| 75 | step.</para></listitem>
|
---|
| 76 | </varlistentry>
|
---|
| 77 |
|
---|
| 78 | <varlistentry>
|
---|
| 79 | <term><parameter>--enable-languages=c</parameter></term>
|
---|
| 80 | <listitem><para>This option ensures that only the C compiler is built.
|
---|
| 81 | This option is only needed when you have downloaded and unpacked the
|
---|
| 82 | full GCC tarball, as opposed to just the gcc-core
|
---|
| 83 | tarball.</para></listitem>
|
---|
| 84 | </varlistentry>
|
---|
| 85 | </variablelist>
|
---|
[73aedd1d] | 86 |
|
---|
| 87 | <para>Continue with compiling the package:</para>
|
---|
| 88 |
|
---|
| 89 | <screen><userinput>make BOOT_LDFLAGS="-static" bootstrap</userinput></screen>
|
---|
| 90 |
|
---|
[81fd230] | 91 | <para>The meaning of the make parameters:</para>
|
---|
| 92 |
|
---|
| 93 | <variablelist>
|
---|
| 94 | <varlistentry>
|
---|
| 95 | <term><parameter>BOOT_LDFLAGS="-static"</parameter></term>
|
---|
| 96 | <listitem><para>This tells GCC to link its programs statically.</para></listitem>
|
---|
| 97 | </varlistentry>
|
---|
| 98 |
|
---|
| 99 | <varlistentry>
|
---|
| 100 | <term><parameter>bootstrap</parameter></term>
|
---|
| 101 | <listitem><para>This target does not just compile GCC, but compiles it
|
---|
| 102 | several times. It uses the programs compiled in a first round to
|
---|
| 103 | compile itself a second time, and then again a third time. It then
|
---|
| 104 | compares these second and third compiles to make sure it can reproduce
|
---|
| 105 | itself flawlessly. This also implies that it was compiled
|
---|
| 106 | correctly.</para></listitem>
|
---|
| 107 | </varlistentry>
|
---|
| 108 | </variablelist>
|
---|
| 109 |
|
---|
| 110 | <para>Compilation is now complete. At this point, the test suite would
|
---|
| 111 | normally be run, but, as mentioned before, the test suite framework is
|
---|
| 112 | not in place yet. The benefits of running the tests at this point
|
---|
| 113 | are minimal since the programs from this first pass will soon be
|
---|
| 114 | replaced.</para>
|
---|
| 115 |
|
---|
| 116 | <para>Install the package:</para>
|
---|
[73aedd1d] | 117 |
|
---|
| 118 | <screen><userinput>make install</userinput></screen>
|
---|
| 119 |
|
---|
[81fd230] | 120 | <para>As a finishing touch, create a symlink. Many programs and
|
---|
| 121 | scripts run <command>cc</command> instead of <command>gcc</command>, which is used to keep programs generic
|
---|
| 122 | and therefore usable on all kinds of UNIX systems where the GNU C compiler
|
---|
| 123 | is not always installed. Running <command>cc</command> leaves the system administrator
|
---|
| 124 | free to decide which C compiler to install.</para>
|
---|
[3d36131c] | 125 |
|
---|
[51fe215] | 126 | <screen><userinput>ln -s gcc /tools/bin/cc</userinput></screen>
|
---|
[73aedd1d] | 127 |
|
---|
| 128 | </sect2>
|
---|
[bc82645e] | 129 |
|
---|
[81fd230] | 130 | <sect2 role="content"><title/>
|
---|
| 131 | <para>Details on this package are located in <xref
|
---|
| 132 | linkend="contents-gcc" role="."/></para>
|
---|
| 133 | </sect2>
|
---|
| 134 |
|
---|
[bc82645e] | 135 | </sect1>
|
---|
[81fd230] | 136 |
|
---|