Mercurial > hg > CbC > CbC_gcc
annotate INSTALL/configure.html @ 19:58ad6c70ea60
update gcc from 4.4.0 to 4.4.1.
author | kent@firefly.cr.ie.u-ryukyu.ac.jp |
---|---|
date | Thu, 24 Sep 2009 13:21:57 +0900 |
parents | a06113de4d67 |
children |
rev | line source |
---|---|
0 | 1 <html lang="en"> |
2 <head> | |
3 <title>Installing GCC: Configuration</title> | |
4 <meta http-equiv="Content-Type" content="text/html"> | |
5 <meta name="description" content="Installing GCC: Configuration"> | |
19
58ad6c70ea60
update gcc from 4.4.0 to 4.4.1.
kent@firefly.cr.ie.u-ryukyu.ac.jp
parents:
0
diff
changeset
|
6 <meta name="generator" content="makeinfo 4.13"> |
0 | 7 <link title="Top" rel="top" href="#Top"> |
8 <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage"> | |
9 <!-- | |
10 Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, | |
11 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, | |
12 2008 Free Software Foundation, Inc. | |
13 | |
14 Permission is granted to copy, distribute and/or modify this document | |
15 under the terms of the GNU Free Documentation License, Version 1.2 or | |
16 any later version published by the Free Software Foundation; with no | |
17 Invariant Sections, the Front-Cover texts being (a) (see below), and | |
18 with the Back-Cover Texts being (b) (see below). A copy of the | |
19 license is included in the section entitled "GNU Free Documentation License". | |
20 | |
21 (a) The FSF's Front-Cover Text is: | |
22 | |
23 A GNU Manual | |
24 | |
25 (b) The FSF's Back-Cover Text is: | |
26 | |
27 You have freedom to copy and modify this GNU Manual, like GNU | |
28 software. Copies published by the Free Software Foundation raise | |
29 funds for GNU development.--> | |
30 <meta http-equiv="Content-Style-Type" content="text/css"> | |
31 <style type="text/css"><!-- | |
32 pre.display { font-family:inherit } | |
33 pre.format { font-family:inherit } | |
34 pre.smalldisplay { font-family:inherit; font-size:smaller } | |
35 pre.smallformat { font-family:inherit; font-size:smaller } | |
36 pre.smallexample { font-size:smaller } | |
37 pre.smalllisp { font-size:smaller } | |
38 span.sc { font-variant:small-caps } | |
39 span.roman { font-family:serif; font-weight:normal; } | |
40 span.sansserif { font-family:sans-serif; font-weight:normal; } | |
41 --></style> | |
42 </head> | |
43 <body> | |
44 <h1 class="settitle">Installing GCC: Configuration</h1> | |
45 <a name="index-Configuration-1"></a><a name="index-Installing-GCC_003a-Configuration-2"></a> | |
46 Like most GNU software, GCC must be configured before it can be built. | |
47 This document describes the recommended configuration procedure | |
48 for both native and cross targets. | |
49 | |
50 <p>We use <var>srcdir</var> to refer to the toplevel source directory for | |
51 GCC; we use <var>objdir</var> to refer to the toplevel build/object directory. | |
52 | |
53 <p>If you obtained the sources via SVN, <var>srcdir</var> must refer to the top | |
54 <samp><span class="file">gcc</span></samp> directory, the one where the <samp><span class="file">MAINTAINERS</span></samp> can be found, | |
55 and not its <samp><span class="file">gcc</span></samp> subdirectory, otherwise the build will fail. | |
56 | |
57 <p>If either <var>srcdir</var> or <var>objdir</var> is located on an automounted NFS | |
58 file system, the shell's built-in <samp><span class="command">pwd</span></samp> command will return | |
59 temporary pathnames. Using these can lead to various sorts of build | |
60 problems. To avoid this issue, set the <samp><span class="env">PWDCMD</span></samp> environment | |
61 variable to an automounter-aware <samp><span class="command">pwd</span></samp> command, e.g., | |
62 <samp><span class="command">pawd</span></samp> or ‘<samp><span class="samp">amq -w</span></samp>’, during the configuration and build | |
63 phases. | |
64 | |
65 <p>First, we <strong>highly</strong> recommend that GCC be built into a | |
66 separate directory than the sources which does <strong>not</strong> reside | |
67 within the source tree. This is how we generally build GCC; building | |
68 where <var>srcdir</var> == <var>objdir</var> should still work, but doesn't | |
69 get extensive testing; building where <var>objdir</var> is a subdirectory | |
70 of <var>srcdir</var> is unsupported. | |
71 | |
72 <p>If you have previously built GCC in the same directory for a | |
73 different target machine, do ‘<samp><span class="samp">make distclean</span></samp>’ to delete all files | |
74 that might be invalid. One of the files this deletes is <samp><span class="file">Makefile</span></samp>; | |
75 if ‘<samp><span class="samp">make distclean</span></samp>’ complains that <samp><span class="file">Makefile</span></samp> does not exist | |
76 or issues a message like “don't know how to make distclean” it probably | |
77 means that the directory is already suitably clean. However, with the | |
78 recommended method of building in a separate <var>objdir</var>, you should | |
79 simply use a different <var>objdir</var> for each target. | |
80 | |
81 <p>Second, when configuring a native system, either <samp><span class="command">cc</span></samp> or | |
82 <samp><span class="command">gcc</span></samp> must be in your path or you must set <samp><span class="env">CC</span></samp> in | |
83 your environment before running configure. Otherwise the configuration | |
84 scripts may fail. | |
85 | |
86 <p>To configure GCC: | |
87 | |
88 <pre class="smallexample"> % mkdir <var>objdir</var> | |
89 % cd <var>objdir</var> | |
90 % <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>] | |
91 </pre> | |
92 <h3 class="heading"><a name="TOC0"></a>Distributor options</h3> | |
93 | |
94 <p>If you will be distributing binary versions of GCC, with modifications | |
95 to the source code, you should use the options described in this | |
96 section to make clear that your version contains modifications. | |
97 | |
98 <dl> | |
99 <dt><code>--with-pkgversion=</code><var>version</var><dd>Specify a string that identifies your package. You may wish | |
100 to include a build number or build date. This version string will be | |
101 included in the output of <samp><span class="command">gcc --version</span></samp>. This suffix does | |
102 not replace the default version string, only the ‘<samp><span class="samp">GCC</span></samp>’ part. | |
103 | |
104 <p>The default value is ‘<samp><span class="samp">GCC</span></samp>’. | |
105 | |
106 <br><dt><code>--with-bugurl=</code><var>url</var><dd>Specify the URL that users should visit if they wish to report a bug. | |
107 You are of course welcome to forward bugs reported to you to the FSF, | |
108 if you determine that they are not bugs in your modifications. | |
109 | |
110 <p>The default value refers to the FSF's GCC bug tracker. | |
111 | |
112 </dl> | |
113 | |
114 <h3 class="heading"><a name="TOC1"></a>Target specification</h3> | |
115 | |
116 <ul> | |
117 <li>GCC has code to correctly determine the correct value for <var>target</var> | |
118 for nearly all native systems. Therefore, we highly recommend you not | |
119 provide a configure target when configuring a native compiler. | |
120 | |
121 <li><var>target</var> must be specified as <samp><span class="option">--target=</span><var>target</var></samp> | |
122 when configuring a cross compiler; examples of valid targets would be | |
123 m68k-coff, sh-elf, etc. | |
124 | |
125 <li>Specifying just <var>target</var> instead of <samp><span class="option">--target=</span><var>target</var></samp> | |
126 implies that the host defaults to <var>target</var>. | |
127 </ul> | |
128 | |
129 <h3 class="heading"><a name="TOC2"></a>Options specification</h3> | |
130 | |
131 <p>Use <var>options</var> to override several configure time options for | |
132 GCC. A list of supported <var>options</var> follows; ‘<samp><span class="samp">configure | |
133 --help</span></samp>’ may list other options, but those not listed below may not | |
134 work and should not normally be used. | |
135 | |
136 <p>Note that each <samp><span class="option">--enable</span></samp> option has a corresponding | |
137 <samp><span class="option">--disable</span></samp> option and that each <samp><span class="option">--with</span></samp> option has a | |
138 corresponding <samp><span class="option">--without</span></samp> option. | |
139 | |
140 <dl> | |
141 <dt><code>--prefix=</code><var>dirname</var><dd>Specify the toplevel installation | |
142 directory. This is the recommended way to install the tools into a directory | |
143 other than the default. The toplevel installation directory defaults to | |
144 <samp><span class="file">/usr/local</span></samp>. | |
145 | |
146 <p>We <strong>highly</strong> recommend against <var>dirname</var> being the same or a | |
147 subdirectory of <var>objdir</var> or vice versa. If specifying a directory | |
148 beneath a user's home directory tree, some shells will not expand | |
149 <var>dirname</var> correctly if it contains the ‘<samp><span class="samp">~</span></samp>’ metacharacter; use | |
150 <samp><span class="env">$HOME</span></samp> instead. | |
151 | |
152 <p>The following standard <samp><span class="command">autoconf</span></samp> options are supported. Normally you | |
153 should not need to use these options. | |
154 <dl> | |
155 <dt><code>--exec-prefix=</code><var>dirname</var><dd>Specify the toplevel installation directory for architecture-dependent | |
156 files. The default is <samp><var>prefix</var></samp>. | |
157 | |
158 <br><dt><code>--bindir=</code><var>dirname</var><dd>Specify the installation directory for the executables called by users | |
159 (such as <samp><span class="command">gcc</span></samp> and <samp><span class="command">g++</span></samp>). The default is | |
160 <samp><var>exec-prefix</var><span class="file">/bin</span></samp>. | |
161 | |
162 <br><dt><code>--libdir=</code><var>dirname</var><dd>Specify the installation directory for object code libraries and | |
163 internal data files of GCC. The default is <samp><var>exec-prefix</var><span class="file">/lib</span></samp>. | |
164 | |
165 <br><dt><code>--libexecdir=</code><var>dirname</var><dd>Specify the installation directory for internal executables of GCC. | |
166 The default is <samp><var>exec-prefix</var><span class="file">/libexec</span></samp>. | |
167 | |
168 <br><dt><code>--with-slibdir=</code><var>dirname</var><dd>Specify the installation directory for the shared libgcc library. The | |
169 default is <samp><var>libdir</var></samp>. | |
170 | |
171 <br><dt><code>--infodir=</code><var>dirname</var><dd>Specify the installation directory for documentation in info format. | |
172 The default is <samp><var>prefix</var><span class="file">/info</span></samp>. | |
173 | |
174 <br><dt><code>--datadir=</code><var>dirname</var><dd>Specify the installation directory for some architecture-independent | |
175 data files referenced by GCC. The default is <samp><var>prefix</var><span class="file">/share</span></samp>. | |
176 | |
177 <br><dt><code>--mandir=</code><var>dirname</var><dd>Specify the installation directory for manual pages. The default is | |
178 <samp><var>prefix</var><span class="file">/man</span></samp>. (Note that the manual pages are only extracts from | |
179 the full GCC manuals, which are provided in Texinfo format. The manpages | |
180 are derived by an automatic conversion process from parts of the full | |
181 manual.) | |
182 | |
183 <br><dt><code>--with-gxx-include-dir=</code><var>dirname</var><dd>Specify | |
184 the installation directory for G++ header files. The default is | |
185 <samp><var>prefix</var><span class="file">/include/c++/</span><var>version</var></samp>. | |
186 | |
187 </dl> | |
188 | |
189 <br><dt><code>--program-prefix=</code><var>prefix</var><dd>GCC supports some transformations of the names of its programs when | |
190 installing them. This option prepends <var>prefix</var> to the names of | |
191 programs to install in <var>bindir</var> (see above). For example, specifying | |
192 <samp><span class="option">--program-prefix=foo-</span></samp> would result in ‘<samp><span class="samp">gcc</span></samp>’ | |
193 being installed as <samp><span class="file">/usr/local/bin/foo-gcc</span></samp>. | |
194 | |
195 <br><dt><code>--program-suffix=</code><var>suffix</var><dd>Appends <var>suffix</var> to the names of programs to install in <var>bindir</var> | |
196 (see above). For example, specifying <samp><span class="option">--program-suffix=-3.1</span></samp> | |
197 would result in ‘<samp><span class="samp">gcc</span></samp>’ being installed as | |
198 <samp><span class="file">/usr/local/bin/gcc-3.1</span></samp>. | |
199 | |
200 <br><dt><code>--program-transform-name=</code><var>pattern</var><dd>Applies the ‘<samp><span class="samp">sed</span></samp>’ script <var>pattern</var> to be applied to the names | |
201 of programs to install in <var>bindir</var> (see above). <var>pattern</var> has to | |
202 consist of one or more basic ‘<samp><span class="samp">sed</span></samp>’ editing commands, separated by | |
203 semicolons. For example, if you want the ‘<samp><span class="samp">gcc</span></samp>’ program name to be | |
204 transformed to the installed program <samp><span class="file">/usr/local/bin/myowngcc</span></samp> and | |
205 the ‘<samp><span class="samp">g++</span></samp>’ program name to be transformed to | |
206 <samp><span class="file">/usr/local/bin/gspecial++</span></samp> without changing other program names, | |
207 you could use the pattern | |
208 <samp><span class="option">--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'</span></samp> | |
209 to achieve this effect. | |
210 | |
211 <p>All three options can be combined and used together, resulting in more | |
212 complex conversion patterns. As a basic rule, <var>prefix</var> (and | |
213 <var>suffix</var>) are prepended (appended) before further transformations | |
214 can happen with a special transformation script <var>pattern</var>. | |
215 | |
216 <p>As currently implemented, this option only takes effect for native | |
217 builds; cross compiler binaries' names are not transformed even when a | |
218 transformation is explicitly asked for by one of these options. | |
219 | |
220 <p>For native builds, some of the installed programs are also installed | |
221 with the target alias in front of their name, as in | |
222 ‘<samp><span class="samp">i686-pc-linux-gnu-gcc</span></samp>’. All of the above transformations happen | |
223 before the target alias is prepended to the name—so, specifying | |
224 <samp><span class="option">--program-prefix=foo-</span></samp> and <samp><span class="option">program-suffix=-3.1</span></samp>, the | |
225 resulting binary would be installed as | |
226 <samp><span class="file">/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1</span></samp>. | |
227 | |
228 <p>As a last shortcoming, none of the installed Ada programs are | |
229 transformed yet, which will be fixed in some time. | |
230 | |
231 <br><dt><code>--with-local-prefix=</code><var>dirname</var><dd>Specify the | |
232 installation directory for local include files. The default is | |
233 <samp><span class="file">/usr/local</span></samp>. Specify this option if you want the compiler to | |
234 search directory <samp><var>dirname</var><span class="file">/include</span></samp> for locally installed | |
235 header files <em>instead</em> of <samp><span class="file">/usr/local/include</span></samp>. | |
236 | |
237 <p>You should specify <samp><span class="option">--with-local-prefix</span></samp> <strong>only</strong> if your | |
238 site has a different convention (not <samp><span class="file">/usr/local</span></samp>) for where to put | |
239 site-specific files. | |
240 | |
241 <p>The default value for <samp><span class="option">--with-local-prefix</span></samp> is <samp><span class="file">/usr/local</span></samp> | |
242 regardless of the value of <samp><span class="option">--prefix</span></samp>. Specifying | |
243 <samp><span class="option">--prefix</span></samp> has no effect on which directory GCC searches for | |
244 local header files. This may seem counterintuitive, but actually it is | |
245 logical. | |
246 | |
247 <p>The purpose of <samp><span class="option">--prefix</span></samp> is to specify where to <em>install | |
248 GCC</em>. The local header files in <samp><span class="file">/usr/local/include</span></samp>—if you put | |
249 any in that directory—are not part of GCC. They are part of other | |
250 programs—perhaps many others. (GCC installs its own header files in | |
251 another directory which is based on the <samp><span class="option">--prefix</span></samp> value.) | |
252 | |
253 <p>Both the local-prefix include directory and the GCC-prefix include | |
254 directory are part of GCC's “system include” directories. Although these | |
255 two directories are not fixed, they need to be searched in the proper | |
256 order for the correct processing of the include_next directive. The | |
257 local-prefix include directory is searched before the GCC-prefix | |
258 include directory. Another characteristic of system include directories | |
259 is that pedantic warnings are turned off for headers in these directories. | |
260 | |
261 <p>Some autoconf macros add <samp><span class="option">-I </span><var>directory</var></samp> options to the | |
262 compiler command line, to ensure that directories containing installed | |
263 packages' headers are searched. When <var>directory</var> is one of GCC's | |
264 system include directories, GCC will ignore the option so that system | |
265 directories continue to be processed in the correct order. This | |
266 may result in a search order different from what was specified but the | |
267 directory will still be searched. | |
268 | |
269 <p>GCC automatically searches for ordinary libraries using | |
270 <samp><span class="env">GCC_EXEC_PREFIX</span></samp>. Thus, when the same installation prefix is | |
271 used for both GCC and packages, GCC will automatically search for | |
272 both headers and libraries. This provides a configuration that is | |
273 easy to use. GCC behaves in a manner similar to that when it is | |
274 installed as a system compiler in <samp><span class="file">/usr</span></samp>. | |
275 | |
276 <p>Sites that need to install multiple versions of GCC may not want to | |
277 use the above simple configuration. It is possible to use the | |
278 <samp><span class="option">--program-prefix</span></samp>, <samp><span class="option">--program-suffix</span></samp> and | |
279 <samp><span class="option">--program-transform-name</span></samp> options to install multiple versions | |
280 into a single directory, but it may be simpler to use different prefixes | |
281 and the <samp><span class="option">--with-local-prefix</span></samp> option to specify the location of the | |
282 site-specific files for each version. It will then be necessary for | |
283 users to specify explicitly the location of local site libraries | |
284 (e.g., with <samp><span class="env">LIBRARY_PATH</span></samp>). | |
285 | |
286 <p>The same value can be used for both <samp><span class="option">--with-local-prefix</span></samp> and | |
287 <samp><span class="option">--prefix</span></samp> provided it is not <samp><span class="file">/usr</span></samp>. This can be used | |
288 to avoid the default search of <samp><span class="file">/usr/local/include</span></samp>. | |
289 | |
290 <p><strong>Do not</strong> specify <samp><span class="file">/usr</span></samp> as the <samp><span class="option">--with-local-prefix</span></samp>! | |
291 The directory you use for <samp><span class="option">--with-local-prefix</span></samp> <strong>must not</strong> | |
292 contain any of the system's standard header files. If it did contain | |
293 them, certain programs would be miscompiled (including GNU Emacs, on | |
294 certain targets), because this would override and nullify the header | |
295 file corrections made by the <samp><span class="command">fixincludes</span></samp> script. | |
296 | |
297 <p>Indications are that people who use this option use it based on mistaken | |
298 ideas of what it is for. People use it as if it specified where to | |
299 install part of GCC. Perhaps they make this assumption because | |
300 installing GCC creates the directory. | |
301 | |
302 <br><dt><code>--enable-shared[=</code><var>package</var><code>[,...]]</code><dd>Build shared versions of libraries, if shared libraries are supported on | |
303 the target platform. Unlike GCC 2.95.x and earlier, shared libraries | |
304 are enabled by default on all platforms that support shared libraries. | |
305 | |
306 <p>If a list of packages is given as an argument, build shared libraries | |
307 only for the listed packages. For other packages, only static libraries | |
308 will be built. Package names currently recognized in the GCC tree are | |
309 ‘<samp><span class="samp">libgcc</span></samp>’ (also known as ‘<samp><span class="samp">gcc</span></samp>’), ‘<samp><span class="samp">libstdc++</span></samp>’ (not | |
310 ‘<samp><span class="samp">libstdc++-v3</span></samp>’), ‘<samp><span class="samp">libffi</span></samp>’, ‘<samp><span class="samp">zlib</span></samp>’, ‘<samp><span class="samp">boehm-gc</span></samp>’, | |
311 ‘<samp><span class="samp">ada</span></samp>’, ‘<samp><span class="samp">libada</span></samp>’, ‘<samp><span class="samp">libjava</span></samp>’ and ‘<samp><span class="samp">libobjc</span></samp>’. | |
312 Note ‘<samp><span class="samp">libiberty</span></samp>’ does not support shared libraries at all. | |
313 | |
314 <p>Use <samp><span class="option">--disable-shared</span></samp> to build only static libraries. Note that | |
315 <samp><span class="option">--disable-shared</span></samp> does not accept a list of package names as | |
316 argument, only <samp><span class="option">--enable-shared</span></samp> does. | |
317 | |
318 <br><dt><code><a name="with_002dgnu_002das"></a>--with-gnu-as</code><dd>Specify that the compiler should assume that the | |
319 assembler it finds is the GNU assembler. However, this does not modify | |
320 the rules to find an assembler and will result in confusion if the | |
321 assembler found is not actually the GNU assembler. (Confusion may also | |
322 result if the compiler finds the GNU assembler but has not been | |
323 configured with <samp><span class="option">--with-gnu-as</span></samp>.) If you have more than one | |
324 assembler installed on your system, you may want to use this option in | |
325 connection with <samp><span class="option">--with-as=</span><var>pathname</var></samp> or | |
326 <samp><span class="option">--with-build-time-tools=</span><var>pathname</var></samp>. | |
327 | |
328 <p>The following systems are the only ones where it makes a difference | |
329 whether you use the GNU assembler. On any other system, | |
330 <samp><span class="option">--with-gnu-as</span></samp> has no effect. | |
331 | |
332 <ul> | |
333 <li>‘<samp><span class="samp">hppa1.0-</span><var>any</var><span class="samp">-</span><var>any</var></samp>’ | |
334 <li>‘<samp><span class="samp">hppa1.1-</span><var>any</var><span class="samp">-</span><var>any</var></samp>’ | |
335 <li>‘<samp><span class="samp">sparc-sun-solaris2.</span><var>any</var></samp>’ | |
336 <li>‘<samp><span class="samp">sparc64-</span><var>any</var><span class="samp">-solaris2.</span><var>any</var></samp>’ | |
337 </ul> | |
338 | |
339 <br><dt><code><a name="with_002das"></a>--with-as=</code><var>pathname</var><dd>Specify that the compiler should use the assembler pointed to by | |
340 <var>pathname</var>, rather than the one found by the standard rules to find | |
341 an assembler, which are: | |
342 <ul> | |
343 <li>Unless GCC is being built with a cross compiler, check the | |
344 <samp><var>libexec</var><span class="file">/gcc/</span><var>target</var><span class="file">/</span><var>version</var></samp> directory. | |
345 <var>libexec</var> defaults to <samp><var>exec-prefix</var><span class="file">/libexec</span></samp>; | |
346 <var>exec-prefix</var> defaults to <var>prefix</var>, which | |
347 defaults to <samp><span class="file">/usr/local</span></samp> unless overridden by the | |
348 <samp><span class="option">--prefix=</span><var>pathname</var></samp> switch described above. <var>target</var> | |
349 is the target system triple, such as ‘<samp><span class="samp">sparc-sun-solaris2.7</span></samp>’, and | |
350 <var>version</var> denotes the GCC version, such as 3.0. | |
351 | |
352 <li>If the target system is the same that you are building on, check | |
353 operating system specific directories (e.g. <samp><span class="file">/usr/ccs/bin</span></samp> on | |
354 Sun Solaris 2). | |
355 | |
356 <li>Check in the <samp><span class="env">PATH</span></samp> for a tool whose name is prefixed by the | |
357 target system triple. | |
358 | |
359 <li>Check in the <samp><span class="env">PATH</span></samp> for a tool whose name is not prefixed by the | |
360 target system triple, if the host and target system triple are | |
361 the same (in other words, we use a host tool if it can be used for | |
362 the target as well). | |
363 </ul> | |
364 | |
365 <p>You may want to use <samp><span class="option">--with-as</span></samp> if no assembler | |
366 is installed in the directories listed above, or if you have multiple | |
367 assemblers installed and want to choose one that is not found by the | |
368 above rules. | |
369 | |
370 <br><dt><code><a name="with_002dgnu_002dld"></a>--with-gnu-ld</code><dd>Same as <a href="#with-gnu-as"><samp><span class="option">--with-gnu-as</span></samp></a> | |
371 but for the linker. | |
372 | |
373 <br><dt><code>--with-ld=</code><var>pathname</var><dd>Same as <a href="#with-as"><samp><span class="option">--with-as</span></samp></a> | |
374 but for the linker. | |
375 | |
376 <br><dt><code>--with-stabs</code><dd>Specify that stabs debugging | |
377 information should be used instead of whatever format the host normally | |
378 uses. Normally GCC uses the same debug format as the host system. | |
379 | |
380 <p>On MIPS based systems and on Alphas, you must specify whether you want | |
381 GCC to create the normal ECOFF debugging format, or to use BSD-style | |
382 stabs passed through the ECOFF symbol table. The normal ECOFF debug | |
383 format cannot fully handle languages other than C. BSD stabs format can | |
384 handle other languages, but it only works with the GNU debugger GDB. | |
385 | |
386 <p>Normally, GCC uses the ECOFF debugging format by default; if you | |
387 prefer BSD stabs, specify <samp><span class="option">--with-stabs</span></samp> when you configure GCC. | |
388 | |
389 <p>No matter which default you choose when you configure GCC, the user | |
390 can use the <samp><span class="option">-gcoff</span></samp> and <samp><span class="option">-gstabs+</span></samp> options to specify explicitly | |
391 the debug format for a particular compilation. | |
392 | |
393 <p><samp><span class="option">--with-stabs</span></samp> is meaningful on the ISC system on the 386, also, if | |
394 <samp><span class="option">--with-gas</span></samp> is used. It selects use of stabs debugging | |
395 information embedded in COFF output. This kind of debugging information | |
396 supports C++ well; ordinary COFF debugging information does not. | |
397 | |
398 <p><samp><span class="option">--with-stabs</span></samp> is also meaningful on 386 systems running SVR4. It | |
399 selects use of stabs debugging information embedded in ELF output. The | |
400 C++ compiler currently (2.6.0) does not support the DWARF debugging | |
401 information normally used on 386 SVR4 platforms; stabs provide a | |
402 workable alternative. This requires gas and gdb, as the normal SVR4 | |
403 tools can not generate or interpret stabs. | |
404 | |
405 <br><dt><code>--disable-multilib</code><dd>Specify that multiple target | |
406 libraries to support different target variants, calling | |
407 conventions, etc. should not be built. The default is to build a | |
408 predefined set of them. | |
409 | |
410 <p>Some targets provide finer-grained control over which multilibs are built | |
411 (e.g., <samp><span class="option">--disable-softfloat</span></samp>): | |
412 <dl> | |
413 <dt><code>arc-*-elf*</code><dd>biendian. | |
414 | |
415 <br><dt><code>arm-*-*</code><dd>fpu, 26bit, underscore, interwork, biendian, nofmult. | |
416 | |
417 <br><dt><code>m68*-*-*</code><dd>softfloat, m68881, m68000, m68020. | |
418 | |
419 <br><dt><code>mips*-*-*</code><dd>single-float, biendian, softfloat. | |
420 | |
421 <br><dt><code>powerpc*-*-*, rs6000*-*-*</code><dd>aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian, | |
422 sysv, aix. | |
423 | |
424 </dl> | |
425 | |
426 <br><dt><code>--enable-threads</code><dd>Specify that the target | |
427 supports threads. This affects the Objective-C compiler and runtime | |
428 library, and exception handling for other languages like C++ and Java. | |
429 On some systems, this is the default. | |
430 | |
431 <p>In general, the best (and, in many cases, the only known) threading | |
432 model available will be configured for use. Beware that on some | |
433 systems, GCC has not been taught what threading models are generally | |
434 available for the system. In this case, <samp><span class="option">--enable-threads</span></samp> is an | |
435 alias for <samp><span class="option">--enable-threads=single</span></samp>. | |
436 | |
437 <br><dt><code>--disable-threads</code><dd>Specify that threading support should be disabled for the system. | |
438 This is an alias for <samp><span class="option">--enable-threads=single</span></samp>. | |
439 | |
440 <br><dt><code>--enable-threads=</code><var>lib</var><dd>Specify that | |
441 <var>lib</var> is the thread support library. This affects the Objective-C | |
442 compiler and runtime library, and exception handling for other languages | |
443 like C++ and Java. The possibilities for <var>lib</var> are: | |
444 | |
445 <dl> | |
446 <dt><code>aix</code><dd>AIX thread support. | |
447 <br><dt><code>dce</code><dd>DCE thread support. | |
448 <br><dt><code>gnat</code><dd>Ada tasking support. For non-Ada programs, this setting is equivalent | |
449 to ‘<samp><span class="samp">single</span></samp>’. When used in conjunction with the Ada run time, it | |
450 causes GCC to use the same thread primitives as Ada uses. This option | |
451 is necessary when using both Ada and the back end exception handling, | |
452 which is the default for most Ada targets. | |
453 <br><dt><code>mach</code><dd>Generic MACH thread support, known to work on NeXTSTEP. (Please note | |
454 that the file needed to support this configuration, <samp><span class="file">gthr-mach.h</span></samp>, is | |
455 missing and thus this setting will cause a known bootstrap failure.) | |
456 <br><dt><code>no</code><dd>This is an alias for ‘<samp><span class="samp">single</span></samp>’. | |
457 <br><dt><code>posix</code><dd>Generic POSIX/Unix98 thread support. | |
458 <br><dt><code>posix95</code><dd>Generic POSIX/Unix95 thread support. | |
459 <br><dt><code>rtems</code><dd>RTEMS thread support. | |
460 <br><dt><code>single</code><dd>Disable thread support, should work for all platforms. | |
461 <br><dt><code>solaris</code><dd>Sun Solaris 2 thread support. | |
462 <br><dt><code>vxworks</code><dd>VxWorks thread support. | |
463 <br><dt><code>win32</code><dd>Microsoft Win32 API thread support. | |
464 <br><dt><code>nks</code><dd>Novell Kernel Services thread support. | |
465 </dl> | |
466 | |
467 <br><dt><code>--enable-tls</code><dd>Specify that the target supports TLS (Thread Local Storage). Usually | |
468 configure can correctly determine if TLS is supported. In cases where | |
469 it guesses incorrectly, TLS can be explicitly enabled or disabled with | |
470 <samp><span class="option">--enable-tls</span></samp> or <samp><span class="option">--disable-tls</span></samp>. This can happen if | |
471 the assembler supports TLS but the C library does not, or if the | |
472 assumptions made by the configure test are incorrect. | |
473 | |
474 <br><dt><code>--disable-tls</code><dd>Specify that the target does not support TLS. | |
475 This is an alias for <samp><span class="option">--enable-tls=no</span></samp>. | |
476 | |
477 <br><dt><code>--with-cpu=</code><var>cpu</var><dt><code>--with-cpu-32=</code><var>cpu</var><dt><code>--with-cpu-64=</code><var>cpu</var><dd>Specify which cpu variant the compiler should generate code for by default. | |
478 <var>cpu</var> will be used as the default value of the <samp><span class="option">-mcpu=</span></samp> switch. | |
479 This option is only supported on some targets, including ARM, i386, M68k, | |
480 PowerPC, and SPARC. The <samp><span class="option">--with-cpu-32</span></samp> and | |
481 <samp><span class="option">--with-cpu-64</span></samp> options specify separate default CPUs for | |
482 32-bit and 64-bit modes; these options are only supported for i386 and | |
483 x86-64. | |
484 | |
485 <br><dt><code>--with-schedule=</code><var>cpu</var><dt><code>--with-arch=</code><var>cpu</var><dt><code>--with-arch-32=</code><var>cpu</var><dt><code>--with-arch-64=</code><var>cpu</var><dt><code>--with-tune=</code><var>cpu</var><dt><code>--with-tune-32=</code><var>cpu</var><dt><code>--with-tune-64=</code><var>cpu</var><dt><code>--with-abi=</code><var>abi</var><dt><code>--with-fpu=</code><var>type</var><dt><code>--with-float=</code><var>type</var><dd>These configure options provide default values for the <samp><span class="option">-mschedule=</span></samp>, | |
486 <samp><span class="option">-march=</span></samp>, <samp><span class="option">-mtune=</span></samp>, <samp><span class="option">-mabi=</span></samp>, and <samp><span class="option">-mfpu=</span></samp> | |
487 options and for <samp><span class="option">-mhard-float</span></samp> or <samp><span class="option">-msoft-float</span></samp>. As with | |
488 <samp><span class="option">--with-cpu</span></samp>, which switches will be accepted and acceptable values | |
489 of the arguments depend on the target. | |
490 | |
491 <br><dt><code>--with-mode=</code><var>mode</var><dd>Specify if the compiler should default to <samp><span class="option">-marm</span></samp> or <samp><span class="option">-mthumb</span></samp>. | |
492 This option is only supported on ARM targets. | |
493 | |
494 <br><dt><code>--with-divide=</code><var>type</var><dd>Specify how the compiler should generate code for checking for | |
495 division by zero. This option is only supported on the MIPS target. | |
496 The possibilities for <var>type</var> are: | |
497 <dl> | |
498 <dt><code>traps</code><dd>Division by zero checks use conditional traps (this is the default on | |
499 systems that support conditional traps). | |
500 <br><dt><code>breaks</code><dd>Division by zero checks use the break instruction. | |
501 </dl> | |
502 | |
503 <!-- If you make -with-llsc the default for additional targets, --> | |
504 <!-- update the -with-llsc description in the MIPS section below. --> | |
505 <br><dt><code>--with-llsc</code><dd>On MIPS targets, make <samp><span class="option">-mllsc</span></samp> the default when no | |
506 <samp><span class="option">-mno-lsc</span></samp> option is passed. This is the default for | |
507 Linux-based targets, as the kernel will emulate them if the ISA does | |
508 not provide them. | |
509 | |
510 <br><dt><code>--without-llsc</code><dd>On MIPS targets, make <samp><span class="option">-mno-llsc</span></samp> the default when no | |
511 <samp><span class="option">-mllsc</span></samp> option is passed. | |
512 | |
513 <br><dt><code>--with-mips-plt</code><dd>On MIPS targets, make use of copy relocations and PLTs. | |
514 These features are extensions to the traditional | |
515 SVR4-based MIPS ABIs and require support from GNU binutils | |
516 and the runtime C library. | |
517 | |
518 <br><dt><code>--enable-__cxa_atexit</code><dd>Define if you want to use __cxa_atexit, rather than atexit, to | |
519 register C++ destructors for local statics and global objects. | |
520 This is essential for fully standards-compliant handling of | |
521 destructors, but requires __cxa_atexit in libc. This option is currently | |
522 only available on systems with GNU libc. When enabled, this will cause | |
523 <samp><span class="option">-fuse-cxa-atexit</span></samp> to be passed by default. | |
524 | |
525 <br><dt><code>--enable-target-optspace</code><dd>Specify that target | |
526 libraries should be optimized for code space instead of code speed. | |
527 This is the default for the m32r platform. | |
528 | |
529 <br><dt><code>--disable-cpp</code><dd>Specify that a user visible <samp><span class="command">cpp</span></samp> program should not be installed. | |
530 | |
531 <br><dt><code>--with-cpp-install-dir=</code><var>dirname</var><dd>Specify that the user visible <samp><span class="command">cpp</span></samp> program should be installed | |
532 in <samp><var>prefix</var><span class="file">/</span><var>dirname</var><span class="file">/cpp</span></samp>, in addition to <var>bindir</var>. | |
533 | |
534 <br><dt><code>--enable-initfini-array</code><dd>Force the use of sections <code>.init_array</code> and <code>.fini_array</code> | |
535 (instead of <code>.init</code> and <code>.fini</code>) for constructors and | |
536 destructors. Option <samp><span class="option">--disable-initfini-array</span></samp> has the | |
537 opposite effect. If neither option is specified, the configure script | |
538 will try to guess whether the <code>.init_array</code> and | |
539 <code>.fini_array</code> sections are supported and, if they are, use them. | |
540 | |
541 <br><dt><code>--enable-maintainer-mode</code><dd>The build rules that | |
542 regenerate the GCC master message catalog <samp><span class="file">gcc.pot</span></samp> are normally | |
543 disabled. This is because it can only be rebuilt if the complete source | |
544 tree is present. If you have changed the sources and want to rebuild the | |
545 catalog, configuring with <samp><span class="option">--enable-maintainer-mode</span></samp> will enable | |
546 this. Note that you need a recent version of the <code>gettext</code> tools | |
547 to do so. | |
548 | |
549 <br><dt><code>--disable-bootstrap</code><dd>For a native build, the default configuration is to perform | |
550 a 3-stage bootstrap of the compiler when ‘<samp><span class="samp">make</span></samp>’ is invoked, | |
551 testing that GCC can compile itself correctly. If you want to disable | |
552 this process, you can configure with <samp><span class="option">--disable-bootstrap</span></samp>. | |
553 | |
554 <br><dt><code>--enable-bootstrap</code><dd>In special cases, you may want to perform a 3-stage build | |
555 even if the target and host triplets are different. | |
556 This could happen when the host can run code compiled for | |
557 the target (e.g. host is i686-linux, target is i486-linux). | |
558 Starting from GCC 4.2, to do this you have to configure explicitly | |
559 with <samp><span class="option">--enable-bootstrap</span></samp>. | |
560 | |
561 <br><dt><code>--enable-generated-files-in-srcdir</code><dd>Neither the .c and .h files that are generated from Bison and flex nor the | |
562 info manuals and man pages that are built from the .texi files are present | |
563 in the SVN development tree. When building GCC from that development tree, | |
564 or from one of our snapshots, those generated files are placed in your | |
565 build directory, which allows for the source to be in a readonly | |
566 directory. | |
567 | |
568 <p>If you configure with <samp><span class="option">--enable-generated-files-in-srcdir</span></samp> then those | |
569 generated files will go into the source directory. This is mainly intended | |
570 for generating release or prerelease tarballs of the GCC sources, since it | |
571 is not a requirement that the users of source releases to have flex, Bison, | |
572 or makeinfo. | |
573 | |
574 <br><dt><code>--enable-version-specific-runtime-libs</code><dd>Specify | |
575 that runtime libraries should be installed in the compiler specific | |
576 subdirectory (<samp><var>libdir</var><span class="file">/gcc</span></samp>) rather than the usual places. In | |
577 addition, ‘<samp><span class="samp">libstdc++</span></samp>’'s include files will be installed into | |
578 <samp><var>libdir</var></samp> unless you overruled it by using | |
579 <samp><span class="option">--with-gxx-include-dir=</span><var>dirname</var></samp>. Using this option is | |
580 particularly useful if you intend to use several versions of GCC in | |
581 parallel. This is currently supported by ‘<samp><span class="samp">libgfortran</span></samp>’, | |
582 ‘<samp><span class="samp">libjava</span></samp>’, ‘<samp><span class="samp">libmudflap</span></samp>’, ‘<samp><span class="samp">libstdc++</span></samp>’, and ‘<samp><span class="samp">libobjc</span></samp>’. | |
583 | |
584 <br><dt><code>--enable-languages=</code><var>lang1</var><code>,</code><var>lang2</var><code>,...</code><dd>Specify that only a particular subset of compilers and | |
585 their runtime libraries should be built. For a list of valid values for | |
586 <var>langN</var> you can issue the following command in the | |
587 <samp><span class="file">gcc</span></samp> directory of your GCC source tree:<br> | |
588 <pre class="smallexample"> grep language= */config-lang.in | |
589 </pre> | |
590 <p>Currently, you can use any of the following: | |
591 <code>all</code>, <code>ada</code>, <code>c</code>, <code>c++</code>, <code>fortran</code>, <code>java</code>, | |
592 <code>objc</code>, <code>obj-c++</code>. | |
593 Building the Ada compiler has special requirements, see below. | |
594 If you do not pass this flag, or specify the option <code>all</code>, then all | |
595 default languages available in the <samp><span class="file">gcc</span></samp> sub-tree will be configured. | |
596 Ada and Objective-C++ are not default languages; the rest are. | |
597 Re-defining <code>LANGUAGES</code> when calling ‘<samp><span class="samp">make</span></samp>’ <strong>does not</strong> | |
598 work anymore, as those language sub-directories might not have been | |
599 configured! | |
600 | |
601 <br><dt><code>--enable-stage1-languages=</code><var>lang1</var><code>,</code><var>lang2</var><code>,...</code><dd>Specify that a particular subset of compilers and their runtime | |
602 libraries should be built with the system C compiler during stage 1 of | |
603 the bootstrap process, rather than only in later stages with the | |
604 bootstrapped C compiler. The list of valid values is the same as for | |
605 <samp><span class="option">--enable-languages</span></samp>, and the option <code>all</code> will select all | |
606 of the languages enabled by <samp><span class="option">--enable-languages</span></samp>. This option is | |
607 primarily useful for GCC development; for instance, when a development | |
608 version of the compiler cannot bootstrap due to compiler bugs, or when | |
609 one is debugging front ends other than the C front end. When this | |
610 option is used, one can then build the target libraries for the | |
611 specified languages with the stage-1 compiler by using <samp><span class="command">make | |
612 stage1-bubble all-target</span></samp>, or run the testsuite on the stage-1 compiler | |
613 for the specified languages using <samp><span class="command">make stage1-start check-gcc</span></samp>. | |
614 | |
615 <br><dt><code>--disable-libada</code><dd>Specify that the run-time libraries and tools used by GNAT should not | |
616 be built. This can be useful for debugging, or for compatibility with | |
617 previous Ada build procedures, when it was required to explicitly | |
618 do a ‘<samp><span class="samp">make -C gcc gnatlib_and_tools</span></samp>’. | |
619 | |
620 <br><dt><code>--disable-libssp</code><dd>Specify that the run-time libraries for stack smashing protection | |
621 should not be built. | |
622 | |
623 <br><dt><code>--disable-libgomp</code><dd>Specify that the run-time libraries used by GOMP should not be built. | |
624 | |
625 <br><dt><code>--with-dwarf2</code><dd>Specify that the compiler should | |
626 use DWARF 2 debugging information as the default. | |
627 | |
628 <br><dt><code>--enable-targets=all</code><dt><code>--enable-targets=</code><var>target_list</var><dd>Some GCC targets, e.g. powerpc64-linux, build bi-arch compilers. | |
629 These are compilers that are able to generate either 64-bit or 32-bit | |
630 code. Typically, the corresponding 32-bit target, e.g. | |
631 powerpc-linux for powerpc64-linux, only generates 32-bit code. This | |
632 option enables the 32-bit target to be a bi-arch compiler, which is | |
633 useful when you want a bi-arch compiler that defaults to 32-bit, and | |
634 you are building a bi-arch or multi-arch binutils in a combined tree. | |
635 Currently, this option only affects sparc-linux, powerpc-linux and | |
636 x86-linux. | |
637 | |
638 <br><dt><code>--enable-secureplt</code><dd>This option enables <samp><span class="option">-msecure-plt</span></samp> by default for powerpc-linux. | |
639 See “RS/6000 and PowerPC Options” in the main manual | |
640 | |
641 <br><dt><code>--enable-cld</code><dd>This option enables <samp><span class="option">-mcld</span></samp> by default for 32-bit x86 targets. | |
642 See “i386 and x86-64 Options” in the main manual | |
643 | |
644 <br><dt><code>--enable-win32-registry</code><dt><code>--enable-win32-registry=</code><var>key</var><dt><code>--disable-win32-registry</code><dd>The <samp><span class="option">--enable-win32-registry</span></samp> option enables Microsoft Windows-hosted GCC | |
645 to look up installations paths in the registry using the following key: | |
646 | |
647 <pre class="smallexample"> <code>HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\</code><var>key</var> | |
648 </pre> | |
649 <p><var>key</var> defaults to GCC version number, and can be overridden by the | |
650 <samp><span class="option">--enable-win32-registry=</span><var>key</var></samp> option. Vendors and distributors | |
651 who use custom installers are encouraged to provide a different key, | |
652 perhaps one comprised of vendor name and GCC version number, to | |
653 avoid conflict with existing installations. This feature is enabled | |
654 by default, and can be disabled by <samp><span class="option">--disable-win32-registry</span></samp> | |
655 option. This option has no effect on the other hosts. | |
656 | |
657 <br><dt><code>--nfp</code><dd>Specify that the machine does not have a floating point unit. This | |
658 option only applies to ‘<samp><span class="samp">m68k-sun-sunos</span><var>n</var></samp>’. On any other | |
659 system, <samp><span class="option">--nfp</span></samp> has no effect. | |
660 | |
661 <br><dt><code>--enable-werror</code><dt><code>--disable-werror</code><dt><code>--enable-werror=yes</code><dt><code>--enable-werror=no</code><dd>When you specify this option, it controls whether certain files in the | |
662 compiler are built with <samp><span class="option">-Werror</span></samp> in bootstrap stage2 and later. | |
663 If you don't specify it, <samp><span class="option">-Werror</span></samp> is turned on for the main | |
664 development trunk. However it defaults to off for release branches and | |
665 final releases. The specific files which get <samp><span class="option">-Werror</span></samp> are | |
666 controlled by the Makefiles. | |
667 | |
668 <br><dt><code>--enable-checking</code><dt><code>--enable-checking=</code><var>list</var><dd>When you specify this option, the compiler is built to perform internal | |
669 consistency checks of the requested complexity. This does not change the | |
670 generated code, but adds error checking within the compiler. This will | |
671 slow down the compiler and may only work properly if you are building | |
672 the compiler with GCC. This is ‘<samp><span class="samp">yes</span></samp>’ by default when building | |
673 from SVN or snapshots, but ‘<samp><span class="samp">release</span></samp>’ for releases. The default | |
674 for building the stage1 compiler is ‘<samp><span class="samp">yes</span></samp>’. More control | |
675 over the checks may be had by specifying <var>list</var>. The categories of | |
676 checks available are ‘<samp><span class="samp">yes</span></samp>’ (most common checks | |
677 ‘<samp><span class="samp">assert,misc,tree,gc,rtlflag,runtime</span></samp>’), ‘<samp><span class="samp">no</span></samp>’ (no checks at | |
678 all), ‘<samp><span class="samp">all</span></samp>’ (all but ‘<samp><span class="samp">valgrind</span></samp>’), ‘<samp><span class="samp">release</span></samp>’ (cheapest | |
679 checks ‘<samp><span class="samp">assert,runtime</span></samp>’) or ‘<samp><span class="samp">none</span></samp>’ (same as ‘<samp><span class="samp">no</span></samp>’). | |
680 Individual checks can be enabled with these flags ‘<samp><span class="samp">assert</span></samp>’, | |
681 ‘<samp><span class="samp">df</span></samp>’, ‘<samp><span class="samp">fold</span></samp>’, ‘<samp><span class="samp">gc</span></samp>’, ‘<samp><span class="samp">gcac</span></samp>’ ‘<samp><span class="samp">misc</span></samp>’, ‘<samp><span class="samp">rtl</span></samp>’, | |
682 ‘<samp><span class="samp">rtlflag</span></samp>’, ‘<samp><span class="samp">runtime</span></samp>’, ‘<samp><span class="samp">tree</span></samp>’, and ‘<samp><span class="samp">valgrind</span></samp>’. | |
683 | |
684 <p>The ‘<samp><span class="samp">valgrind</span></samp>’ check requires the external <samp><span class="command">valgrind</span></samp> | |
685 simulator, available from <a href="http://valgrind.org/">http://valgrind.org/</a>. The | |
686 ‘<samp><span class="samp">df</span></samp>’, ‘<samp><span class="samp">rtl</span></samp>’, ‘<samp><span class="samp">gcac</span></samp>’ and ‘<samp><span class="samp">valgrind</span></samp>’ checks are very expensive. | |
687 To disable all checking, ‘<samp><span class="samp">--disable-checking</span></samp>’ or | |
688 ‘<samp><span class="samp">--enable-checking=none</span></samp>’ must be explicitly requested. Disabling | |
689 assertions will make the compiler and runtime slightly faster but | |
690 increase the risk of undetected internal errors causing wrong code to be | |
691 generated. | |
692 | |
693 <br><dt><code>--disable-stage1-checking</code><br><dt><code>--enable-stage1-checking</code><dt><code>--enable-stage1-checking=</code><var>list</var><dd>If no <samp><span class="option">--enable-checking</span></samp> option is specified the stage1 | |
694 compiler will be built with ‘<samp><span class="samp">yes</span></samp>’ checking enabled, otherwise | |
695 the stage1 checking flags are the same as specified by | |
696 <samp><span class="option">--enable-checking</span></samp>. To build the stage1 compiler with | |
697 different checking options use <samp><span class="option">--enable-stage1-checking</span></samp>. | |
698 The list of checking options is the same as for <samp><span class="option">--enable-checking</span></samp>. | |
699 If your system is too slow or too small to bootstrap a released compiler | |
700 with checking for stage1 enabled, you can use ‘<samp><span class="samp">--disable-stage1-checking</span></samp>’ | |
701 to disable checking for the stage1 compiler. | |
702 | |
703 <br><dt><code>--enable-coverage</code><dt><code>--enable-coverage=</code><var>level</var><dd>With this option, the compiler is built to collect self coverage | |
704 information, every time it is run. This is for internal development | |
705 purposes, and only works when the compiler is being built with gcc. The | |
706 <var>level</var> argument controls whether the compiler is built optimized or | |
707 not, values are ‘<samp><span class="samp">opt</span></samp>’ and ‘<samp><span class="samp">noopt</span></samp>’. For coverage analysis you | |
708 want to disable optimization, for performance analysis you want to | |
709 enable optimization. When coverage is enabled, the default level is | |
710 without optimization. | |
711 | |
712 <br><dt><code>--enable-gather-detailed-mem-stats</code><dd>When this option is specified more detailed information on memory | |
713 allocation is gathered. This information is printed when using | |
714 <samp><span class="option">-fmem-report</span></samp>. | |
715 | |
716 <br><dt><code>--with-gc</code><dt><code>--with-gc=</code><var>choice</var><dd>With this option you can specify the garbage collector implementation | |
717 used during the compilation process. <var>choice</var> can be one of | |
718 ‘<samp><span class="samp">page</span></samp>’ and ‘<samp><span class="samp">zone</span></samp>’, where ‘<samp><span class="samp">page</span></samp>’ is the default. | |
719 | |
720 <br><dt><code>--enable-nls</code><dt><code>--disable-nls</code><dd>The <samp><span class="option">--enable-nls</span></samp> option enables Native Language Support (NLS), | |
721 which lets GCC output diagnostics in languages other than American | |
722 English. Native Language Support is enabled by default if not doing a | |
723 canadian cross build. The <samp><span class="option">--disable-nls</span></samp> option disables NLS. | |
724 | |
725 <br><dt><code>--with-included-gettext</code><dd>If NLS is enabled, the <samp><span class="option">--with-included-gettext</span></samp> option causes the build | |
726 procedure to prefer its copy of GNU <samp><span class="command">gettext</span></samp>. | |
727 | |
728 <br><dt><code>--with-catgets</code><dd>If NLS is enabled, and if the host lacks <code>gettext</code> but has the | |
729 inferior <code>catgets</code> interface, the GCC build procedure normally | |
730 ignores <code>catgets</code> and instead uses GCC's copy of the GNU | |
731 <code>gettext</code> library. The <samp><span class="option">--with-catgets</span></samp> option causes the | |
732 build procedure to use the host's <code>catgets</code> in this situation. | |
733 | |
734 <br><dt><code>--with-libiconv-prefix=</code><var>dir</var><dd>Search for libiconv header files in <samp><var>dir</var><span class="file">/include</span></samp> and | |
735 libiconv library files in <samp><var>dir</var><span class="file">/lib</span></samp>. | |
736 | |
737 <br><dt><code>--enable-obsolete</code><dd>Enable configuration for an obsoleted system. If you attempt to | |
738 configure GCC for a system (build, host, or target) which has been | |
739 obsoleted, and you do not specify this flag, configure will halt with an | |
740 error message. | |
741 | |
742 <p>All support for systems which have been obsoleted in one release of GCC | |
743 is removed entirely in the next major release, unless someone steps | |
744 forward to maintain the port. | |
745 | |
746 <br><dt><code>--enable-decimal-float</code><dt><code>--enable-decimal-float=yes</code><dt><code>--enable-decimal-float=no</code><dt><code>--enable-decimal-float=bid</code><dt><code>--enable-decimal-float=dpd</code><dt><code>--disable-decimal-float</code><dd>Enable (or disable) support for the C decimal floating point extension | |
747 that is in the IEEE 754-2008 standard. This is enabled by default only | |
748 on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also | |
749 support it, but require the user to specifically enable it. You can | |
750 optionally control which decimal floating point format is used (either | |
751 ‘<samp><span class="samp">bid</span></samp>’ or ‘<samp><span class="samp">dpd</span></samp>’). The ‘<samp><span class="samp">bid</span></samp>’ (binary integer decimal) | |
752 format is default on i386 and x86_64 systems, and the ‘<samp><span class="samp">dpd</span></samp>’ | |
753 (densely packed decimal) format is default on PowerPC systems. | |
754 | |
755 <br><dt><code>--enable-fixed-point</code><dt><code>--disable-fixed-point</code><dd>Enable (or disable) support for C fixed-point arithmetic. | |
756 This option is enabled by default for some targets (such as MIPS) which | |
757 have hardware-support for fixed-point operations. On other targets, you | |
758 may enable this option manually. | |
759 | |
760 <br><dt><code>--with-long-double-128</code><dd>Specify if <code>long double</code> type should be 128-bit by default on selected | |
761 GNU/Linux architectures. If using <code>--without-long-double-128</code>, | |
762 <code>long double</code> will be by default 64-bit, the same as <code>double</code> type. | |
763 When neither of these configure options are used, the default will be | |
764 128-bit <code>long double</code> when built against GNU C Library 2.4 and later, | |
765 64-bit <code>long double</code> otherwise. | |
766 | |
767 <br><dt><code>--with-gmp=</code><var>pathname</var><dt><code>--with-gmp-include=</code><var>pathname</var><dt><code>--with-gmp-lib=</code><var>pathname</var><dt><code>--with-mpfr=</code><var>pathname</var><dt><code>--with-mpfr-include=</code><var>pathname</var><dt><code>--with-mpfr-lib=</code><var>pathname</var><dd>If you do not have GMP (the GNU Multiple Precision library) and the | |
768 MPFR Libraries installed in a standard location and you want to build | |
769 GCC, you can explicitly specify the directory where they are installed | |
770 (‘<samp><span class="samp">--with-gmp=</span><var>gmpinstalldir</var></samp>’, | |
771 ‘<samp><span class="samp">--with-mpfr=</span><var>mpfrinstalldir</var></samp>’). The | |
772 <samp><span class="option">--with-gmp=</span><var>gmpinstalldir</var></samp> option is shorthand for | |
773 <samp><span class="option">--with-gmp-lib=</span><var>gmpinstalldir</var><span class="option">/lib</span></samp> and | |
774 <samp><span class="option">--with-gmp-include=</span><var>gmpinstalldir</var><span class="option">/include</span></samp>. Likewise the | |
775 <samp><span class="option">--with-mpfr=</span><var>mpfrinstalldir</var></samp> option is shorthand for | |
776 <samp><span class="option">--with-mpfr-lib=</span><var>mpfrinstalldir</var><span class="option">/lib</span></samp> and | |
777 <samp><span class="option">--with-mpfr-include=</span><var>mpfrinstalldir</var><span class="option">/include</span></samp>. If these | |
778 shorthand assumptions are not correct, you can use the explicit | |
779 include and lib options directly. | |
780 | |
781 <br><dt><code>--with-ppl=</code><var>pathname</var><dt><code>--with-ppl-include=</code><var>pathname</var><dt><code>--with-ppl-lib=</code><var>pathname</var><dt><code>--with-cloog=</code><var>pathname</var><dt><code>--with-cloog-include=</code><var>pathname</var><dt><code>--with-cloog-lib=</code><var>pathname</var><dd>If you do not have PPL (the Parma Polyhedra Library) and the CLooG | |
782 libraries installed in a standard location and you want to build GCC, | |
783 you can explicitly specify the directory where they are installed | |
784 (‘<samp><span class="samp">--with-ppl=</span><var>pplinstalldir</var></samp>’, | |
785 ‘<samp><span class="samp">--with-cloog=</span><var>clooginstalldir</var></samp>’). The | |
786 <samp><span class="option">--with-ppl=</span><var>pplinstalldir</var></samp> option is shorthand for | |
787 <samp><span class="option">--with-ppl-lib=</span><var>pplinstalldir</var><span class="option">/lib</span></samp> and | |
788 <samp><span class="option">--with-ppl-include=</span><var>pplinstalldir</var><span class="option">/include</span></samp>. Likewise the | |
789 <samp><span class="option">--with-cloog=</span><var>clooginstalldir</var></samp> option is shorthand for | |
790 <samp><span class="option">--with-cloog-lib=</span><var>clooginstalldir</var><span class="option">/lib</span></samp> and | |
791 <samp><span class="option">--with-cloog-include=</span><var>clooginstalldir</var><span class="option">/include</span></samp>. If these | |
792 shorthand assumptions are not correct, you can use the explicit | |
793 include and lib options directly. | |
794 | |
795 <br><dt><code>--with-host-libstdcxx=</code><var>linker-args</var><dd>If you are linking with a static copy of PPL, you can use this option | |
796 to specify how the linker should find the standard C++ library used | |
797 internally by PPL. Typical values of <var>linker-args</var> might be | |
798 ‘<samp><span class="samp">-lstdc++</span></samp>’ or ‘<samp><span class="samp">-Wl,-Bstatic,-lstdc++,-Bdynamic -lm</span></samp>’. If you are | |
799 linking with a shared copy of PPL, you probably do not need this | |
800 option; shared library dependencies will cause the linker to search | |
801 for the standard C++ library automatically. | |
802 | |
803 <br><dt><code>--with-debug-prefix-map=</code><var>map</var><dd>Convert source directory names using <samp><span class="option">-fdebug-prefix-map</span></samp> when | |
804 building runtime libraries. ‘<samp><var>map</var></samp>’ is a space-separated | |
805 list of maps of the form ‘<samp><var>old</var><span class="samp">=</span><var>new</var></samp>’. | |
806 | |
807 </dl> | |
808 | |
809 <h4 class="subheading"><a name="TOC3"></a>Cross-Compiler-Specific Options</h4> | |
810 | |
811 <p>The following options only apply to building cross compilers. | |
812 <dl> | |
813 <dt><code>--with-sysroot</code><dt><code>--with-sysroot=</code><var>dir</var><dd>Tells GCC to consider <var>dir</var> as the root of a tree that contains a | |
814 (subset of) the root filesystem of the target operating system. | |
815 Target system headers, libraries and run-time object files will be | |
816 searched in there. The specified directory is not copied into the | |
817 install tree, unlike the options <samp><span class="option">--with-headers</span></samp> and | |
818 <samp><span class="option">--with-libs</span></samp> that this option obsoletes. The default value, | |
819 in case <samp><span class="option">--with-sysroot</span></samp> is not given an argument, is | |
820 <samp><span class="option">${gcc_tooldir}/sys-root</span></samp>. If the specified directory is a | |
821 subdirectory of <samp><span class="option">${exec_prefix}</span></samp>, then it will be found relative to | |
822 the GCC binaries if the installation tree is moved. | |
823 | |
824 <br><dt><code>--with-build-sysroot</code><dt><code>--with-build-sysroot=</code><var>dir</var><dd>Tells GCC to consider <var>dir</var> as the system root (see | |
825 <samp><span class="option">--with-sysroot</span></samp>) while building target libraries, instead of | |
826 the directory specified with <samp><span class="option">--with-sysroot</span></samp>. This option is | |
827 only useful when you are already using <samp><span class="option">--with-sysroot</span></samp>. You | |
828 can use <samp><span class="option">--with-build-sysroot</span></samp> when you are configuring with | |
829 <samp><span class="option">--prefix</span></samp> set to a directory that is different from the one in | |
830 which you are installing GCC and your target libraries. | |
831 | |
832 <p>This option affects the system root for the compiler used to build | |
833 target libraries (which runs on the build system); it does not affect | |
834 the compiler which is used to build GCC itself. | |
835 | |
836 <br><dt><code>--with-headers</code><dt><code>--with-headers=</code><var>dir</var><dd>Deprecated in favor of <samp><span class="option">--with-sysroot</span></samp>. | |
837 Specifies that target headers are available when building a cross compiler. | |
838 The <var>dir</var> argument specifies a directory which has the target include | |
839 files. These include files will be copied into the <samp><span class="file">gcc</span></samp> install | |
840 directory. <em>This option with the </em><var>dir</var><em> argument is required</em> when | |
841 building a cross compiler, if <samp><var>prefix</var><span class="file">/</span><var>target</var><span class="file">/sys-include</span></samp> | |
842 doesn't pre-exist. If <samp><var>prefix</var><span class="file">/</span><var>target</var><span class="file">/sys-include</span></samp> does | |
843 pre-exist, the <var>dir</var> argument may be omitted. <samp><span class="command">fixincludes</span></samp> | |
844 will be run on these files to make them compatible with GCC. | |
845 | |
846 <br><dt><code>--without-headers</code><dd>Tells GCC not use any target headers from a libc when building a cross | |
847 compiler. When crossing to GNU/Linux, you need the headers so GCC | |
848 can build the exception handling for libgcc. | |
849 | |
850 <br><dt><code>--with-libs</code><dt><code>--with-libs=``</code><var>dir1</var> <var>dir2</var><code> ... </code><var>dirN</var><code>''</code><dd>Deprecated in favor of <samp><span class="option">--with-sysroot</span></samp>. | |
851 Specifies a list of directories which contain the target runtime | |
852 libraries. These libraries will be copied into the <samp><span class="file">gcc</span></samp> install | |
853 directory. If the directory list is omitted, this option has no | |
854 effect. | |
855 | |
856 <br><dt><code>--with-newlib</code><dd>Specifies that ‘<samp><span class="samp">newlib</span></samp>’ is | |
857 being used as the target C library. This causes <code>__eprintf</code> to be | |
858 omitted from <samp><span class="file">libgcc.a</span></samp> on the assumption that it will be provided by | |
859 ‘<samp><span class="samp">newlib</span></samp>’. | |
860 | |
861 <br><dt><code>--with-build-time-tools=</code><var>dir</var><dd>Specifies where to find the set of target tools (assembler, linker, etc.) | |
862 that will be used while building GCC itself. This option can be useful | |
863 if the directory layouts are different between the system you are building | |
864 GCC on, and the system where you will deploy it. | |
865 | |
866 <p>For example, on a <samp><span class="option">ia64-hp-hpux</span></samp> system, you may have the GNU | |
867 assembler and linker in <samp><span class="file">/usr/bin</span></samp>, and the native tools in a | |
868 different path, and build a toolchain that expects to find the | |
869 native tools in <samp><span class="file">/usr/bin</span></samp>. | |
870 | |
871 <p>When you use this option, you should ensure that <var>dir</var> includes | |
872 <samp><span class="command">ar</span></samp>, <samp><span class="command">as</span></samp>, <samp><span class="command">ld</span></samp>, <samp><span class="command">nm</span></samp>, | |
873 <samp><span class="command">ranlib</span></samp> and <samp><span class="command">strip</span></samp> if necessary, and possibly | |
874 <samp><span class="command">objdump</span></samp>. Otherwise, GCC may use an inconsistent set of | |
875 tools. | |
876 </dl> | |
877 | |
878 <h4 class="subheading"><a name="TOC4"></a>Java-Specific Options</h4> | |
879 | |
880 <p>The following option applies to the build of the Java front end. | |
881 | |
882 <dl> | |
883 <dt><code>--disable-libgcj</code><dd>Specify that the run-time libraries | |
884 used by GCJ should not be built. This is useful in case you intend | |
885 to use GCJ with some other run-time, or you're going to install it | |
886 separately, or it just happens not to build on your particular | |
887 machine. In general, if the Java front end is enabled, the GCJ | |
888 libraries will be enabled too, unless they're known to not work on | |
889 the target platform. If GCJ is enabled but ‘<samp><span class="samp">libgcj</span></samp>’ isn't built, you | |
890 may need to port it; in this case, before modifying the top-level | |
891 <samp><span class="file">configure.in</span></samp> so that ‘<samp><span class="samp">libgcj</span></samp>’ is enabled by default on this platform, | |
892 you may use <samp><span class="option">--enable-libgcj</span></samp> to override the default. | |
893 | |
894 </dl> | |
895 | |
896 <p>The following options apply to building ‘<samp><span class="samp">libgcj</span></samp>’. | |
897 | |
898 <h5 class="subsubheading"><a name="TOC5"></a>General Options</h5> | |
899 | |
900 <dl> | |
901 <dt><code>--enable-java-maintainer-mode</code><dd>By default the ‘<samp><span class="samp">libjava</span></samp>’ build will not attempt to compile the | |
902 <samp><span class="file">.java</span></samp> source files to <samp><span class="file">.class</span></samp>. Instead, it will use the | |
903 <samp><span class="file">.class</span></samp> files from the source tree. If you use this option you | |
904 must have executables named <samp><span class="command">ecj1</span></samp> and <samp><span class="command">gjavah</span></samp> in your path | |
905 for use by the build. You must use this option if you intend to | |
906 modify any <samp><span class="file">.java</span></samp> files in <samp><span class="file">libjava</span></samp>. | |
907 | |
908 <br><dt><code>--with-java-home=</code><var>dirname</var><dd>This ‘<samp><span class="samp">libjava</span></samp>’ option overrides the default value of the | |
909 ‘<samp><span class="samp">java.home</span></samp>’ system property. It is also used to set | |
910 ‘<samp><span class="samp">sun.boot.class.path</span></samp>’ to <samp><var>dirname</var><span class="file">/lib/rt.jar</span></samp>. By | |
911 default ‘<samp><span class="samp">java.home</span></samp>’ is set to <samp><var>prefix</var></samp> and | |
912 ‘<samp><span class="samp">sun.boot.class.path</span></samp>’ to | |
913 <samp><var>datadir</var><span class="file">/java/libgcj-</span><var>version</var><span class="file">.jar</span></samp>. | |
914 | |
915 <br><dt><code>--with-ecj-jar=</code><var>filename</var><dd>This option can be used to specify the location of an external jar | |
916 file containing the Eclipse Java compiler. A specially modified | |
917 version of this compiler is used by <samp><span class="command">gcj</span></samp> to parse | |
918 <samp><span class="file">.java</span></samp> source files. If this option is given, the | |
919 ‘<samp><span class="samp">libjava</span></samp>’ build will create and install an <samp><span class="file">ecj1</span></samp> executable | |
920 which uses this jar file at runtime. | |
921 | |
922 <p>If this option is not given, but an <samp><span class="file">ecj.jar</span></samp> file is found in | |
923 the topmost source tree at configure time, then the ‘<samp><span class="samp">libgcj</span></samp>’ | |
924 build will create and install <samp><span class="file">ecj1</span></samp>, and will also install the | |
925 discovered <samp><span class="file">ecj.jar</span></samp> into a suitable place in the install tree. | |
926 | |
927 <p>If <samp><span class="file">ecj1</span></samp> is not installed, then the user will have to supply one | |
928 on his path in order for <samp><span class="command">gcj</span></samp> to properly parse <samp><span class="file">.java</span></samp> | |
929 source files. A suitable jar is available from | |
930 <a href="ftp://sourceware.org/pub/java/">ftp://sourceware.org/pub/java/</a>. | |
931 | |
932 <br><dt><code>--disable-getenv-properties</code><dd>Don't set system properties from <samp><span class="env">GCJ_PROPERTIES</span></samp>. | |
933 | |
934 <br><dt><code>--enable-hash-synchronization</code><dd>Use a global hash table for monitor locks. Ordinarily, | |
935 ‘<samp><span class="samp">libgcj</span></samp>’'s ‘<samp><span class="samp">configure</span></samp>’ script automatically makes | |
936 the correct choice for this option for your platform. Only use | |
937 this if you know you need the library to be configured differently. | |
938 | |
939 <br><dt><code>--enable-interpreter</code><dd>Enable the Java interpreter. The interpreter is automatically | |
940 enabled by default on all platforms that support it. This option | |
941 is really only useful if you want to disable the interpreter | |
942 (using <samp><span class="option">--disable-interpreter</span></samp>). | |
943 | |
944 <br><dt><code>--disable-java-net</code><dd>Disable java.net. This disables the native part of java.net only, | |
945 using non-functional stubs for native method implementations. | |
946 | |
947 <br><dt><code>--disable-jvmpi</code><dd>Disable JVMPI support. | |
948 | |
949 <br><dt><code>--disable-libgcj-bc</code><dd>Disable BC ABI compilation of certain parts of libgcj. By default, | |
950 some portions of libgcj are compiled with <samp><span class="option">-findirect-dispatch</span></samp> | |
951 and <samp><span class="option">-fno-indirect-classes</span></samp>, allowing them to be overridden at | |
952 run-time. | |
953 | |
954 <p>If <samp><span class="option">--disable-libgcj-bc</span></samp> is specified, libgcj is built without | |
955 these options. This allows the compile-time linker to resolve | |
956 dependencies when statically linking to libgcj. However it makes it | |
957 impossible to override the affected portions of libgcj at run-time. | |
958 | |
959 <br><dt><code>--enable-reduced-reflection</code><dd>Build most of libgcj with <samp><span class="option">-freduced-reflection</span></samp>. This reduces | |
960 the size of libgcj at the expense of not being able to do accurate | |
961 reflection on the classes it contains. This option is safe if you | |
962 know that code using libgcj will never use reflection on the standard | |
963 runtime classes in libgcj (including using serialization, RMI or CORBA). | |
964 | |
965 <br><dt><code>--with-ecos</code><dd>Enable runtime eCos target support. | |
966 | |
967 <br><dt><code>--without-libffi</code><dd>Don't use ‘<samp><span class="samp">libffi</span></samp>’. This will disable the interpreter and JNI | |
968 support as well, as these require ‘<samp><span class="samp">libffi</span></samp>’ to work. | |
969 | |
970 <br><dt><code>--enable-libgcj-debug</code><dd>Enable runtime debugging code. | |
971 | |
972 <br><dt><code>--enable-libgcj-multifile</code><dd>If specified, causes all <samp><span class="file">.java</span></samp> source files to be | |
973 compiled into <samp><span class="file">.class</span></samp> files in one invocation of | |
974 ‘<samp><span class="samp">gcj</span></samp>’. This can speed up build time, but is more | |
975 resource-intensive. If this option is unspecified or | |
976 disabled, ‘<samp><span class="samp">gcj</span></samp>’ is invoked once for each <samp><span class="file">.java</span></samp> | |
977 file to compile into a <samp><span class="file">.class</span></samp> file. | |
978 | |
979 <br><dt><code>--with-libiconv-prefix=DIR</code><dd>Search for libiconv in <samp><span class="file">DIR/include</span></samp> and <samp><span class="file">DIR/lib</span></samp>. | |
980 | |
981 <br><dt><code>--enable-sjlj-exceptions</code><dd>Force use of the <code>setjmp</code>/<code>longjmp</code>-based scheme for exceptions. | |
982 ‘<samp><span class="samp">configure</span></samp>’ ordinarily picks the correct value based on the platform. | |
983 Only use this option if you are sure you need a different setting. | |
984 | |
985 <br><dt><code>--with-system-zlib</code><dd>Use installed ‘<samp><span class="samp">zlib</span></samp>’ rather than that included with GCC. | |
986 | |
987 <br><dt><code>--with-win32-nlsapi=ansi, unicows or unicode</code><dd>Indicates how MinGW ‘<samp><span class="samp">libgcj</span></samp>’ translates between UNICODE | |
988 characters and the Win32 API. | |
989 | |
990 <br><dt><code>--enable-java-home</code><dd>If enabled, this creates a JPackage compatible SDK environment during install. | |
991 Note that if –enable-java-home is used, –with-arch-directory=ARCH must also | |
992 be specified. | |
993 | |
994 <br><dt><code>--with-arch-directory=ARCH</code><dd>Specifies the name to use for the <samp><span class="file">jre/lib/ARCH</span></samp> directory in the SDK | |
995 environment created when –enable-java-home is passed. Typical names for this | |
996 directory include i386, amd64, ia64, etc. | |
997 | |
998 <br><dt><code>--with-os-directory=DIR</code><dd>Specifies the OS directory for the SDK include directory. This is set to auto | |
999 detect, and is typically 'linux'. | |
1000 | |
1001 <br><dt><code>--with-origin-name=NAME</code><dd>Specifies the JPackage origin name. This defaults to the 'gcj' in | |
1002 java-1.5.0-gcj. | |
1003 | |
1004 <br><dt><code>--with-arch-suffix=SUFFIX</code><dd>Specifies the suffix for the sdk directory. Defaults to the empty string. | |
1005 Examples include '.x86_64' in 'java-1.5.0-gcj-1.5.0.0.x86_64'. | |
1006 | |
1007 <br><dt><code>--with-jvm-root-dir=DIR</code><dd>Specifies where to install the SDK. Default is $(prefix)/lib/jvm. | |
1008 | |
1009 <br><dt><code>--with-jvm-jar-dir=DIR</code><dd>Specifies where to install jars. Default is $(prefix)/lib/jvm-exports. | |
1010 | |
1011 <br><dt><code>--with-python-dir=DIR</code><dd>Specifies where to install the Python modules used for aot-compile. DIR should | |
1012 not include the prefix used in installation. For example, if the Python modules | |
1013 are to be installed in /usr/lib/python2.5/site-packages, then | |
1014 –with-python-dir=/lib/python2.5/site-packages should be passed. If this is | |
1015 not specified, then the Python modules are installed in $(prefix)/share/python. | |
1016 | |
1017 <br><dt><code>--enable-aot-compile-rpm</code><dd>Adds aot-compile-rpm to the list of installed scripts. | |
1018 | |
1019 <dl> | |
1020 <dt><code>ansi</code><dd>Use the single-byte <code>char</code> and the Win32 A functions natively, | |
1021 translating to and from UNICODE when using these functions. If | |
1022 unspecified, this is the default. | |
1023 | |
1024 <br><dt><code>unicows</code><dd>Use the <code>WCHAR</code> and Win32 W functions natively. Adds | |
1025 <code>-lunicows</code> to <samp><span class="file">libgcj.spec</span></samp> to link with ‘<samp><span class="samp">libunicows</span></samp>’. | |
1026 <samp><span class="file">unicows.dll</span></samp> needs to be deployed on Microsoft Windows 9X machines | |
1027 running built executables. <samp><span class="file">libunicows.a</span></samp>, an open-source | |
1028 import library around Microsoft's <code>unicows.dll</code>, is obtained from | |
1029 <a href="http://libunicows.sourceforge.net/">http://libunicows.sourceforge.net/</a>, which also gives details | |
1030 on getting <samp><span class="file">unicows.dll</span></samp> from Microsoft. | |
1031 | |
1032 <br><dt><code>unicode</code><dd>Use the <code>WCHAR</code> and Win32 W functions natively. Does <em>not</em> | |
1033 add <code>-lunicows</code> to <samp><span class="file">libgcj.spec</span></samp>. The built executables will | |
1034 only run on Microsoft Windows NT and above. | |
1035 </dl> | |
1036 </dl> | |
1037 | |
1038 <h5 class="subsubheading"><a name="TOC6"></a>AWT-Specific Options</h5> | |
1039 | |
1040 <dl> | |
1041 <dt><code>--with-x</code><dd>Use the X Window System. | |
1042 | |
1043 <br><dt><code>--enable-java-awt=PEER(S)</code><dd>Specifies the AWT peer library or libraries to build alongside | |
1044 ‘<samp><span class="samp">libgcj</span></samp>’. If this option is unspecified or disabled, AWT | |
1045 will be non-functional. Current valid values are <samp><span class="option">gtk</span></samp> and | |
1046 <samp><span class="option">xlib</span></samp>. Multiple libraries should be separated by a | |
1047 comma (i.e. <samp><span class="option">--enable-java-awt=gtk,xlib</span></samp>). | |
1048 | |
1049 <br><dt><code>--enable-gtk-cairo</code><dd>Build the cairo Graphics2D implementation on GTK. | |
1050 | |
1051 <br><dt><code>--enable-java-gc=TYPE</code><dd>Choose garbage collector. Defaults to <samp><span class="option">boehm</span></samp> if unspecified. | |
1052 | |
1053 <br><dt><code>--disable-gtktest</code><dd>Do not try to compile and run a test GTK+ program. | |
1054 | |
1055 <br><dt><code>--disable-glibtest</code><dd>Do not try to compile and run a test GLIB program. | |
1056 | |
1057 <br><dt><code>--with-libart-prefix=PFX</code><dd>Prefix where libart is installed (optional). | |
1058 | |
1059 <br><dt><code>--with-libart-exec-prefix=PFX</code><dd>Exec prefix where libart is installed (optional). | |
1060 | |
1061 <br><dt><code>--disable-libarttest</code><dd>Do not try to compile and run a test libart program. | |
1062 | |
1063 </dl> | |
1064 | |
1065 <p><hr /> | |
1066 <p><a href="./index.html">Return to the GCC Installation page</a> | |
1067 | |
1068 <!-- ***Building**************************************************************** --> | |
1069 <!-- ***Testing***************************************************************** --> | |
1070 <!-- ***Final install*********************************************************** --> | |
1071 <!-- ***Binaries**************************************************************** --> | |
1072 <!-- ***Specific**************************************************************** --> | |
1073 <!-- ***Old documentation****************************************************** --> | |
1074 <!-- ***GFDL******************************************************************** --> | |
1075 <!-- *************************************************************************** --> | |
1076 <!-- Part 6 The End of the Document --> | |
1077 </body></html> | |
1078 |