[673b0d8] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
|
---|
| 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 |
|
---|
[673b0d8] | 10 | <indexterm zone="ch-tools-gcc-pass1">
|
---|
| 11 | <primary sortas="a-GCC">GCC</primary>
|
---|
| 12 | <secondary>tools, pass 1</secondary></indexterm>
|
---|
[bc82645e] | 13 |
|
---|
[9652249] | 14 | <sect2 role="package"><title/>
|
---|
| 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 |
|
---|
[9652249] | 23 | <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="../chapter06/gcc.xml" xpointer="xpointer(/sect1/sect2[1]/segmentedlist[2])"/>
|
---|
[73aedd1d] | 24 |
|
---|
[9652249] | 25 | </sect2>
|
---|
[73aedd1d] | 26 |
|
---|
[9652249] | 27 | <sect2 role="installation">
|
---|
[73aedd1d] | 28 | <title>Installation of GCC</title>
|
---|
| 29 |
|
---|
[6e41459] | 30 | <para>Unpack only the gcc-core tarball because neither the C++
|
---|
| 31 | compiler nor the test suite will be needed here.</para>
|
---|
[73aedd1d] | 32 |
|
---|
[6e41459] | 33 | <para>This package is known to have issues when the default
|
---|
[574b0ea] | 34 | optimization flags (including the <parameter>-march</parameter> and
|
---|
[6e41459] | 35 | <parameter>-mcpu</parameter> options) are changed. Therefore, if any
|
---|
| 36 | environment variables that override default optimizations have been
|
---|
| 37 | defined, such as <emphasis>CFLAGS</emphasis> and
|
---|
| 38 | <emphasis>CXXFLAGS</emphasis>, we recommend un-setting them when
|
---|
| 39 | building GCC.</para>
|
---|
[73aedd1d] | 40 |
|
---|
[6e41459] | 41 | <para>The GCC documentation recommends building GCC outside of the
|
---|
| 42 | source directory in a dedicated build directory:</para>
|
---|
[73aedd1d] | 43 |
|
---|
| 44 | <screen><userinput>mkdir ../gcc-build
|
---|
| 45 | cd ../gcc-build</userinput></screen>
|
---|
| 46 |
|
---|
[d27a27b] | 47 | <para>Prepare GCC for compilation:</para>
|
---|
[73aedd1d] | 48 |
|
---|
[673b0d8] | 49 | <screen><userinput>../gcc-&gcc-version;/configure --prefix=/tools \
|
---|
[9dfc02f] | 50 | --libexecdir=/tools/lib --with-local-prefix=/tools \
|
---|
| 51 | --disable-nls --enable-shared --enable-languages=c</userinput></screen>
|
---|
[73aedd1d] | 52 |
|
---|
| 53 | <para>The meaning of the configure options:</para>
|
---|
| 54 |
|
---|
[9652249] | 55 | <variablelist>
|
---|
| 56 | <varlistentry>
|
---|
[574b0ea] | 57 | <term><parameter>--with-local-prefix=/tools</parameter></term>
|
---|
| 58 | <listitem><para>The purpose of this switch is to remove <filename class="directory">/usr/local/include</filename>
|
---|
[90e3cb3] | 59 | from <command>gcc</command>'s include search path. This is not absolutely
|
---|
[6e41459] | 60 | essential, however, this helps to minimize the influence of the host
|
---|
| 61 | system.</para></listitem>
|
---|
[9652249] | 62 | </varlistentry>
|
---|
[73aedd1d] | 63 |
|
---|
[9652249] | 64 | <varlistentry>
|
---|
[574b0ea] | 65 | <term><parameter>--enable-shared</parameter></term>
|
---|
[6e41459] | 66 | <listitem><para>This switch may seem counter-intuitive at first.
|
---|
| 67 | However, this switch allows the building of
|
---|
| 68 | <filename>libgcc_s.so.1</filename> and
|
---|
| 69 | <filename>libgcc_eh.a</filename>, and having
|
---|
| 70 | <filename>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 | as this is controlled by the <parameter>-static</parameter> value of
|
---|
| 74 | the <emphasis>BOOT_LDFLAGS</emphasis> variable in the next
|
---|
| 75 | step.</para></listitem>
|
---|
[9652249] | 76 | </varlistentry>
|
---|
[73aedd1d] | 77 |
|
---|
[9652249] | 78 | <varlistentry>
|
---|
[574b0ea] | 79 | <term><parameter>--enable-languages=c</parameter></term>
|
---|
[9652249] | 80 | <listitem><para>This option
|
---|
[6e41459] | 81 | ensures that only the C compiler is built. This option is only needed when you
|
---|
| 82 | have downloaded and unpacked the full GCC tarball, as opposed to just
|
---|
| 83 | having unpacked the gcc-core tarball.</para></listitem>
|
---|
[9652249] | 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 |
|
---|
| 91 | <para>The meaning of the make parameters:</para>
|
---|
| 92 |
|
---|
[9652249] | 93 | <variablelist>
|
---|
| 94 | <varlistentry>
|
---|
[574b0ea] | 95 | <term><parameter>BOOT_LDFLAGS="-static"</parameter></term>
|
---|
[9652249] | 96 | <listitem><para>This tells GCC to link its programs statically.</para></listitem>
|
---|
| 97 | </varlistentry>
|
---|
[73aedd1d] | 98 |
|
---|
[9652249] | 99 | <varlistentry>
|
---|
[574b0ea] | 100 | <term><parameter>bootstrap</parameter></term>
|
---|
[6e41459] | 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>
|
---|
[9652249] | 107 | </varlistentry>
|
---|
| 108 | </variablelist>
|
---|
[73aedd1d] | 109 |
|
---|
[6e41459] | 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 | would be minimal since the programs from this first pass will soon be
|
---|
| 114 | replaced.</para>
|
---|
[443cace] | 115 |
|
---|
[6e41459] | 116 | <para>Install the package:</para>
|
---|
[73aedd1d] | 117 |
|
---|
| 118 | <screen><userinput>make install</userinput></screen>
|
---|
| 119 |
|
---|
[6e41459] | 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 what C compiler to install.</para>
|
---|
[73aedd1d] | 125 |
|
---|
[51fe215] | 126 | <screen><userinput>ln -s gcc /tools/bin/cc</userinput></screen>
|
---|
[73aedd1d] | 127 |
|
---|
| 128 | </sect2>
|
---|
[bc82645e] | 129 |
|
---|
[9652249] | 130 | <sect2 role="content"><title/>
|
---|
[5888299] | 131 | <para>The details on this package are found in <xref linkend="contents-gcc"/>.</para>
|
---|
[0868461] | 132 | </sect2>
|
---|
[5888299] | 133 |
|
---|
[bc82645e] | 134 | </sect1>
|
---|
[6e41459] | 135 |
|
---|