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 | ]>
|
---|
6 | <sect1 id="ch-tools-gcc-pass1" role="wrap">
|
---|
7 | <title>GCC-&gcc-version; - Pass 1</title>
|
---|
8 | <?dbhtml filename="gcc-pass1.html"?>
|
---|
9 |
|
---|
10 | <indexterm zone="ch-tools-gcc-pass1">
|
---|
11 | <primary sortas="a-GCC">GCC</primary>
|
---|
12 | <secondary>tools, pass 1</secondary></indexterm>
|
---|
13 |
|
---|
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])"/>
|
---|
16 |
|
---|
17 | <segmentedlist>
|
---|
18 | <segtitle>&buildtime;</segtitle>
|
---|
19 | <segtitle>&diskspace;</segtitle>
|
---|
20 | <seglistitem><seg>4.4 SBU</seg><seg>300 MB</seg></seglistitem>
|
---|
21 | </segmentedlist>
|
---|
22 |
|
---|
23 | <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="../chapter06/gcc.xml" xpointer="xpointer(/sect1/sect2[1]/segmentedlist[2])"/>
|
---|
24 |
|
---|
25 | </sect2>
|
---|
26 |
|
---|
27 | <sect2 role="installation">
|
---|
28 | <title>Installation of GCC</title>
|
---|
29 |
|
---|
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 <emphasis>CFLAGS</emphasis> and <emphasis>CXXFLAGS</emphasis>,
|
---|
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>
|
---|
42 |
|
---|
43 | <screen><userinput>mkdir ../gcc-build
|
---|
44 | cd ../gcc-build</userinput></screen>
|
---|
45 |
|
---|
46 | <para>Prepare GCC for compilation:</para>
|
---|
47 |
|
---|
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, this helps to minimize the influence of the host
|
---|
60 | system.</para></listitem>
|
---|
61 | </varlistentry>
|
---|
62 |
|
---|
63 | <varlistentry>
|
---|
64 | <term><parameter>--enable-shared</parameter></term>
|
---|
65 | <listitem><para>This switch may seem counter-intuitive at first.
|
---|
66 | However, this switch allows the building of
|
---|
67 | <filename>libgcc_s.so.1</filename> and
|
---|
68 | <filename>libgcc_eh.a</filename>, and having
|
---|
69 | <filename>libgcc_eh.a</filename> available ensures that the configure
|
---|
70 | script for Glibc (the next package we compile) produces the proper
|
---|
71 | results. Note that the GCC binaries will still be linked statically,
|
---|
72 | as this is controlled by the <parameter>-static</parameter> value of
|
---|
73 | the <emphasis>BOOT_LDFLAGS</emphasis> variable in the next
|
---|
74 | step.</para></listitem>
|
---|
75 | </varlistentry>
|
---|
76 |
|
---|
77 | <varlistentry>
|
---|
78 | <term><parameter>--enable-languages=c</parameter></term>
|
---|
79 | <listitem><para>This option
|
---|
80 | ensures that only the C compiler is built. This option is only needed when you
|
---|
81 | have downloaded and unpacked the full GCC tarball, as opposed to just
|
---|
82 | having unpacked the gcc-core tarball.</para></listitem>
|
---|
83 | </varlistentry>
|
---|
84 | </variablelist>
|
---|
85 |
|
---|
86 | <para>Continue with compiling the package:</para>
|
---|
87 |
|
---|
88 | <screen><userinput>make BOOT_LDFLAGS="-static" bootstrap</userinput></screen>
|
---|
89 |
|
---|
90 | <para>The meaning of the make parameters:</para>
|
---|
91 |
|
---|
92 | <variablelist>
|
---|
93 | <varlistentry>
|
---|
94 | <term><parameter>BOOT_LDFLAGS="-static"</parameter></term>
|
---|
95 | <listitem><para>This tells GCC to link its programs statically.</para></listitem>
|
---|
96 | </varlistentry>
|
---|
97 |
|
---|
98 | <varlistentry>
|
---|
99 | <term><parameter>bootstrap</parameter></term>
|
---|
100 | <listitem><para>This target does not just compile GCC, but compiles it
|
---|
101 | several times. It uses the programs compiled in a first round to
|
---|
102 | compile itself a second time, and then again a third time. It then
|
---|
103 | compares these second and third compiles to make sure it can reproduce
|
---|
104 | itself flawlessly. This also implies that it was compiled
|
---|
105 | correctly.</para></listitem>
|
---|
106 | </varlistentry>
|
---|
107 | </variablelist>
|
---|
108 |
|
---|
109 | <para>Compilation is now complete. At this point, the test suite would
|
---|
110 | normally be run, but, as mentioned before, the test suite framework is
|
---|
111 | not in place yet. The benefits of running the tests at this point
|
---|
112 | would be minimal since the programs from this first pass will soon be
|
---|
113 | replaced.</para>
|
---|
114 |
|
---|
115 | <para>Install the package:</para>
|
---|
116 |
|
---|
117 | <screen><userinput>make install</userinput></screen>
|
---|
118 |
|
---|
119 | <para>As a finishing touch, create a symlink. Many programs and
|
---|
120 | scripts run <command>cc</command> instead of <command>gcc</command>, which is used to keep programs generic
|
---|
121 | and therefore usable on all kinds of UNIX systems where the GNU C compiler
|
---|
122 | is not always installed. Running <command>cc</command> leaves the system administrator
|
---|
123 | free to decide what C compiler to install.</para>
|
---|
124 |
|
---|
125 | <screen><userinput>ln -s gcc /tools/bin/cc</userinput></screen>
|
---|
126 |
|
---|
127 | </sect2>
|
---|
128 |
|
---|
129 | <sect2 role="content"><title/>
|
---|
130 | <para>The details on this package are found in <xref linkend="contents-gcc"/>.</para>
|
---|
131 | </sect2>
|
---|
132 |
|
---|
133 | </sect1>
|
---|
134 |
|
---|