Gitiles
Code Review Sign In
gerrit-public.fairphone.software / fp2-dev / platform / external / llvm / c856c7aea67c7a68454129336e173f388f42373c / . / docs / CFEBuildInstrs.html
blob: 033edcc1f2089292b0e16e9dfdc394726c77abca [file] [log] [blame]
Misha Brukman6a2b3102004-05-12 18:49:47 +0000[diff] [blame]1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
Misha Brukman83bd33a2003-10-23 01:48:33 +0000[diff] [blame]3<html>
4<head>
Misha Brukman6a2b3102004-05-12 18:49:47 +0000[diff] [blame]5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
6 <link rel="stylesheet" href="llvm.css" type="text/css" media="screen">
Misha Brukmanb9e57892003-10-28 21:09:29 +0000[diff] [blame]7 <title>Bootstrapping the LLVM C/C++ Front-End</title>
Misha Brukman83bd33a2003-10-23 01:48:33 +0000[diff] [blame]8</head>
9<body>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]10
Misha Brukman83bd33a2003-10-23 01:48:33 +0000[diff] [blame]11<div class="doc_title">
Misha Brukmanb9e57892003-10-28 21:09:29 +0000[diff] [blame]12 Bootstrapping the LLVM C/C++ Front-End
Misha Brukman83bd33a2003-10-23 01:48:33 +0000[diff] [blame]13</div>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]14
Brian Gaeke7af03e92003-11-12 20:47:30 +0000[diff] [blame]15<ol>
16 <li><a href="#cautionarynote">A Cautionary Note</a>
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]17 <ul>
Misha Brukman62a93432004-06-18 15:54:54 +0000[diff] [blame]18 <li><a href="#cygwin">Building under Cygwin</a></li>
Misha Brukman03ea9d42004-08-23 17:54:45 +0000[diff] [blame]19 <li><a href="#aix">Building under AIX</a></li>
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]20 </ul>
21 </li>
Chris Lattner810ad8c2006-07-11 20:47:00 +0000[diff] [blame]22 <li><a href="#instructions">llvm-gcc4 Instructions</a></li>
23 <li><a href="#llvm-gcc3-instructions">llvm-gcc3 Instructions</a></li>
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]24 <li><a href="#license">License Information</a></li>
Brian Gaeke7af03e92003-11-12 20:47:30 +0000[diff] [blame]25</ol>
26
Chris Lattner7911ce22004-05-23 21:07:27 +0000[diff] [blame]27<div class="doc_author">
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]28 <p>Written by Brian R. Gaeke and
29 <a href="http://nondot.org/sabre">Chris Lattner</a></p>
Brian Gaeke7af03e92003-11-12 20:47:30 +0000[diff] [blame]30</div>
31
32<!-- *********************************************************************** -->
33<div class="doc_section">
34 <a name="cautionarynote">A Cautionary Note</a>
35</div>
36<!-- *********************************************************************** -->
37
38<div class="doc_text">
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]39
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]40<p>This document is intended to explain the process of building the LLVM C/C++
41front-end from its source code. You have to do this, for example, if you are
42porting LLVM to a new architecture or operating system, if you are working from
43Top-Of-Tree CVS/SVN, or if there is no precompiled snapshot available.</p>
44
45<p><b>NOTE:</b> This is currently a somewhat fragile, error-prone process, and
46you should <b>only</b> try to do it if:</p>
Misha Brukmanb9e57892003-10-28 21:09:29 +0000[diff] [blame]47
48<ol>
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]49 <li>you really, <em>really</em>, <b><em>really</em></b> can't use the
50 binaries we distribute</li>
Misha Brukmanb9e57892003-10-28 21:09:29 +0000[diff] [blame]51 <li>you are an elite GCC hacker.</li>
Chris Lattnerc8118e12005-02-21 16:35:31 +0000[diff] [blame]52 <li>you want to use the latest bits from CVS.</li>
Misha Brukmanb9e57892003-10-28 21:09:29 +0000[diff] [blame]53</ol>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]54
55<p>We welcome patches to help make this process simpler.</p>
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]56
Brian Gaeke7af03e92003-11-12 20:47:30 +0000[diff] [blame]57</div>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]58
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]59<!--=========================================================================-->
60<div class="doc_subsection">
Misha Brukman62a93432004-06-18 15:54:54 +0000[diff] [blame]61 <a name="cygwin">Building under Cygwin</a>
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]62</div>
63<!--=========================================================================-->
64
65<div class="doc_text">
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]66
John Criswell9e2485c2004-12-10 15:51:16 +0000[diff] [blame]67<p>If you are building LLVM and the GCC front-end under Cygwin, please note that
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]68the LLVM and GCC makefiles do not correctly handle spaces in paths. To deal
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]69with this issue, make sure that your LLVM and GCC source and build trees are
70located in a top-level directory (like <tt>/cygdrive/c/llvm</tt> and
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]71<tt>/cygdrive/c/llvm-cfrontend</tt>), not in a directory that contains a space
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]72(which includes your "home directory", because it lives under the "Documents and
73Settings" directory). We welcome patches to fix this issue.</p>
74
Reid Spencer24042362004-12-22 09:52:30 +0000[diff] [blame]75<p>It has been found that the GCC 3.3.3 compiler provided with recent Cygwin
John Criswelld6c6ee02005-10-24 16:37:24 +0000[diff] [blame]76versions is incapable of compiling the LLVM GCC front-end correctly. If your
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]77Cygwin installation includes GCC 3.3.3, we <em>strongly</em> recommend that you
78download GCC 3.4.3, build it separately, and use it for compiling the LLVM GCC
79front-end. This has been shown to work correctly.</p>
80
Reid Spencer72a59002004-12-23 19:49:54 +0000[diff] [blame]81<p>Some versions of Cygwin utilize an experimental version of GNU binutils that
82will cause the GNU <tt>ld</tt> linker to fail an assertion when linking
83components of the libstdc++. It is recommended that you replace the entire
84binutils package with version 2.15 such that "<tt>ld --version</tt>" responds
Misha Brukman00b95c32005-03-01 17:19:21 +0000[diff] [blame]85with</p>
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]86
87<div class="doc_code">
Reid Spencer72a59002004-12-23 19:49:54 +0000[diff] [blame]88<pre>GNU ld version 2.15</pre>
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]89</div>
90
91<p>not with:</p>
92
93<div class="doc_code">
Reid Spencer72a59002004-12-23 19:49:54 +0000[diff] [blame]94<pre>GNU ld version 2.15.91 20040725</pre>
Misha Brukman00b95c32005-03-01 17:19:21 +0000[diff] [blame]95</div>
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]96
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]97</div>
98
Misha Brukman03ea9d42004-08-23 17:54:45 +0000[diff] [blame]99<!--=========================================================================-->
Reid Spencere0a7ddd2004-12-31 19:48:59 +0000[diff] [blame]100<div class="doc_subsection"><a name="aix">Building under AIX</a></div>
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]101
Misha Brukman03ea9d42004-08-23 17:54:45 +0000[diff] [blame]102<div class="doc_text">
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]103
John Criswell9e2485c2004-12-10 15:51:16 +0000[diff] [blame]104<p>If you are building LLVM and the GCC front-end under AIX, do NOT use GNU
Misha Brukman03ea9d42004-08-23 17:54:45 +0000[diff] [blame]105Binutils. They are not stable under AIX and may produce incorrect and/or
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]106invalid code. Instead, use the system assembler and linker.</p>
107
Misha Brukman03ea9d42004-08-23 17:54:45 +0000[diff] [blame]108</div>
109
Misha Brukman83bd33a2003-10-23 01:48:33 +0000[diff] [blame]110<!-- *********************************************************************** -->
111<div class="doc_section">
Chris Lattner810ad8c2006-07-11 20:47:00 +0000[diff] [blame]112 <a name="instructions">llvm-gcc4 Instructions</a>
Misha Brukman83bd33a2003-10-23 01:48:33 +0000[diff] [blame]113</div>
114<!-- *********************************************************************** -->
115
116<div class="doc_text">
Chris Lattner810ad8c2006-07-11 20:47:00 +0000[diff] [blame]117
118<p>This section describes how to aquire and build llvm-gcc4, which is based on
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]119the GCC 4.0.1 front-end. This front-end supports C, C++, Objective-C, and
Chris Lattner810ad8c2006-07-11 20:47:00 +0000[diff] [blame]120Objective-C++. Note that the instructions for building this front-end are
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]121completely different than those for building llvm-gcc3.</p>
Chris Lattner810ad8c2006-07-11 20:47:00 +0000[diff] [blame]122
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]123<ol>
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]124 <li><p>Retrieve the appropriate llvm-gcc4-x.y.source.tar.gz archive from the
125 llvm web site.</p>
Jim Laskeye9493d32006-06-16 23:34:49 +0000[diff] [blame]126
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]127 <p>It is also possible to download the sources of the llvm-gcc4 front end
128 from a read-only mirror using subversion. To check out the code the
129 first time use:</p>
Jim Laskeye9493d32006-06-16 23:34:49 +0000[diff] [blame]130
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]131<div class="doc_code">
132<pre>
133svn co svn://anonsvn.opensource.apple.com/svn/llvm/trunk <i>dst-directory</i>
134</pre>
135</div>
Jim Laskeye9493d32006-06-16 23:34:49 +0000[diff] [blame]136
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]137 <p>After that, the code can be be updated in the destination directory
138 using:</p>
Jim Laskeye9493d32006-06-16 23:34:49 +0000[diff] [blame]139
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]140<div class="doc_code">
141<pre>svn update</pre>
142</div>
Chris Lattner810ad8c2006-07-11 20:47:00 +0000[diff] [blame]143
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]144 <p>The mirror is brought up to date every evening.</p></li>
145
146 <li>Follow the directions in the top-level <tt>README.LLVM</tt> file for
147 up-to-date instructions on how to build llvm-gcc4.</li>
Chris Lattner810ad8c2006-07-11 20:47:00 +0000[diff] [blame]148</ol>
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]149
Chris Lattner810ad8c2006-07-11 20:47:00 +0000[diff] [blame]150</div>
151
152<!-- *********************************************************************** -->
153<div class="doc_section">
154 <a name="llvm-gcc3-instructions">llvm-gcc3 Instructions</a>
155</div>
156<!-- *********************************************************************** -->
157
158<div class="doc_text">
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]159
Chris Lattner810ad8c2006-07-11 20:47:00 +0000[diff] [blame]160<ol>
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]161 <li>Aquire llvm-gcc3 from <a href="GettingStarted.html#checkout">LLVM CVS</a>
162 or from a <a href="http://llvm.org/releases/">release tarball</a>.</li>
Chris Lattner810ad8c2006-07-11 20:47:00 +0000[diff] [blame]163
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]164 <li><p>Configure and build the LLVM libraries and tools. There are two ways to
165 do this: either with <tt><i>objdir</i> == <i>srcdir</i></tt> or
166 <tt><i>objdir</i> != <i>srcdir</i></tt>. It is recommended that
167 <tt><i>srcdir</i></tt> be the same as <tt><i>objdir</i></tt> for your
168 LLVM tree (but note that you should always use <tt><i>srcdir</i> !=
169 <i>objdir</i></tt> for llvm-gcc):</p>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]170
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]171 <ul>
172 <li><p>With <tt><i>objdir</i> != <i>srcdir</i></tt>:</p>
173
174<div class="doc_code">
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]175<pre>
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]176% cd <i>objdir</i>
177% <i>srcdir</i>/configure --prefix=/some/path/you/can/install/to [options...]
178% gmake tools-only
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]179</pre>
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]180</div>
181 </li>
182 <li><p>With <tt><i>objdir</i> == <i>srcdir</i></tt>:</p>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]183
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]184<div class="doc_code">
Chris Lattner893c26a2004-06-02 19:27:50 +0000[diff] [blame]185<pre>
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]186% cd llvm
187% ./configure --prefix=/some/path/you/can/install/to [options...]
188% gmake tools-only
Chris Lattner893c26a2004-06-02 19:27:50 +0000[diff] [blame]189</pre>
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]190</div>
191 </li>
192 </ul>
Chris Lattner893c26a2004-06-02 19:27:50 +0000[diff] [blame]193
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]194 <p>This will build all of the LLVM tools and libraries. The
195 <tt>--prefix</tt> option defaults to <tt>/usr/local</tt> (per configure
196 standards) but unless you are a system administrator, you probably
197 won't be able to install LLVM there because of permissions. Specify a
198 path into which LLVM can be installed
199 (e.g. <tt>--prefix=/home/user/llvm</tt>).</p></li>
200 <li><p>Add the directory containing the tools to your PATH.</p>
John Criswell55072842003-12-08 19:59:14 +0000[diff] [blame]201
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]202<div class="doc_code">
203csh:
John Criswell55072842003-12-08 19:59:14 +0000[diff] [blame]204<pre>
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]205 % set path = ( `cd llvm/Debug/bin &amp;&amp; pwd` $path )
John Criswell55072842003-12-08 19:59:14 +0000[diff] [blame]206</pre>
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]207sh:
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]208<pre>
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]209 % export PATH=`cd llvm/Debug/bin &amp;&amp; pwd`:$PATH
Reid Spencerf99e59a2004-11-25 17:13:17 +0000[diff] [blame]210</pre>
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]211</div>
212 </li>
Reid Spencerf99e59a2004-11-25 17:13:17 +0000[diff] [blame]213
Tanya Lattnerc9aee642006-11-20 05:52:06 +0000[diff] [blame]214 <li><p>Unpack the C/C++ front-end source, either by
215 untar'ing/unzipping a tar.gz file or checking out CVS into this
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]216 directory.</p></li>
217 <li><p>Make "build" and "install" directories as siblings of the "src"
218 tree:</p>
219
220<div class="doc_code">
221csh:
222<pre>
223 % pwd
Tanya Lattnerc9aee642006-11-20 05:52:06 +0000[diff] [blame]224 /usr/local/example/llvm-gcc3.4/src
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]225 % cd ..
226 % mkdir build install
227 % set CFEINSTALL = `pwd`/install
228</pre>
229sh:
230<pre>
231 % pwd
Tanya Lattnerc9aee642006-11-20 05:52:06 +0000[diff] [blame]232 /usr/local/example/llvm-gcc3.4/src
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]233 % cd ..
234 % mkdir build install
235 % export CFEINSTALL=`pwd`/install
236</pre>
237</div>
238 </li>
239
240 <li><p>Configure, build, and install the GCC front-end:</p>
241
242 <p>
243 <b>Linux/x86:</b><br>
244 <b>Linux/IA-64:</b><br>
245 <b>MacOS X/PowerPC</b> (requires dlcompat library):<br>
246 <b>AIX/PowerPC:</b>
247 </p>
248
249<div class="doc_code">
250<pre>
251% cd build
252% ../src/configure --prefix=$CFEINSTALL --disable-threads --disable-nls \
253 --disable-shared --enable-languages=c,c++ --program-prefix=llvm-
254% gmake all; gmake install
255</pre>
256</div>
257
258 <p><b>Cygwin/x86:</b></p>
259
260<div class="doc_code">
261<pre>
262% cd build
263% ../src/configure --prefix=$CFEINSTALL --disable-threads --disable-nls \
264 --disable-shared --enable-languages=c,c++ --disable-c-mbchar \
265 --program-prefix=llvm-
266% gmake all; gmake install
267</pre>
268</div>
269
270 <p><b>Solaris/SPARC:</b></p>
271
272 <p>The GCC front-end can be configured for either SPARC V8 (32 bit) or
273 SPARC V9 (64 bit). This changes, among other things, the sizes of
274 integer types and the macros defined for conditional compilation.</p>
275
276 <p>The SPARC V8 ABI support is more robust than the V9 ABI support and can
277 generate SPARC V9 code. It is highly recommended that you use the V8
278 ABI with LLVM, as shown below. Also, note that Solaris has trouble
279 with various wide (multibyte) character functions from C as referenced
280 from C++, so we typically configure with --disable-c-mbchar (cf. <a
281 href="http://llvm.org/PR206">Bug 206</a>).</p>
282
283<div class="doc_code">
284<pre>
285% cd build
286% ../src/configure --prefix=$CFEINSTALL --disable-threads --disable-nls \
287 --disable-shared --enable-languages=c,c++ --host=sparc-sun-solaris2.8 \
288 --disable-c-mbchar --program-prefix=llvm-
289% gmake all; gmake install
290</pre>
291</div>
292
293 <p><b>Common Problem:</b> You may get error messages regarding the fact
294 that LLVM does not support inline assembly. Here are two common
295 fixes:</p>
296
297 <ul>
298 <li><p><b>Fix 1:</b> If you have system header files that include inline
299 assembly, you may have to modify them to remove the inline assembly
300 and install the modified versions in
301 <code>$CFEINSTALL/lib/gcc/<i>target-triplet</i>/3.4-llvm/include</code>.</li>
302
303 <li><b>Fix 2:</b> If you are building the C++ front-end on a CPU we
304 haven't tried yet, you will probably have to edit the appropriate
305 version of atomicity.h under
306 <code>src/libstdc++-v3/config/cpu/<i>name-of-cpu</i>/atomicity.h</code>
307 and apply a patch so that it does not use inline assembly.</li>
308 </ul>
309
310 <p><b>Porting to a new architecture:</b> If you are porting the front-end
311 to a new architecture or compiling in a configuration that we have not
312 tried previously, there are probably several changes you will have to
313 make to the GCC target to get it to work correctly. These include:</p>
314
315 <ul>
316 <li>Often targets include special assembler or linker flags which
Reid Spencer434262a2007-02-09 15:59:08 +0000[diff] [blame]317 <tt>llvm-as</tt>, <tt>opt</tt>, or <tt>llvm-ld</tt> do not
318 understand. In general, these can just be removed.</li>
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]319
320 <li>LLVM currently does not support any floating point values other than
321 32-bit and 64-bit IEEE floating point. The primary effect of this
322 is that you may have to map "long double" onto "double".</li>
323
324 <li>The profiling hooks in GCC do not apply at all to the LLVM
325 front-end. These may need to be disabled.</li>
326
327 <li>No inline assembly for position independent code. At the LLVM
328 level, everything is position independent.</li>
329
330 <li>We handle <tt>.init</tt> and <tt>.fini</tt> differently.</li>
331
332 <li>You may have to disable multilib support in your target. Using
333 multilib support causes the GCC compiler driver to add a lot of
Reid Spencer434262a2007-02-09 15:59:08 +0000[diff] [blame]334 "<tt>-L</tt>" options to the link line, which do not relate to
335 LLVM. To disable multilibs, delete any
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]336 <tt>MULTILIB_OPTIONS</tt> lines from your target files.</li>
337
338 <li>Did we mention that we don't support inline assembly? You'll
339 probably have to add some fixinclude hacks to disable it in the
340 system headers.</li>
341 </ul></li>
342
343 <li><p>Put <tt>$CFEINSTALL/bin</tt> into your <tt>PATH</tt> environment
344 variable.</p>
345
346<div class="doc_code">
347csh:
348<pre>
349 % setenv PATH $CFEINSTALL/bin:$PATH
350</pre>
351sh:
352<pre>
353 % export PATH=$CFEINSTALL/bin:$PATH
354</pre>
355</div>
356 </li>
357
358 <li><p>Go back into the LLVM source tree proper. Rerun configure, using the
359 same options as the last time. This will cause the configuration to now
360 find the newly built llvm-gcc and llvm-g++ executables. </p></li>
361
362 <li><p>Rebuild your CVS tree. This shouldn't cause the whole thing to be
363 rebuilt, but it should build the runtime libraries. After the tree is
364 built, install the runtime libraries into your GCC front-end build tree.
365 These are the commands you need:</p>
366
367<div class="doc_code">
368<pre>
369% gmake
370% gmake -C runtime install-bytecode
371</pre>
372</div>
373 </li>
374
375 <li><p>Optionally, build a symbol table for the newly installed runtime
376 libraries. Although this step is optional, you are strongly encouraged to
377 do this as the symbol tables will make a significant difference in your
378 link times. Use the <tt>llvm-ranlib</tt> tool to do this, as follows:</p>
379
380<div class="doc_code">
381<pre>
382% cd $CFEINSTALL/lib
383% llvm-ranlib libiberty.a
384% llvm-ranlib libstdc++.a
385% llvm-ranlib libsupc++.a
386% cd $CFEINSTALL/lib/gcc/<i>target-triplet</i>/3.4-llvm
387% llvm-ranlib libgcc.a
388% llvm-ranlib libgcov.a
389</pre>
390</div>
391 </li>
392
393 <li><p>Test the newly-installed C frontend by one or more of the following
394 means:</p>
395
396 <ul>
397 <li>running the feature &amp; regression tests via <tt>make
398 check</tt></li>
399 <li>compiling and running a "hello, LLVM" program in C and C++.</li>
400 <li>running the tests found in the <tt>llvm-test</tt> CVS module</li>
401 </ul></li>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]402</ol>
Bill Wendling0ca558f2006-11-16 09:31:19 +0000[diff] [blame]403
Misha Brukman83bd33a2003-10-23 01:48:33 +0000[diff] [blame]404</div>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]405
406<!-- *********************************************************************** -->
John Criswelld000e1d2003-12-18 16:43:17 +0000[diff] [blame]407<div class="doc_section">
408 <a name="license">License Information</a>
409</div>
410
411<div class="doc_text">
412<p>
413The LLVM GCC frontend is licensed to you under the GNU General Public License
414and the GNU Lesser General Public License. Please see the files COPYING and
415COPYING.LIB for more details.
416</p>
417
418<p>
Chris Lattner810ad8c2006-07-11 20:47:00 +0000[diff] [blame]419More information is <a href="FAQ.html#license">available in the FAQ</a>.
John Criswelld000e1d2003-12-18 16:43:17 +0000[diff] [blame]420</p>
John Criswelld000e1d2003-12-18 16:43:17 +0000[diff] [blame]421</pre>
422</div>
423
424<!-- *********************************************************************** -->
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]425
Misha Brukmanb9e57892003-10-28 21:09:29 +0000[diff] [blame]426<hr>
Misha Brukman6a2b3102004-05-12 18:49:47 +0000[diff] [blame]427<address>
428 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
429 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
430 <a href="http://validator.w3.org/check/referer"><img
431 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!"></a>
432
433 Brian Gaeke<br>
Reid Spencer05fe4b02006-03-14 05:39:39 +0000[diff] [blame]434 <a href="http://llvm.org">LLVM Compiler Infrastructure</a><br>
Misha Brukmanb9e57892003-10-28 21:09:29 +0000[diff] [blame]435 Last modified: $Date$
Misha Brukman6a2b3102004-05-12 18:49:47 +0000[diff] [blame]436</address>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]437
Misha Brukman83bd33a2003-10-23 01:48:33 +0000[diff] [blame]438</body>
439</html>