]>
Commit | Line | Data |
---|---|---|
1 | \input texinfo.tex @c -*-texinfo-*- | |
2 | @c @ifnothtml | |
3 | @c %**start of header | |
4 | @setfilename install.info | |
5 | @settitle Installing GCC | |
6 | @setchapternewpage odd | |
7 | @c %**end of header | |
8 | @c @end ifnothtml | |
9 | ||
10 | @c Specify title for specific html page | |
11 | @ifset indexhtml | |
12 | @settitle Installing GCC | |
13 | @end ifset | |
14 | @ifset specifichtml | |
15 | @settitle Host/Target specific installation notes for GCC | |
16 | @end ifset | |
17 | @ifset downloadhtml | |
18 | @settitle Downloading GCC | |
19 | @end ifset | |
20 | @ifset configurehtml | |
21 | @settitle Installing GCC: Configuration | |
22 | @end ifset | |
23 | @ifset buildhtml | |
24 | @settitle Installing GCC: Building | |
25 | @end ifset | |
26 | @ifset testhtml | |
27 | @settitle Installing GCC: Testing | |
28 | @end ifset | |
29 | @ifset finalinstallhtml | |
30 | @settitle Installing GCC: Final installation | |
31 | @end ifset | |
32 | @ifset binarieshtml | |
33 | @settitle Installing GCC: Binaries | |
34 | @end ifset | |
35 | ||
36 | @c Copyright (C) 2001 Free Software Foundation, Inc. | |
37 | @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com | |
38 | ||
39 | @c Include everything if we're not making html | |
40 | @ifnothtml | |
41 | @set indexhtml | |
42 | @set specifichtml | |
43 | @set downloadhtml | |
44 | @set configurehtml | |
45 | @set buildhtml | |
46 | @set testhtml | |
47 | @set finalinstallhtml | |
48 | @set binarieshtml | |
49 | @end ifnothtml | |
50 | ||
51 | @c Part 2 Summary Description and Copyright | |
52 | @ifinfo | |
53 | ||
54 | Copyright @copyright{} 2001 Free Software Foundation, Inc. | |
55 | @end ifinfo | |
56 | ||
57 | @c Part 3 Titlepage and Copyright | |
58 | @titlepage | |
59 | @sp 10 | |
60 | @comment The title is printed in a large font. | |
61 | @center @titlefont{Installing GCC} | |
62 | ||
63 | @c The following two commands start the copyright page. | |
64 | @page | |
65 | @vskip 0pt plus 1filll | |
66 | Copyright @copyright{} 2001 Free Software Foundation, Inc. | |
67 | @end titlepage | |
68 | ||
69 | @c Part 4 Top node and Master Menu | |
70 | @ifinfo | |
71 | @node Top, , , (dir) | |
72 | @comment node-name, next, Previous, up | |
73 | ||
74 | @menu | |
75 | * Installing GCC:: This document describes the generic installation | |
76 | procedure for GCC as well as detailing some target | |
77 | specific installation instructions. | |
78 | ||
79 | * Specific:: Host/target specific installation notes for GCC. | |
80 | * Binaries:: Where to get pre-compiled binaries. | |
81 | ||
82 | * Concept Index:: This index has two entries. | |
83 | @end menu | |
84 | @end ifinfo | |
85 | ||
86 | @c Part 5 The Body of the Document | |
87 | @c ***Installing GCC********************************************************** | |
88 | @ifnothtml | |
89 | @comment node-name, next, previous, up | |
90 | @node Installing GCC, Binaries, , Top | |
91 | @end ifnothtml | |
92 | @ifset indexhtml | |
93 | @html | |
94 | <h1 align="center">Installing GCC</h1> | |
95 | @end html | |
96 | @ifnothtml | |
97 | @chapter Installing GCC | |
98 | @end ifnothtml | |
99 | ||
100 | The latest version of this document is always available at | |
101 | @uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}. | |
102 | ||
103 | This document describes the generic installation procedure for GCC as well | |
104 | as detailing some target specific installation instructions. | |
105 | ||
106 | GCC includes several components that previously were separate distributions | |
107 | with their own installation instructions. This document supersedes all | |
108 | package specific installation instructions. | |
109 | ||
110 | @emph{Before} starting the build/install procedure please check the | |
111 | @ifnothtml | |
112 | @ref{Specific, host/target specific installation notes}. | |
113 | @end ifnothtml | |
114 | @ifnotinfo | |
115 | @uref{specific.html,,host/target specific installation notes}. | |
116 | @end ifnotinfo | |
117 | We recommend you browse the entire generic installation instructions before | |
118 | you proceed. | |
119 | ||
120 | The installation procedure itself is broken into five steps. | |
121 | ||
122 | @ifinfo | |
123 | @menu | |
124 | * Downloading the source:: | |
125 | * Configuration:: | |
126 | * Building:: | |
127 | * Testing:: (optional) | |
128 | * Final install:: | |
129 | @end menu | |
130 | @end ifinfo | |
131 | @ifnotinfo | |
132 | @enumerate | |
133 | @item | |
134 | @uref{download.html,,Downloading the source} | |
135 | @item | |
136 | @uref{configure.html,,Configuration} | |
137 | @item | |
138 | @uref{build.html,,Building} | |
139 | @item | |
140 | @uref{test.html,,Testing} (optional) | |
141 | @item | |
142 | @uref{finalinstall.html,,Final install} | |
143 | @end enumerate | |
144 | @end ifnotinfo | |
145 | ||
146 | Please note that GCC does not support @samp{make uninstall} and probably | |
147 | won't do so in the near future as this would open a can of worms. Instead, | |
148 | we suggest that you install GCC into a directory of its own and simply | |
149 | remove that directory when you do not need that specific version of GCC | |
150 | any longer, and, if shared libraries are installed there as well, no | |
151 | more binaries exist that use them. | |
152 | ||
153 | @html | |
154 | <hr> | |
155 | <p> | |
156 | @end html | |
157 | @ifhtml | |
158 | @uref{./index.html,,Return to the GCC Installation page} | |
159 | @end ifhtml | |
160 | @end ifset | |
161 | ||
162 | @c ***Downloading the source************************************************** | |
163 | @ifnothtml | |
164 | @comment node-name, next, previous, up | |
165 | @node Downloading the source, Configuration, , Installing GCC | |
166 | @end ifnothtml | |
167 | @ifset downloadhtml | |
168 | @html | |
169 | <h1 align="center">Downloading GCC</h1> | |
170 | @end html | |
171 | @ifnothtml | |
172 | @chapter Downloading GCC | |
173 | @end ifnothtml | |
174 | @cindex Downloading GCC | |
175 | @cindex Downloading the Source | |
176 | ||
177 | GCC is distributed via @uref{http://gcc.gnu.org/cvs.html,,CVS} and FTP | |
178 | tarballs compressed with @command{gzip} or | |
179 | @command{bzip2}. It is possible to download a full distribution or specific | |
180 | components. | |
181 | ||
182 | Please refer to our @uref{http://gcc.gnu.org/releases.html,,releases web page} | |
183 | for information on how to obtain GCC@. | |
184 | ||
185 | The full distribution includes the C, C++, Objective-C, Fortran, Java, | |
186 | and CHILL compilers. The full distribution also includes runtime libraries | |
187 | for C++, Objective-C, Fortran, Java and CHILL. (GCC 3.0 does not | |
188 | include CHILL.) In GCC 3.0 and later versions, GNU compiler testsuites | |
189 | are also included in the full distribution. | |
190 | ||
191 | If you choose to download specific components, you must download the core | |
192 | GCC distribution plus any language specific distributions you wish to | |
193 | use. The core distribution includes the C language front end as well as the | |
194 | shared components. Each language has a tarball which includes the language | |
195 | front end as well as the language runtime (when appropriate). | |
196 | ||
197 | Unpack the core distribution as well as any language specific | |
198 | distributions in the same directory. | |
199 | ||
200 | If you also intend to build binutils (either to upgrade an existing | |
201 | installation or for use in place of the corresponding tools of your | |
202 | OS), unpack the binutils distribution either in the same directory or | |
203 | a separate one. In the latter case, add symbolic links to any | |
204 | components of the binutils you intend to build alongside the compiler | |
205 | (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld}, | |
206 | @file{opcodes}, @dots{}) to the directory containing the GCC sources. | |
207 | ||
208 | @html | |
209 | <hr> | |
210 | <p> | |
211 | @end html | |
212 | @ifhtml | |
213 | @uref{./index.html,,Return to the GCC Installation page} | |
214 | @end ifhtml | |
215 | @end ifset | |
216 | ||
217 | @c ***Configuration*********************************************************** | |
218 | @ifnothtml | |
219 | @comment node-name, next, previous, up | |
220 | @node Configuration, Building, Downloading the source, Installing GCC | |
221 | @end ifnothtml | |
222 | @ifset configurehtml | |
223 | @html | |
224 | <h1 align="center">Installing GCC: Configuration</h1> | |
225 | @end html | |
226 | @ifnothtml | |
227 | @chapter Installing GCC: Configuration | |
228 | @end ifnothtml | |
229 | @cindex Configuration | |
230 | @cindex Installing GCC: Configuration | |
231 | ||
232 | Like most GNU software, GCC must be configured before it can be built. | |
233 | This document describes the recommended configuration procedure | |
234 | for both native and cross targets. | |
235 | ||
236 | We use @var{srcdir} to refer to the toplevel source directory for | |
237 | GCC; we use @var{objdir} to refer to the toplevel build/object directory. | |
238 | ||
239 | If you obtained the sources via CVS, @var{srcdir} must refer to the top | |
240 | @file{gcc} directory, the one where the @file{MAINTAINERS} can be found, | |
241 | and not its @file{gcc} subdirectory, otherwise the build will fail. | |
242 | ||
243 | First, we @strong{highly} recommend that GCC be built into a | |
244 | separate directory than the sources which does @strong{not} reside | |
245 | within the source tree. This is how we generally build GCC; building | |
246 | where @var{srcdir} == @var{objdir} should still work, but doesn't | |
247 | get extensive testing; building where @var{objdir} is a subdirectory | |
248 | of @var{srcdir} is unsupported. | |
249 | ||
250 | If you have previously built GCC in the same directory for a | |
251 | different target machine, do @samp{make distclean} to delete all files | |
252 | that might be invalid. One of the files this deletes is | |
253 | @file{Makefile}; if @samp{make distclean} complains that @file{Makefile} | |
254 | does not exist, it probably means that the directory is already suitably | |
255 | clean. However, with the recommended method of building in a separate | |
256 | @var{objdir}, you should simply use a different @var{objdir} for each | |
257 | target. | |
258 | ||
259 | Second, when configuring a native system, either @command{cc} or | |
260 | @command{gcc} must be in your path or you must set @env{CC} in | |
261 | your environment before running configure. Otherwise the configuration | |
262 | scripts may fail. | |
263 | ||
264 | Note that the bootstrap compiler and the resulting GCC must be link | |
265 | compatible, else the bootstrap will fail with linker errors about | |
266 | incompatible object file formats. Several multilibed targets are | |
267 | affected by this requirement, see @ref{Specific, host/target specific | |
268 | installation notes} for details. | |
269 | ||
270 | To configure GCC: | |
271 | ||
272 | @example | |
273 | % mkdir @var{objdir} | |
274 | % cd @var{objdir} | |
275 | % @var{srcdir}/configure [@var{options}] [@var{target}] | |
276 | @end example | |
277 | ||
278 | ||
279 | @heading Target specification | |
280 | @itemize @bullet | |
281 | @item | |
282 | GCC has code to correctly determine the correct value for @var{target} | |
283 | for nearly all native systems. Therefore, we highly recommend you not | |
284 | provide a configure target when configuring a native compiler. | |
285 | ||
286 | @item | |
287 | @var{target} must be specified as @option{--target=@var{target}} | |
288 | when configuring a cross compiler; examples of valid targets would be | |
289 | i960-rtems, m68k-coff, sh-elf, etc. | |
290 | ||
291 | @item | |
292 | Specifying just @var{target} instead of @option{--target=@var{target}} | |
293 | implies that the host defaults to @var{target}. | |
294 | @end itemize | |
295 | ||
296 | ||
297 | @heading Options specification | |
298 | ||
299 | Use @var{options} to override several configure time options for | |
300 | GCC@. A partial list of supported @var{options}: | |
301 | ||
302 | @table @code | |
303 | @item --prefix=@var{dirname} | |
304 | Specify the toplevel installation | |
305 | directory. This is the recommended way to install the tools into a directory | |
306 | other than the default. The toplevel installation directory defaults to | |
307 | @file{/usr/local}. | |
308 | ||
309 | We @strong{highly} recommend against @var{dirname} being the same or a | |
310 | subdirectory of @var{objdir} or vice versa. | |
311 | ||
312 | These additional options control where certain parts of the distribution | |
313 | are installed. Normally you should not need to use these options. | |
314 | @table @code | |
315 | ||
316 | @item --exec-prefix=@var{dirname} | |
317 | Specify the toplevel installation directory for architecture-dependent | |
318 | files. The default is @file{@var{prefix}}. | |
319 | ||
320 | @item --bindir=@var{dirname} | |
321 | Specify the installation directory for the executables called by users | |
322 | (such as @command{gcc} and @command{g++}). The default is | |
323 | @file{@var{exec-prefix}/bin}. | |
324 | ||
325 | @item --libdir=@var{dirname} | |
326 | Specify the installation directory for object code libraries and | |
327 | internal parts of GCC@. The default is @file{@var{exec-prefix}/lib}. | |
328 | ||
329 | @item --with-slibdir=@var{dirname} | |
330 | Specify the installation directory for the shared libgcc library. The | |
331 | default is @file{@var{libdir}}. | |
332 | ||
333 | @item --infodir=@var{dirname} | |
334 | Specify the installation directory for documentation in info format. | |
335 | The default is @file{@var{prefix}/info}. | |
336 | ||
337 | @item --mandir=@var{dirname} | |
338 | Specify the installation directory for manual pages. The default is | |
339 | @file{@var{prefix}/man}. (Note that the manual pages are only extracts from | |
340 | the full GCC manuals, which are provided in Texinfo format. The | |
341 | @command{g77} manpage is unmaintained and may be out of date; the others | |
342 | are derived by an automatic conversion process from parts of the full | |
343 | manual.) | |
344 | ||
345 | @item --with-gxx-include-dir=@var{dirname} | |
346 | Specify | |
347 | the installation directory for G++ header files. The default is | |
348 | @file{@var{prefix}/include/g++-v3}. | |
349 | ||
350 | @end table | |
351 | ||
352 | @item --with-local-prefix=@var{dirname} | |
353 | Specify the | |
354 | installation directory for local include files. The default is | |
355 | @file{/usr/local}. Specify this option if you want the compiler to | |
356 | search directory @file{@var{dirname}/include} for locally installed | |
357 | header files @emph{instead} of @file{/usr/local/include}. | |
358 | ||
359 | You should specify @option{--with-local-prefix} @strong{only} if your | |
360 | site has a different convention (not @file{/usr/local}) for where to put | |
361 | site-specific files. | |
362 | ||
363 | The default value for @option{--with-local-prefix} is @file{/usr/local} | |
364 | regardless of the value of @option{--prefix}. Specifying | |
365 | @option{--prefix} has no effect on which directory GCC searches for | |
366 | local header files. This may seem counterintuitive, but actually it is | |
367 | logical. | |
368 | ||
369 | The purpose of @option{--prefix} is to specify where to @emph{install | |
370 | GCC}. The local header files in @file{/usr/local/include}---if you put | |
371 | any in that directory---are not part of GCC@. They are part of other | |
372 | programs---perhaps many others. (GCC installs its own header files in | |
373 | another directory which is based on the @option{--prefix} value.) | |
374 | ||
375 | @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}! | |
376 | The directory you use for @option{--with-local-prefix} @strong{must not} | |
377 | contain any of the system's standard header files. If it did contain | |
378 | them, certain programs would be miscompiled (including GNU Emacs, on | |
379 | certain targets), because this would override and nullify the header | |
380 | file corrections made by the @code{fixincludes} script. | |
381 | ||
382 | Indications are that people who use this option use it based on mistaken | |
383 | ideas of what it is for. People use it as if it specified where to | |
384 | install part of GCC@. Perhaps they make this assumption because | |
385 | installing GCC creates the directory. | |
386 | ||
387 | @item --enable-shared[=@var{package}[,@dots{}]] | |
388 | Build shared versions of libraries, if shared libraries are supported on | |
389 | the target platform. Unlike GCC 2.95.x and earlier, shared libraries | |
390 | are enabled by default on all platforms that support shared libraries, | |
391 | except for @samp{libobjc} which is built as a static library only by | |
392 | default. | |
393 | ||
394 | If a list of packages is given as an argument, build shared libraries | |
395 | only for the listed packages. For other packages, only static libraries | |
396 | will be built. Package names currently recognized in the GCC tree are | |
397 | @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not | |
398 | @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc} and | |
399 | @samp{libjava}. Note that @samp{libobjc} does not recognize itself by | |
400 | any name, so, if you list package names in @option{--enable-shared}, | |
401 | you will only get static Objective-C libraries. @samp{libf2c} and | |
402 | @samp{libiberty} do not support shared libraries at all. | |
403 | ||
404 | Use @option{--disable-shared} to build only static libraries. Note that | |
405 | @option{--disable-shared} does not accept a list of package names as | |
406 | argument, only @option{--enable-shared} does. | |
407 | ||
408 | @item @anchor{with-gnu-as}--with-gnu-as | |
409 | Specify that the compiler should assume that the | |
410 | assembler it finds is the GNU assembler. However, this does not modify | |
411 | the rules to find an assembler and will result in confusion if found | |
412 | assembler is not actually the GNU assembler. (Confusion will also | |
413 | result if the compiler finds the GNU assembler but has not been | |
414 | configured with @option{--with-gnu-as}.) If you have more than one | |
415 | assembler installed on your system, you may want to use this option in | |
416 | connection with @option{--with-as=@var{pathname}}. | |
417 | ||
418 | The systems where it makes a difference whether you use the GNU assembler are | |
419 | @samp{hppa1.0-@var{any}-@var{any}}, @samp{hppa1.1-@var{any}-@var{any}}, | |
420 | @samp{i386-@var{any}-sysv}, @samp{i386-@var{any}-isc}, | |
421 | @samp{i860-@var{any}-bsd}, @samp{m68k-bull-sysv}, | |
422 | @samp{m68k-hp-hpux}, @samp{m68k-sony-bsd}, | |
423 | @samp{m68k-altos-sysv}, @samp{m68000-hp-hpux}, | |
424 | @samp{m68000-att-sysv}, @samp{@var{any}-lynx-lynxos}, | |
425 | and @samp{mips-@var{any}}. | |
426 | On any other system, @option{--with-gnu-as} has no effect. | |
427 | ||
428 | On the systems listed above (except for the HP-PA, for ISC on the | |
429 | 386, and for @samp{mips-sgi-irix5.*}), if you use the GNU assembler, | |
430 | you should also use the GNU linker (and specify @option{--with-gnu-ld}). | |
431 | ||
432 | @item --with-as=@var{pathname} | |
433 | Specify that the | |
434 | compiler should use the assembler pointed to by @var{pathname}, rather | |
435 | than the one found by the standard rules to find an assembler, which | |
436 | are: | |
437 | @itemize @bullet | |
438 | @item | |
439 | Check the | |
440 | @file{@var{exec_prefix}/lib/gcc-lib/@var{target}/@var{version}} | |
441 | directory, where @var{exec_prefix} defaults to @var{prefix} which | |
442 | defaults to @file{/usr/local} unless overridden by the | |
443 | @option{--prefix=@var{pathname}} switch described above. @var{target} is the | |
444 | target system triple, such as @var{sparc-sun-solaris2.7}, and | |
445 | @var{version} denotes the GCC version, such as 3.0. | |
446 | @item | |
447 | Check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on | |
448 | Sun Solaris). | |
449 | @end itemize | |
450 | Note that these rules do not check for the value of @env{PATH}. You may | |
451 | want to use @option{--with-as} if no assembler is installed in the | |
452 | directories listed above, or if you have multiple assemblers installed | |
453 | and want to choose one that is not found by the above rules. | |
454 | ||
455 | @item @anchor{with-gnu-ld}--with-gnu-ld | |
456 | Same as @uref{#with-gnu-as,,@option{--with-gnu-as}} | |
457 | but for linker. | |
458 | ||
459 | ||
460 | @item --with-ld=@var{pathname} | |
461 | Same as | |
462 | @option{--with-as}, but for the linker. | |
463 | ||
464 | @item --with-stabs | |
465 | Specify that stabs debugging | |
466 | information should be used instead of whatever format the host normally | |
467 | uses. Normally GCC uses the same debug format as the host system. | |
468 | ||
469 | On MIPS based systems and on Alphas, you must specify whether you want | |
470 | GCC to create the normal ECOFF debugging format, or to use BSD-style | |
471 | stabs passed through the ECOFF symbol table. The normal ECOFF debug | |
472 | format cannot fully handle languages other than C@. BSD stabs format can | |
473 | handle other languages, but it only works with the GNU debugger GDB@. | |
474 | ||
475 | Normally, GCC uses the ECOFF debugging format by default; if you | |
476 | prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@. | |
477 | ||
478 | No matter which default you choose when you configure GCC, the user | |
479 | can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly | |
480 | the debug format for a particular compilation. | |
481 | ||
482 | @option{--with-stabs} is meaningful on the ISC system on the 386, also, if | |
483 | @option{--with-gas} is used. It selects use of stabs debugging | |
484 | information embedded in COFF output. This kind of debugging information | |
485 | supports C++ well; ordinary COFF debugging information does not. | |
486 | ||
487 | @option{--with-stabs} is also meaningful on 386 systems running SVR4. It | |
488 | selects use of stabs debugging information embedded in ELF output. The | |
489 | C++ compiler currently (2.6.0) does not support the DWARF debugging | |
490 | information normally used on 386 SVR4 platforms; stabs provide a | |
491 | workable alternative. This requires gas and gdb, as the normal SVR4 | |
492 | tools can not generate or interpret stabs. | |
493 | ||
494 | @item --disable-multilib | |
495 | Specify that multiple target | |
496 | libraries to support different target variants, calling | |
497 | conventions, etc should not be built. The default is to build a | |
498 | predefined set of them. | |
499 | ||
500 | @item --enable-threads | |
501 | Specify that the target | |
502 | supports threads. This affects the Objective-C compiler and runtime | |
503 | library, and exception handling for other languages like C++ and Java. | |
504 | On some systems, this is the default. | |
505 | ||
506 | In general, the best (and, in many cases, the only known) threading | |
507 | model available will be configured for use. Beware that on some | |
508 | systems, gcc has not been taught what threading models are generally | |
509 | available for the system. In this case, @option{--enable-threads} is an | |
510 | alias for @option{--enable-threads=single}. | |
511 | ||
512 | @item --disable-threads | |
513 | Specify that threading support should be disabled for the system. | |
514 | This is an alias for @option{--enable-threads=single}. | |
515 | ||
516 | @item --enable-threads=@var{lib} | |
517 | Specify that | |
518 | @var{lib} is the thread support library. This affects the Objective-C | |
519 | compiler and runtime library, and exception handling for other languages | |
520 | like C++ and Java. The possibilities for @var{lib} are: | |
521 | ||
522 | @table @code | |
523 | @item aix | |
524 | AIX thread support. | |
525 | @item dce | |
526 | DCE thread support. | |
527 | @item mach | |
528 | Generic MACH thread support, known to work on NeXTSTEP@. (Please note | |
529 | that the file needed to support this configuration, @file{gthr-mach.h}, is | |
530 | missing and thus this setting will cause a known bootstrap failure.) | |
531 | @item no | |
532 | This is an alias for @samp{single}. | |
533 | @item posix | |
534 | Generic POSIX thread support. | |
535 | @item pthreads | |
536 | Same as @samp{posix} on arm*-*-linux*, *-*-chorusos* and *-*-freebsd* | |
537 | only. A future release of gcc might remove this alias or extend it | |
538 | to all platforms. | |
539 | @item rtems | |
540 | RTEMS thread support. | |
541 | @item single | |
542 | Disable thread support, should work for all platforms. | |
543 | @item solaris | |
544 | Sun Solaris 2 thread support. | |
545 | @item vxworks | |
546 | VxWorks thread support. | |
547 | @item win32 | |
548 | Microsoft Win32 API thread support. | |
549 | @end table | |
550 | ||
551 | @item --with-cpu=@var{cpu} | |
552 | Specify which cpu variant the | |
553 | compiler should generate code for by default. This is currently | |
554 | only supported on the some ports, specifically arm, powerpc, and | |
555 | SPARC@. If configure does not recognize the model name (e.g.@: arm700, | |
556 | 603e, or ultrasparc) you provide, please check the configure script | |
557 | for a complete list of supported models. | |
558 | ||
559 | @item --enable-target-optspace | |
560 | Specify that target | |
561 | libraries should be optimized for code space instead of code speed. | |
562 | This is the default for the m32r platform. | |
563 | ||
564 | @item --disable-cpp | |
565 | Specify that a user visible @command{cpp} program should not be installed. | |
566 | ||
567 | @item --with-cpp-install-dir=@var{dirname} | |
568 | Specify that the user visible @command{cpp} program should be installed | |
569 | in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}. | |
570 | ||
571 | @item --enable-maintainer-mode | |
572 | The build rules that | |
573 | regenerate the GCC master message catalog @file{gcc.pot} are normally | |
574 | disabled. This is because it can only be rebuilt if the complete source | |
575 | tree is present. If you have changed the sources and want to rebuild the | |
576 | catalog, configuring with @option{--enable-maintainer-mode} will enable | |
577 | this. Note that you need a recent version of the @code{gettext} tools | |
578 | to do so. | |
579 | ||
580 | @item --enable-version-specific-runtime-libs | |
581 | Specify | |
582 | that runtime libraries should be installed in the compiler specific | |
583 | subdirectory (@file{@var{libsubdir}}) rather than the usual places. In | |
584 | addition, @samp{libstdc++}'s include files will be installed in | |
585 | @file{@var{libsubdir}/include/g++} unless you overruled it by using | |
586 | @option{--with-gxx-include-dir=@var{dirname}}. Using this option is | |
587 | particularly useful if you intend to use several versions of GCC in | |
588 | parallel. This is currently supported by @samp{libf2c} and | |
589 | @samp{libstdc++}, and is the default for @samp{libobjc} which cannot be | |
590 | changed in this case. | |
591 | ||
592 | @item --enable-languages=@var{lang1},@var{lang2},@dots{} | |
593 | Specify that only a particular subset of compilers and | |
594 | their runtime libraries should be built. For a list of valid values for | |
595 | @var{langN} you can issue the following command in the | |
596 | @file{gcc} directory of your GCC source tree:@* | |
597 | @example | |
598 | grep language= */config-lang.in | |
599 | @end example | |
600 | Currently, you can use any of the following: | |
601 | @code{c}, @code{c++}, @code{f77}, @code{java} and @code{objc}. | |
602 | @code{CHILL} is not currently maintained, and will almost | |
603 | certainly fail to compile.@* | |
604 | If you do not pass this flag, all languages available in the @file{gcc} | |
605 | sub-tree will be configured. Re-defining @code{LANGUAGES} when calling | |
606 | @samp{make bootstrap} @strong{does not} work anymore, as those | |
607 | language sub-directories might not have been configured! | |
608 | ||
609 | @item --disable-libgcj | |
610 | Specify that the run-time libraries | |
611 | used by GCJ should not be built. This is useful in case you intend | |
612 | to use GCJ with some other run-time, or you're going to install it | |
613 | separately, or it just happens not to build on your particular | |
614 | machine. In general, if the Java front end is enabled, the GCJ | |
615 | libraries will be enabled too, unless they're known to not work on | |
616 | the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you | |
617 | may need to port it; in this case, before modifying the top-level | |
618 | @file{configure.in} so that @samp{libgcj} is enabled by default on this platform, | |
619 | you may use @option{--enable-libgcj} to override the default. | |
620 | ||
621 | @item --with-dwarf2 | |
622 | Specify that the compiler should | |
623 | use DWARF 2 debugging information as the default. | |
624 | ||
625 | @item --enable-win32-registry | |
626 | @itemx --enable-win32-registry=@var{key} | |
627 | @itemx --disable-win32-registry | |
628 | The @option{--enable-win32-registry} option enables Windows-hosted GCC | |
629 | to look up installations paths in the registry using the following key: | |
630 | ||
631 | @smallexample | |
632 | @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}} | |
633 | @end smallexample | |
634 | ||
635 | @var{key} defaults to GCC version number, and can be overridden by the | |
636 | @option{--enable-win32-registry=@var{key}} option. Vendors and distributors | |
637 | who use custom installers are encouraged to provide a different key, | |
638 | perhaps one comprised of vendor name and GCC version number, to | |
639 | avoid conflict with existing installations. This feature is enabled | |
640 | by default, and can be disabled by @option{--disable-win32-registry} | |
641 | option. This option has no effect on the other hosts. | |
642 | ||
643 | @item --nfp | |
644 | Specify that the machine does not have a floating point unit. This | |
645 | option only applies to @samp{m68k-sun-sunos@var{n}} and | |
646 | @samp{m68k-isi-bsd}. On any other system, @option{--nfp} has no effect. | |
647 | ||
648 | @item --enable-checking | |
649 | @itemx --enable-checking=@var{list} | |
650 | When you specify this option, the compiler is built to perform checking | |
651 | of tree node types when referencing fields of that node, and some other | |
652 | internal consistency checks. This does not change the generated code, | |
653 | but adds error checking within the compiler. This will slow down the | |
654 | compiler and may only work properly if you are building the compiler | |
655 | with GCC@. This is on by default when building from CVS or snapshots, | |
656 | but off for releases. More control over the checks may be had by | |
657 | specifying @var{list}; the categories of checks available are | |
658 | @samp{misc}, @samp{tree}, @samp{gc}, @samp{rtl} and @samp{gcac}. The | |
659 | default when @var{list} is not specified is @samp{misc,tree,gc}; the | |
660 | checks @samp{rtl} and @samp{gcac} are very expensive. | |
661 | ||
662 | @item --enable-nls | |
663 | @itemx --disable-nls | |
664 | The @option{--enable-nls} option enables Native Language Support (NLS), | |
665 | which lets GCC output diagnostics in languages other than American | |
666 | English. Native Language Support is enabled by default if not doing a | |
667 | canadian cross build. The @option{--disable-nls} option disables NLS@. | |
668 | ||
669 | @item --with-included-gettext | |
670 | If NLS is enabled, the @option{--with-included-gettext} option causes the build | |
671 | procedure to prefer its copy of GNU @command{gettext}. | |
672 | ||
673 | @item --with-catgets | |
674 | If NLS is enabled, and if the host lacks @code{gettext} but has the | |
675 | inferior @code{catgets} interface, the GCC build procedure normally | |
676 | ignores @code{catgets} and instead uses GCC's copy of the GNU | |
677 | @code{gettext} library. The @option{--with-catgets} option causes the | |
678 | build procedure to use the host's @code{catgets} in this situation. | |
679 | @end table | |
680 | ||
681 | Some options which only apply to building cross compilers: | |
682 | @table @code | |
683 | @item --with-headers=@var{dir} | |
684 | Specifies a directory | |
685 | which has target include files. | |
686 | @emph{This options is required} when building a cross | |
687 | compiler, if @file{@var{prefix}/@var{target}/sys-include} doesn't pre-exist. | |
688 | These include files will be copied into the @file{gcc} install directory. | |
689 | Fixincludes will be run on these files to make them compatible with | |
690 | GCC. | |
691 | @item --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}'' | |
692 | Specifies a list of directories which contain the target runtime | |
693 | libraries. These libraries will be copied into the @file{gcc} install | |
694 | directory. | |
695 | @item --with-newlib | |
696 | Specifies that @samp{newlib} is | |
697 | being used as the target C library. This causes @code{__eprintf} to be | |
698 | omitted from @file{libgcc.a} on the assumption that it will be provided by | |
699 | @samp{newlib}. | |
700 | @end table | |
701 | ||
702 | Note that each @option{--enable} option has a corresponding | |
703 | @option{--disable} option and that each @option{--with} option has a | |
704 | corresponding @option{--without} option. | |
705 | ||
706 | @html | |
707 | <hr> | |
708 | <p> | |
709 | @end html | |
710 | @ifhtml | |
711 | @uref{./index.html,,Return to the GCC Installation page} | |
712 | @end ifhtml | |
713 | @end ifset | |
714 | ||
715 | @c ***Building**************************************************************** | |
716 | @ifnothtml | |
717 | @comment node-name, next, previous, up | |
718 | @node Building, Testing, Configuration, Installing GCC | |
719 | @end ifnothtml | |
720 | @ifset buildhtml | |
721 | @html | |
722 | <h1 align="center">Installing GCC: Building</h1> | |
723 | @end html | |
724 | @ifnothtml | |
725 | @chapter Building | |
726 | @end ifnothtml | |
727 | @cindex Installing GCC: Building | |
728 | ||
729 | Now that GCC is configured, you are ready to build the compiler and | |
730 | runtime libraries. | |
731 | ||
732 | We @strong{highly} recommend that GCC be built using GNU make; | |
733 | other versions may work, then again they might not. | |
734 | ||
735 | (For example, many broken versions of make will fail if you use the | |
736 | recommended setup where @var{objdir} is different from @var{srcdir}. | |
737 | Other broken versions may recompile parts of the compiler when | |
738 | installing the compiler.) | |
739 | ||
740 | Some commands executed when making the compiler may fail (return a | |
741 | non-zero status) and be ignored by @code{make}. These failures, which | |
742 | are often due to files that were not found, are expected, and can safely | |
743 | be ignored. | |
744 | ||
745 | It is normal to have compiler warnings when compiling certain files. | |
746 | Unless you are a GCC developer, you can generally ignore these warnings | |
747 | unless they cause compilation to fail. | |
748 | ||
749 | On certain old systems, defining certain environment variables such as | |
750 | @env{CC} can interfere with the functioning of @command{make}. | |
751 | ||
752 | If you encounter seemingly strange errors when trying to build the | |
753 | compiler in a directory other than the source directory, it could be | |
754 | because you have previously configured the compiler in the source | |
755 | directory. Make sure you have done all the necessary preparations. | |
756 | ||
757 | If you build GCC on a BSD system using a directory stored in an old System | |
758 | V file system, problems may occur in running @code{fixincludes} if the | |
759 | System V file system doesn't support symbolic links. These problems | |
760 | result in a failure to fix the declaration of @code{size_t} in | |
761 | @file{sys/types.h}. If you find that @code{size_t} is a signed type and | |
762 | that type mismatches occur, this could be the cause. | |
763 | ||
764 | The solution is not to use such a directory for building GCC@. | |
765 | ||
766 | When building from CVS or snapshots, or if you modify parser sources, | |
767 | you need the Bison parser generator installed. Any version 1.25 or | |
768 | later should work; older versions may also work. If you do not modify | |
769 | parser sources, releases contain the Bison-generated files and you do | |
770 | not need Bison installed to build them. | |
771 | ||
772 | When building from CVS or snapshots, or if you modify Texinfo | |
773 | documentation, you need version 4.0 or later of Texinfo installed if you | |
774 | want Info documentation to be regenerated. Releases contain Info | |
775 | documentation pre-built for the unmodified documentation in the release. | |
776 | ||
777 | @section Building a native compiler | |
778 | ||
779 | For a native build issue the command @samp{make bootstrap}. This | |
780 | will build the entire GCC system, which includes the following steps: | |
781 | ||
782 | @itemize @bullet | |
783 | @item | |
784 | Build host tools necessary to build the compiler such as texinfo, bison, | |
785 | gperf. | |
786 | ||
787 | @item | |
788 | Build target tools for use by the compiler such as binutils (bfd, | |
789 | binutils, gas, gprof, ld, and opcodes) | |
790 | if they have been individually linked | |
791 | or moved into the top level GCC source tree before configuring. | |
792 | ||
793 | @item | |
794 | Perform a 3-stage bootstrap of the compiler. | |
795 | ||
796 | @item | |
797 | Perform a comparison test of the stage2 and stage3 compilers. | |
798 | ||
799 | @item | |
800 | Build runtime libraries using the stage3 compiler from the previous step. | |
801 | ||
802 | @end itemize | |
803 | ||
804 | If you are short on disk space you might consider @samp{make | |
805 | bootstrap-lean} instead. This is identical to @samp{make | |
806 | bootstrap} except that object files from the stage1 and | |
807 | stage2 of the 3-stage bootstrap of the compiler are deleted as | |
808 | soon as they are no longer needed. | |
809 | ||
810 | ||
811 | If you want to save additional space during the bootstrap and in | |
812 | the final installation as well, you can build the compiler binaries | |
813 | without debugging information with @samp{make CFLAGS='-O' LIBCFLAGS='-g | |
814 | -O2' LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap}. This will save | |
815 | roughly 40% of disk space both for the bootstrap and the final installation. | |
816 | (Libraries will still contain debugging information.) | |
817 | ||
818 | If you wish to use non-default GCC flags when compiling the stage2 and | |
819 | stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing | |
820 | @samp{make bootstrap}. Non-default optimization flags are less well | |
821 | tested here than the default of @samp{-g -O2}, but should still work. | |
822 | In a few cases, you may find that you need to specify special flags such | |
823 | as @option{-msoft-float} here to complete the bootstrap; or, if the | |
824 | native compiler miscompiles the stage1 compiler, you may need to work | |
825 | around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the | |
826 | stage1 compiler that were miscompiled, or by using @samp{make | |
827 | bootstrap4} to increase the number of stages of bootstrap. | |
828 | ||
829 | If you used the flag @option{--enable-languages=@dots{}} to restrict | |
830 | the compilers to be built, only those you've actually enabled will be | |
831 | built. This will of course only build those runtime libraries, for | |
832 | which the particular compiler has been built. Please note, | |
833 | that re-defining @env{LANGUAGES} when calling @samp{make bootstrap} | |
834 | @strong{does not} work anymore! | |
835 | ||
836 | If the comparison of stage2 and stage3 fails, this normally indicates | |
837 | that the stage2 compiler has compiled GCC incorrectly, and is therefore | |
838 | a potentially serious bug which you should investigate and report. (On | |
839 | a few systems, meaningful comparison of object files is impossible; they | |
840 | always appear ``different''. If you encounter this problem, you will | |
841 | need to disable comparison in the @file{Makefile}.) | |
842 | ||
843 | @section Building a cross compiler | |
844 | ||
845 | We recommend reading the | |
846 | @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ} | |
847 | for information about building cross compilers. | |
848 | ||
849 | When building a cross compiler, it is not generally possible to do a | |
850 | 3-stage bootstrap of the compiler. This makes for an interesting problem | |
851 | as parts of GCC can only be built with GCC@. | |
852 | ||
853 | To build a cross compiler, we first recommend building and installing a | |
854 | native compiler. You can then use the native GCC compiler to build the | |
855 | cross compiler. | |
856 | ||
857 | Assuming you have already installed a native copy of GCC and configured | |
858 | your cross compiler, issue the command @command{make}, which performs the | |
859 | following steps: | |
860 | ||
861 | @itemize @bullet | |
862 | @item | |
863 | Build host tools necessary to build the compiler such as texinfo, bison, | |
864 | gperf. | |
865 | ||
866 | @item | |
867 | Build target tools for use by the compiler such as binutils (bfd, | |
868 | binutils, gas, gprof, ld, and opcodes) | |
869 | if they have been individually linked or moved into the top level GCC source | |
870 | tree before configuring. | |
871 | ||
872 | @item | |
873 | Build the compiler (single stage only). | |
874 | ||
875 | @item | |
876 | Build runtime libraries using the compiler from the previous step. | |
877 | @end itemize | |
878 | ||
879 | Note that if an error occurs in any step the make process will exit. | |
880 | ||
881 | @section Building in parallel | |
882 | ||
883 | If you have a multiprocessor system you can use @samp{make bootstrap | |
884 | MAKE="make -j 2" -j 2} or just @samp{make -j 2 bootstrap} | |
885 | for GNU Make 3.79 and above instead of just @samp{make bootstrap} | |
886 | when building GCC@. You can use a bigger number instead of two if | |
887 | you like. In most cases, it won't help to use a number bigger than | |
888 | the number of processors in your machine. | |
889 | ||
890 | @html | |
891 | <hr> | |
892 | <p> | |
893 | @end html | |
894 | @ifhtml | |
895 | @uref{./index.html,,Return to the GCC Installation page} | |
896 | @end ifhtml | |
897 | @end ifset | |
898 | ||
899 | @c ***Testing***************************************************************** | |
900 | @ifnothtml | |
901 | @comment node-name, next, previous, up | |
902 | @node Testing, Final install, Building, Installing GCC | |
903 | @end ifnothtml | |
904 | @ifset testhtml | |
905 | @html | |
906 | <h1 align="center">Installing GCC: Testing</h1> | |
907 | @end html | |
908 | @ifnothtml | |
909 | @chapter Installing GCC: Testing | |
910 | @end ifnothtml | |
911 | @cindex Testing | |
912 | @cindex Installing GCC: Testing | |
913 | @cindex Testsuite | |
914 | ||
915 | Before you install GCC, you might wish to run the testsuite. This | |
916 | step is optional and may require you to download additional software. | |
917 | ||
918 | First, you must have @uref{download.html,,downloaded the testsuites}. | |
919 | The full distribution contains testsuites; only if you downloaded the | |
920 | ``core'' compiler plus any front ends, you do not have the testsuites. | |
921 | ||
922 | Second, you must have a @uref{http://www.gnu.org/software/dejagnu/,,current version of DejaGnu} installed; | |
923 | dejagnu 1.3 is not sufficient. | |
924 | ||
925 | Now you may need specific preparations: | |
926 | ||
927 | @itemize @bullet | |
928 | ||
929 | @item | |
930 | The following environment variables may need to be set appropriately, as in | |
931 | the following example (which assumes that DejaGnu has been installed | |
932 | under @file{/usr/local}): | |
933 | ||
934 | @example | |
935 | TCL_LIBRARY = /usr/local/share/tcl8.0 | |
936 | DEJAGNULIBS = /usr/local/share/dejagnu | |
937 | @end example | |
938 | ||
939 | On systems such as Cygwin, these paths are required to be actual | |
940 | paths, not mounts or links; presumably this is due to some lack of | |
941 | portability in the DejaGnu code. | |
942 | ||
943 | If the directories where @command{runtest} and @command{expect} were | |
944 | installed are in the @env{PATH}, it should not be necessary to set these | |
945 | environment variables. | |
946 | ||
947 | @end itemize | |
948 | ||
949 | Finally, you can run the testsuite (which may take a long time): | |
950 | @example | |
951 | cd @var{objdir}; make -k check | |
952 | @end example | |
953 | ||
954 | The testing process will try to test as many components in the GCC | |
955 | distribution as possible, including the C, C++, Objective-C and Fortran | |
956 | compilers as well as the C++ and Java runtime libraries. | |
957 | ||
958 | @section How can I run the test suite on selected tests? | |
959 | ||
960 | As a first possibility to cut down the number of tests that are run it is | |
961 | possible to use @samp{make check-gcc} or @samp{make check-g++} | |
962 | in the @file{gcc} subdirectory of the object directory. To further cut down the | |
963 | tests the following is possible: | |
964 | ||
965 | @example | |
966 | make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}" | |
967 | @end example | |
968 | ||
969 | This will run all @command{gcc} execute tests in the testsuite. | |
970 | ||
971 | @example | |
972 | make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}" | |
973 | @end example | |
974 | ||
975 | This will run the @command{g++} ``old-deja'' tests in the testsuite where the filename | |
976 | matches @samp{9805*}. | |
977 | ||
978 | The @file{*.exp} files are located in the testsuite directories of the GCC | |
979 | source, the most important ones being @file{compile.exp}, | |
980 | @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}. | |
981 | To get a list of the possible @file{*.exp} files, pipe the | |
982 | output of @samp{make check} into a file and look at the | |
983 | @samp{Running @dots{} .exp} lines. | |
984 | ||
985 | @section How to interpret test results | |
986 | ||
987 | After the testsuite has run you'll find various @file{*.sum} and @file{*.log} | |
988 | files in the testsuite subdirectories. The @file{*.log} files contain a | |
989 | detailed log of the compiler invocations and the corresponding | |
990 | results, the @file{*.sum} files summarize the results. These summaries list | |
991 | all the tests that have been run with a corresponding status code: | |
992 | ||
993 | @itemize @bullet | |
994 | @item | |
995 | PASS: the test passed as expected | |
996 | @item | |
997 | XPASS: the test unexpectedly passed | |
998 | @item | |
999 | FAIL: the test unexpectedly failed | |
1000 | @item | |
1001 | XFAIL: the test failed as expected | |
1002 | @item | |
1003 | UNSUPPORTED: the test is not supported on this platform | |
1004 | @item | |
1005 | ERROR: the testsuite detected an error | |
1006 | @item | |
1007 | WARNING: the testsuite detected a possible problem | |
1008 | @end itemize | |
1009 | ||
1010 | It is normal for some tests to report unexpected failures. At the | |
1011 | current time our testing harness does not allow fine grained control | |
1012 | over whether or not a test is expected to fail. We expect to fix this | |
1013 | problem in future releases. | |
1014 | ||
1015 | ||
1016 | @section Submitting test results | |
1017 | ||
1018 | If you want to report the results to the GCC project, use the | |
1019 | @file{contrib/test_summary} shell script. Start it in the @var{objdir} with | |
1020 | ||
1021 | @example | |
1022 | @var{srcdir}/contrib/test_summary -p your_commentary.txt \ | |
1023 | -m gcc-testresults@@gcc.gnu.org |sh | |
1024 | @end example | |
1025 | ||
1026 | This script uses the @command{Mail} program to send the results, so | |
1027 | make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is | |
1028 | prepended to the testsuite summary and should contain any special | |
1029 | remarks you have on your results or your build environment. Please | |
1030 | do not edit the testsuite result block or the subject line, as these | |
1031 | messages are automatically parsed and presented at the | |
1032 | @uref{http://gcc.gnu.org/testresults/,,GCC testresults} web | |
1033 | page. Here you can also gather information on how specific tests | |
1034 | behave on different platforms and compare them with your results. A | |
1035 | few failing testcases are possible even on released versions and you | |
1036 | should look here first if you think your results are unreasonable. | |
1037 | ||
1038 | @end ifset | |
1039 | ||
1040 | @c ***Final install*********************************************************** | |
1041 | @ifnothtml | |
1042 | @comment node-name, next, previous, up | |
1043 | @node Final install, , Testing, Installing GCC | |
1044 | @end ifnothtml | |
1045 | @ifset finalinstallhtml | |
1046 | @html | |
1047 | <h1 align="center">Installing GCC: Final installation</h1> | |
1048 | @end html | |
1049 | @ifnothtml | |
1050 | @chapter Installing GCC: Final installation | |
1051 | @end ifnothtml | |
1052 | ||
1053 | Now that GCC has been built (and optionally tested), you can install it with | |
1054 | @example | |
1055 | cd @var{objdir}; make install | |
1056 | @end example | |
1057 | ||
1058 | That step completes the installation of GCC; user level binaries can | |
1059 | be found in @file{@var{prefix}/bin} where @var{prefix} is the value you | |
1060 | specified with the @option{--prefix} to configure (or @file{/usr/local} | |
1061 | by default). (If you specified @option{--bindir}, that directory will | |
1062 | be used instead; otherwise, if you specified @option{--exec-prefix}, | |
1063 | @file{@var{exec-prefix}/bin} will be used.) Headers for the C++ and | |
1064 | Java libraries are installed in @file{@var{prefix}/include}; libraries | |
1065 | in @file{@var{libdir}} (normally @file{@var{prefix}/lib}); internal | |
1066 | parts of the compiler in @file{@var{libdir}/gcc-lib}; documentation in | |
1067 | info format in @file{@var{infodir}} (normally @file{@var{prefix}/info}). | |
1068 | ||
1069 | If you don't mind, please quickly review the | |
1070 | @uref{http://gcc.gnu.org/gcc-3.0/buildstat.html,,build status page}. | |
1071 | If your system is not listed, send a note to | |
1072 | @email{gcc@@gcc.gnu.org} indicating | |
1073 | that you successfully built and installed GCC. | |
1074 | ||
1075 | Include the output from running @file{@var{srcdir}/config.guess}. (Do | |
1076 | not send us the @file{config.guess} file itself, just the one-line output from | |
1077 | running it!) | |
1078 | ||
1079 | If you find a bug, please report it following our | |
1080 | @uref{../bugs.html,,bug reporting guidelines}. | |
1081 | ||
1082 | If you want to print the GCC manuals, do @samp{cd @var{objdir}; make | |
1083 | dvi}. You will need to have @command{texi2dvi} (version at least 4.0) | |
1084 | and @TeX{} installed. This creates a number of @file{.dvi} files in | |
1085 | subdirectories of @file{@var{objdir}}; these may be converted for | |
1086 | printing with programs such as @command{dvips}. You can also | |
1087 | @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the | |
1088 | Free Software Foundation}, though such manuals may not be for the most | |
1089 | recent version of GCC@. | |
1090 | ||
1091 | @html | |
1092 | <hr> | |
1093 | <p> | |
1094 | @end html | |
1095 | @ifhtml | |
1096 | @uref{./index.html,,Return to the GCC Installation page} | |
1097 | @end ifhtml | |
1098 | @end ifset | |
1099 | ||
1100 | @c ***Binaries**************************************************************** | |
1101 | @ifnothtml | |
1102 | @comment node-name, next, previous, up | |
1103 | @node Binaries, Specific, Installing GCC, Top | |
1104 | @end ifnothtml | |
1105 | @ifset binarieshtml | |
1106 | @html | |
1107 | <h1 align="center">Installing GCC: Binaries</h1> | |
1108 | @end html | |
1109 | @ifnothtml | |
1110 | @chapter Installing GCC: Binaries | |
1111 | @end ifnothtml | |
1112 | @cindex Binaries | |
1113 | @cindex Installing GCC: Binaries | |
1114 | ||
1115 | We are often asked about pre-compiled versions of GCC@. While we cannot | |
1116 | provide these for all platforms, below you'll find links to binaries for | |
1117 | various platforms where creating them by yourself is not easy due to various | |
1118 | reasons. | |
1119 | ||
1120 | Please note that we did not create these binaries, nor do we | |
1121 | support them. If you have any problems installing them, please | |
1122 | contact their makers. | |
1123 | ||
1124 | @itemize | |
1125 | @item | |
1126 | AIX: | |
1127 | @itemize | |
1128 | @item | |
1129 | @uref{http://www-frec.bull.com/docs/download.htm,,Bull's Freeware and | |
1130 | Shareware Archive for AIX}; | |
1131 | ||
1132 | @item | |
1133 | @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX}; | |
1134 | @end itemize | |
1135 | ||
1136 | @item | |
1137 | DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}; | |
1138 | ||
1139 | @item | |
1140 | @uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center}; | |
1141 | ||
1142 | @item | |
1143 | @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO | |
1144 | OpenServer/Unixware}; | |
1145 | ||
1146 | @item | |
1147 | Solaris (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}; | |
1148 | ||
1149 | @item | |
1150 | SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}; | |
1151 | ||
1152 | @item | |
1153 | Windows 95, 98, and NT: | |
1154 | @itemize | |
1155 | @item | |
1156 | The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project; | |
1157 | @item | |
1158 | @uref{http://www.xraylith.wisc.edu/~khan/software/gnu-win32/,,GNU Win32} | |
1159 | related projects by Mumit Khan. | |
1160 | @end itemize | |
1161 | ||
1162 | @item | |
1163 | @uref{ftp://ftp.thewrittenword.com/packages/free/by-name/gcc-2.95.2/,,The | |
1164 | Written Word} offers binaries for Solaris 2.5.1, 2.6, 2.7/SPARC, 2.7/Intel, | |
1165 | IRIX 6.2, 6.5, Digital UNIX 4.0D, HP-UX 10.20, and HP-UX 11.00. | |
1166 | ||
1167 | @item | |
1168 | Hitachi H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU | |
1169 | Development Tools for the Hitachi H8/300[HS] Series} | |
1170 | ||
1171 | @end itemize | |
1172 | ||
1173 | In addition to those specific offerings, you can get a binary | |
1174 | distribution CD-ROM from the | |
1175 | @uref{http://www.fsf.org/order/order.html,,Free Software Foundation}. | |
1176 | It contains binaries for a number of platforms, and | |
1177 | includes not only GCC, but other stuff as well. The current CD does | |
1178 | not contain the latest version of GCC, but it should allow | |
1179 | bootstrapping the compiler. An updated version of that disk is in the | |
1180 | works. | |
1181 | ||
1182 | @html | |
1183 | <hr> | |
1184 | <p> | |
1185 | @end html | |
1186 | @ifhtml | |
1187 | @uref{./index.html,,Return to the GCC Installation page} | |
1188 | @end ifhtml | |
1189 | @end ifset | |
1190 | ||
1191 | @c ***Specific**************************************************************** | |
1192 | @ifnothtml | |
1193 | @comment node-name, next, previous, up | |
1194 | @node Specific, Concept Index, Binaries, Top | |
1195 | @end ifnothtml | |
1196 | @ifset specifichtml | |
1197 | @html | |
1198 | <h1 align="center">Host/target specific installation notes for GCC</h1> | |
1199 | @end html | |
1200 | @ifnothtml | |
1201 | @chapter Host/target specific installation notes for GCC | |
1202 | @end ifnothtml | |
1203 | @cindex Specific | |
1204 | @cindex Specific installation notes | |
1205 | @cindex Target specific installation | |
1206 | @cindex Host specific installation | |
1207 | @cindex Target specific installation notes | |
1208 | ||
1209 | Please read this document carefully @emph{before} installing the | |
1210 | GNU Compiler Collection on your machine. | |
1211 | ||
1212 | @ifhtml | |
1213 | @itemize | |
1214 | @item | |
1215 | @uref{#1750a-*-*,,1750a-*-*} | |
1216 | @item | |
1217 | @uref{#a29k,,a29k} | |
1218 | @item | |
1219 | @uref{#a29k-*-bsd,,a29k-*-bsd} | |
1220 | @item | |
1221 | @uref{#alpha*-*-*,,alpha*-*-*} | |
1222 | @item | |
1223 | @uref{#alpha*-dec-osf*,,alpha*-dec-osf*} | |
1224 | @item | |
1225 | @uref{#arc-*-elf,,arc-*-elf} | |
1226 | @item | |
1227 | @uref{#arm-*-aout,,arm-*-aout} | |
1228 | @item | |
1229 | @uref{#arm-*-elf,,arm-*-elf} | |
1230 | @item | |
1231 | @uref{#arm*-*-linux-gnu,,arm*-*-linux-gnu} | |
1232 | @item | |
1233 | @uref{#arm-*-riscix,,arm-*-riscix} | |
1234 | @item | |
1235 | @uref{#avr,,avr} | |
1236 | @item | |
1237 | @uref{#c4x,,c4x} | |
1238 | @item | |
1239 | @uref{#dos,,DOS} | |
1240 | @item | |
1241 | @uref{#dsp16xx,,dsp16xx} | |
1242 | @item | |
1243 | @uref{#elxsi-elxsi-bsd,,elxsi-elxsi-bsd} | |
1244 | @item | |
1245 | @uref{#*-*-freebsd*,,*-*-freebsd*} | |
1246 | @item | |
1247 | @uref{#h8300-hms,,h8300-hms} | |
1248 | @item | |
1249 | @uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*} | |
1250 | @item | |
1251 | @uref{#hppa*-hp-hpux9,,hppa*-hp-hpux9} | |
1252 | @item | |
1253 | @uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10} | |
1254 | @item | |
1255 | @uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11} | |
1256 | @item | |
1257 | @uref{#i370-*-*,,i370-*-*} | |
1258 | @item | |
1259 | @uref{#*-*-linux-gnu,,*-*-linux-gnu} | |
1260 | @item | |
1261 | @uref{#ix86-*-linux*oldld,,i?86-*-linux*oldld} | |
1262 | @item | |
1263 | @uref{#ix86-*-linux*aout,,i?86-*-linux*aout} | |
1264 | @item | |
1265 | @uref{#ix86-*-linux*,,i?86-*-linux*} | |
1266 | @item | |
1267 | @uref{#ix86-*-sco,,i?86-*-sco} | |
1268 | @item | |
1269 | @uref{#ix86-*-sco3.2v4,,i?86-*-sco3.2v4} | |
1270 | @item | |
1271 | @uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*} | |
1272 | @item | |
1273 | @uref{#ix86-*-udk,,i?86-*-udk} | |
1274 | @item | |
1275 | @uref{#ix86-*-isc,,i?86-*-isc} | |
1276 | @item | |
1277 | @uref{#ix86-*-esix,,i?86-*-esix} | |
1278 | @item | |
1279 | @uref{#ix86-ibm-aix,,i?86-ibm-aix} | |
1280 | @item | |
1281 | @uref{#ix86-sequent-bsd,,i?86-sequent-bsd} | |
1282 | @item | |
1283 | @uref{#ix86-sequent-ptx1*,,i?86-sequent-ptx1*, i?86-sequent-ptx2*} | |
1284 | @item | |
1285 | @uref{#ix86-*-sysv3*,,i?86-*-sysv3*} | |
1286 | @item | |
1287 | @uref{#i860-intel-osf*,,i860-intel-osf*} | |
1288 | @item | |
1289 | @uref{#*-lynx-lynxos,,*-lynx-lynxos} | |
1290 | @item | |
1291 | @uref{#*-ibm-aix*,,*-ibm-aix*} | |
1292 | @item | |
1293 | @uref{#m32r-*-elf,,m32r-*-elf} | |
1294 | @item | |
1295 | @uref{#m68000-hp-bsd,,m68000-hp-bsd} | |
1296 | @item | |
1297 | @uref{#m6811-elf,,m6811-elf} | |
1298 | @item | |
1299 | @uref{#m6812-elf,,m6812-elf} | |
1300 | @item | |
1301 | @uref{#m68k-altos,,m68k-altos} | |
1302 | @item | |
1303 | @uref{#m68k-apple-aux,,m68k-apple-aux} | |
1304 | @item | |
1305 | @uref{#m68k-att-sysv,,m68k-att-sysv} | |
1306 | @item | |
1307 | @uref{#m68k-bull-sysv,,m68k-bull-sysv} | |
1308 | @item | |
1309 | @uref{#m68k-crds-unox,,m68k-crds-unox} | |
1310 | @item | |
1311 | @uref{#m68k-hp-hpux,,m68k-hp-hpux} | |
1312 | @item | |
1313 | @uref{#m68k-*-nextstep*,,m68k-*-nextstep*} | |
1314 | @item | |
1315 | @uref{#m68k-ncr-*,,m68k-ncr-*} | |
1316 | @item | |
1317 | @uref{#m68k-sun,,m68k-sun} | |
1318 | @item | |
1319 | @uref{#m68k-sun-sunos4.1.1,,m68k-sun-sunos4.1.1} | |
1320 | @item | |
1321 | @uref{#m88k-*-svr3,,m88k-*-svr3} | |
1322 | @item | |
1323 | @uref{#m88k-*-dgux,,m88k-*-dgux} | |
1324 | @item | |
1325 | @uref{#m88k-tektronix-sysv3,,m88k-tektronix-sysv3} | |
1326 | @item | |
1327 | @uref{#mips-*-*,,mips-*-*} | |
1328 | @item | |
1329 | @uref{#mips-dec-*,,mips-dec-*} | |
1330 | @item | |
1331 | @uref{#mips-mips-bsd,,mips-mips-bsd} | |
1332 | @item | |
1333 | @uref{#mips-mips-riscos*,,mips-mips-riscos*} | |
1334 | @item | |
1335 | @uref{#mips*-sgi-irix4,,mips*-sgi-irix4} | |
1336 | @item | |
1337 | @uref{#mips*-sgi-irix5,,mips*-sgi-irix5} | |
1338 | @item | |
1339 | @uref{#mips*-sgi-irix6,,mips*-sgi-irix6} | |
1340 | @item | |
1341 | @uref{#mips-sony-sysv,,mips-sony-sysv} | |
1342 | @item | |
1343 | @uref{#ns32k-encore,,ns32k-encore} | |
1344 | @item | |
1345 | @uref{#ns32k-*-genix,,ns32k-*-genix} | |
1346 | @item | |
1347 | @uref{#ns32k-sequent,,ns32k-sequent} | |
1348 | @item | |
1349 | @uref{#ns32k-utek,,ns32k-utek} | |
1350 | @item | |
1351 | @uref{#powerpc*-*-*,,powerpc*-*-*, powerpc-*-sysv4} | |
1352 | @item | |
1353 | @uref{#powerpc-*-elf,,powerpc-*-elf, powerpc-*-sysv4} | |
1354 | @item | |
1355 | @uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*} | |
1356 | @item | |
1357 | @uref{#powerpc-*-eabiaix,,powerpc-*-eabiaix} | |
1358 | @item | |
1359 | @uref{#powerpc-*-eabisim,,powerpc-*-eabisim} | |
1360 | @item | |
1361 | @uref{#powerpc-*-eabi,,powerpc-*-eabi} | |
1362 | @item | |
1363 | @uref{#powerpcle-*-elf,,powerpcle-*-elf, powerpcle-*-sysv4} | |
1364 | @item | |
1365 | @uref{#powerpcle-*-eabisim,,powerpcle-*-eabisim} | |
1366 | @item | |
1367 | @uref{#powerpcle-*-eabi,,powerpcle-*-eabi} | |
1368 | @item | |
1369 | @uref{#powerpcle-*-winnt,,powerpcle-*-winnt, powerpcle-*-pe} | |
1370 | @item | |
1371 | @uref{#romp-*-aos,,romp-*-aos, romp-*-mach} | |
1372 | @item | |
1373 | @uref{#*-*-solaris*,,*-*-solaris*} | |
1374 | @item | |
1375 | @uref{#sparc-sun-*,,sparc-sun-*} | |
1376 | @item | |
1377 | @uref{#sparc-sun-solaris*,,sparc-sun-solaris*} | |
1378 | @item | |
1379 | @uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7} | |
1380 | @item | |
1381 | @uref{#*-sun-solaris2.8,,*-sun-solaris2.8} | |
1382 | @item | |
1383 | @uref{#sparc-sun-sunos*,,sparc-sun-sunos*} | |
1384 | @item | |
1385 | @uref{#sparc-unknown-linux-gnulibc1,,sparc-unknown-linux-gnulibc1} | |
1386 | @item | |
1387 | @uref{#sparc64-*-*,,sparc64-*-*} | |
1388 | @item | |
1389 | @uref{#*-*-sysv*,,*-*-sysv*} | |
1390 | @item | |
1391 | @uref{#vax-dec-ultrix,,vax-dec-ultrix} | |
1392 | @item | |
1393 | @uref{#we32k-*-*,,we32k-*-*} | |
1394 | @item | |
1395 | @uref{#windows,,Microsoft Windows} | |
1396 | @item | |
1397 | @uref{#os2,,OS/2} | |
1398 | @item | |
1399 | @uref{#older,,Older systems} | |
1400 | @end itemize | |
1401 | ||
1402 | @itemize | |
1403 | @item | |
1404 | @uref{#elf_targets,,all ELF targets} (SVR4, Solaris, etc.) | |
1405 | @end itemize | |
1406 | @end ifhtml | |
1407 | ||
1408 | ||
1409 | @html | |
1410 | <!-- -------- host/target specific issues start here ---------------- --> | |
1411 | <hr> | |
1412 | @end html | |
1413 | @heading @anchor{1750a-*-*}1750a-*-* | |
1414 | MIL-STD-1750A processors. | |
1415 | ||
1416 | The MIL-STD-1750A cross configuration produces output for | |
1417 | @code{as1750}, an assembler/linker available under the GNU General Public | |
1418 | License for the 1750A@. @code{as1750} can be obtained at | |
1419 | @uref{ftp://ftp.fta-berlin.de/pub/crossgcc/1750gals/}. | |
1420 | A similarly licensed simulator for | |
1421 | the 1750A is available from same address. | |
1422 | ||
1423 | You should ignore a fatal error during the building of @samp{libgcc} | |
1424 | (@samp{libgcc} is not yet implemented for the 1750A@.) | |
1425 | ||
1426 | The @code{as1750} assembler requires the file @file{ms1750.inc}, which is | |
1427 | found in the directory @file{gcc/config/1750a}. | |
1428 | ||
1429 | GCC produced the same sections as the Fairchild F9450 C Compiler, | |
1430 | namely: | |
1431 | ||
1432 | @table @code | |
1433 | @item Normal | |
1434 | The program code section. | |
1435 | ||
1436 | @item Static | |
1437 | The read/write (RAM) data section. | |
1438 | ||
1439 | @item Konst | |
1440 | The read-only (ROM) constants section. | |
1441 | ||
1442 | @item Init | |
1443 | Initialization section (code to copy KREL to SREL)@. | |
1444 | @end table | |
1445 | ||
1446 | The smallest addressable unit is 16 bits (@code{BITS_PER_UNIT} is 16). This | |
1447 | means that type @code{char} is represented with a 16-bit word per character. | |
1448 | The 1750A's ``Load/Store Upper/Lower Byte'' instructions are not used by | |
1449 | GCC@. | |
1450 | ||
1451 | @html | |
1452 | </p> | |
1453 | <hr> | |
1454 | @end html | |
1455 | @heading @anchor{a29k}a29k | |
1456 | AMD Am29k-family processors. These are normally used in embedded | |
1457 | applications. There are no standard Unix configurations. | |
1458 | This configuration | |
1459 | corresponds to AMD's standard calling sequence and binary interface | |
1460 | and is compatible with other 29k tools. | |
1461 | ||
1462 | You may need to make a variant of the file @file{a29k.h} for your | |
1463 | particular configuration. | |
1464 | ||
1465 | @html | |
1466 | </p> | |
1467 | <hr> | |
1468 | @end html | |
1469 | @heading @anchor{a29k-*-bsd}a29k-*-bsd | |
1470 | AMD Am29050 used in a system running a variant of BSD Unix. | |
1471 | ||
1472 | @html | |
1473 | </p> | |
1474 | <hr> | |
1475 | @end html | |
1476 | @heading @anchor{alpha*-*-*}alpha*-*-* | |
1477 | ||
1478 | This section contains general configuration information for all | |
1479 | alpha-based platforms using ELF (in particular, ignore this section for | |
1480 | DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this | |
1481 | section, please read all other sections that match your target. | |
1482 | ||
1483 | We require binutils 2.11.2 or newer. | |
1484 | Previous binutils releases had a number of problems with DWARF 2 | |
1485 | debugging information, not the least of which is incorrect linking of | |
1486 | shared libraries. | |
1487 | ||
1488 | @html | |
1489 | </p> | |
1490 | <hr> | |
1491 | @end html | |
1492 | @heading @anchor{alpha*-dec-osf*}alpha*-dec-osf* | |
1493 | Systems using processors that implement the DEC Alpha architecture and | |
1494 | are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq | |
1495 | Tru64 UNIX) operating system, for example the DEC Alpha AXP systems. | |
1496 | ||
1497 | In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not | |
1498 | currently (2001-06-13) work with @command{mips-tfile}. As a workaround, | |
1499 | we need to use the old assembler, invoked via the barely documented | |
1500 | @option{-oldas} option. To bootstrap GCC, you either need to use the | |
1501 | Compaq C Compiler: | |
1502 | ||
1503 | @example | |
1504 | % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}] | |
1505 | @end example | |
1506 | ||
1507 | or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0: | |
1508 | ||
1509 | @example | |
1510 | % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}] | |
1511 | @end example | |
1512 | ||
1513 | GCC writes a @samp{.verstamp} directive to the assembler output file | |
1514 | unless it is built as a cross-compiler. It gets the version to use from | |
1515 | the system header file @file{/usr/include/stamp.h}. If you install a | |
1516 | new version of DEC Unix, you should rebuild GCC to pick up the new version | |
1517 | stamp. | |
1518 | ||
1519 | Note that since the Alpha is a 64-bit architecture, cross-compilers from | |
1520 | 32-bit machines will not generate code as efficient as that generated | |
1521 | when the compiler is running on a 64-bit machine because many | |
1522 | optimizations that depend on being able to represent a word on the | |
1523 | target in an integral value on the host cannot be performed. Building | |
1524 | cross-compilers on the Alpha for 32-bit machines has only been tested in | |
1525 | a few cases and may not work properly. | |
1526 | ||
1527 | @code{make compare} may fail on old versions of DEC Unix unless you add | |
1528 | @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the | |
1529 | assembler input file is stored in the object file, and that makes | |
1530 | comparison fail if it differs between the @code{stage1} and | |
1531 | @code{stage2} compilations. The option @option{-save-temps} forces a | |
1532 | fixed name to be used for the assembler input file, instead of a | |
1533 | randomly chosen name in @file{/tmp}. Do not add @option{-save-temps} | |
1534 | unless the comparisons fail without that option. If you add | |
1535 | @option{-save-temps}, you will have to manually delete the @samp{.i} and | |
1536 | @samp{.s} files after each series of compilations. | |
1537 | ||
1538 | GCC now supports both the native (ECOFF) debugging format used by DBX | |
1539 | and GDB and an encapsulated STABS format for use only with GDB@. See the | |
1540 | discussion of the @option{--with-stabs} option of @file{configure} above | |
1541 | for more information on these formats and how to select them. | |
1542 | ||
1543 | There is a bug in DEC's assembler that produces incorrect line numbers | |
1544 | for ECOFF format when the @samp{.align} directive is used. To work | |
1545 | around this problem, GCC will not emit such alignment directives | |
1546 | while writing ECOFF format debugging information even if optimization is | |
1547 | being performed. Unfortunately, this has the very undesirable | |
1548 | side-effect that code addresses when @option{-O} is specified are | |
1549 | different depending on whether or not @option{-g} is also specified. | |
1550 | ||
1551 | To avoid this behavior, specify @option{-gstabs+} and use GDB instead of | |
1552 | DBX@. DEC is now aware of this problem with the assembler and hopes to | |
1553 | provide a fix shortly. | |
1554 | ||
1555 | @html | |
1556 | </p> | |
1557 | <hr> | |
1558 | @end html | |
1559 | @heading @anchor{arc-*-elf}arc-*-elf | |
1560 | Argonaut ARC processor. | |
1561 | This configuration is intended for embedded systems. | |
1562 | ||
1563 | @html | |
1564 | </p> | |
1565 | <hr> | |
1566 | @end html | |
1567 | @heading @anchor{arm-*-aout}arm-*-aout | |
1568 | Advanced RISC Machines ARM-family processors. These are often used in | |
1569 | embedded applications. There are no standard Unix configurations. | |
1570 | This configuration corresponds to the basic instruction sequences and will | |
1571 | produce @file{a.out} format object modules. | |
1572 | ||
1573 | You may need to make a variant of the file @file{arm.h} for your particular | |
1574 | configuration. | |
1575 | ||
1576 | @html | |
1577 | </p> | |
1578 | <hr> | |
1579 | @end html | |
1580 | @heading @anchor{arm-*-elf}arm-*-elf | |
1581 | This configuration is intended for embedded systems. | |
1582 | ||
1583 | @html | |
1584 | </p> | |
1585 | <hr> | |
1586 | @end html | |
1587 | @heading @anchor{arm*-*-linux-gnu}arm*-*-linux-gnu | |
1588 | ||
1589 | We require GNU binutils 2.10 or newer. | |
1590 | ||
1591 | @html | |
1592 | </p> | |
1593 | <hr> | |
1594 | @end html | |
1595 | @heading @anchor{arm-*-riscix}arm-*-riscix | |
1596 | The ARM2 or ARM3 processor running RISC iX, Acorn's port of BSD Unix. | |
1597 | If you are running a version of RISC iX prior to 1.2 then you must | |
1598 | specify the version number during configuration. Note that the | |
1599 | assembler shipped with RISC iX does not support stabs debugging | |
1600 | information; a new version of the assembler, with stabs support | |
1601 | included, is now available from Acorn and via ftp | |
1602 | @uref{ftp://ftp.acorn.com/pub/riscix/as+xterm.tar.Z}. To enable stabs | |
1603 | debugging, pass @option{--with-gnu-as} to configure. | |
1604 | ||
1605 | You will need to install GNU @command{sed} before you can run configure. | |
1606 | ||
1607 | @html | |
1608 | </p> | |
1609 | <hr> | |
1610 | @end html | |
1611 | @heading @anchor{avr}avr | |
1612 | ||
1613 | ATMEL AVR-family micro controllers. These are used in embedded | |
1614 | applications. There are no standard Unix configurations. @xref{AVR | |
1615 | Options,, AVR Options, gcc, Using and Porting the GNU Compiler | |
1616 | Collection (GCC)}, for the list of supported MCU types. | |
1617 | ||
1618 | Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@. | |
1619 | ||
1620 | Further installation notes and other useful information about AVR tools | |
1621 | can also be obtained from: | |
1622 | ||
1623 | @itemize @bullet | |
1624 | @item | |
1625 | @uref{http://home.overta.ru/users/denisc,,http://home.overta.ru/users/denisc} | |
1626 | @item | |
1627 | @uref{http://www.itnet.pl/amelektr/avr,,http://www.itnet.pl/amelektr/avr} | |
1628 | @end itemize | |
1629 | ||
1630 | We @emph{strongly} recommend using binutils 2.11 or newer. | |
1631 | ||
1632 | The following error: | |
1633 | @example | |
1634 | Error: register required | |
1635 | @end example | |
1636 | ||
1637 | indicates that you should upgrade to a newer version of the binutils. | |
1638 | ||
1639 | @html | |
1640 | </p> | |
1641 | <hr> | |
1642 | @end html | |
1643 | @heading @anchor{c4x}c4x | |
1644 | ||
1645 | Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal | |
1646 | Processors. These are used in embedded applications. There are no | |
1647 | standard Unix configurations. @xref{C4x Options,, C4x Options, gcc, | |
1648 | Using and Porting the GNU Compiler Collection (GCC)}, for the list of | |
1649 | supported MCU types. | |
1650 | ||
1651 | GCC can be configured as a cross compiler for both the C3x and C4x | |
1652 | architectures on the same system. Use @samp{configure --target=c4x | |
1653 | --enable-languages="c,c++"} to configure. | |
1654 | ||
1655 | ||
1656 | Further installation notes and other useful information about C4x tools | |
1657 | can also be obtained from: | |
1658 | ||
1659 | @itemize @bullet | |
1660 | @item | |
1661 | @uref{http://www.elec.canterbury.ac.nz/c4x,,http://www.elec.canterbury.ac.nz/c4x} | |
1662 | @end itemize | |
1663 | ||
1664 | @html | |
1665 | </p> | |
1666 | <hr> | |
1667 | @end html | |
1668 | @heading @anchor{dos}DOS | |
1669 | ||
1670 | Please have a look at our @uref{binaries.html,,binaries page}. | |
1671 | ||
1672 | You cannot install GCC by itself on MSDOS; it will not compile under | |
1673 | any MSDOS compiler except itself. You need to get the complete | |
1674 | compilation package DJGPP, which includes binaries as well as sources, | |
1675 | and includes all the necessary compilation tools and libraries. | |
1676 | ||
1677 | @html | |
1678 | </p> | |
1679 | <hr> | |
1680 | @end html | |
1681 | @heading @anchor{dsp16xx}dsp16xx | |
1682 | A port to the AT&T DSP1610 family of processors. | |
1683 | ||
1684 | @html | |
1685 | </p> | |
1686 | <hr> | |
1687 | @end html | |
1688 | @heading @anchor{*-*-freebsd*}*-*-freebsd* | |
1689 | ||
1690 | The version of binutils installed in @file{/usr/bin} is known to work unless | |
1691 | otherwise specified in any per-architecture notes. However, binutils | |
1692 | 2.11 is known to improve overall testsuite results. | |
1693 | ||
1694 | For FreeBSD 1, FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All | |
1695 | configuration support and files as shipped with GCC 2.95 are still in | |
1696 | place. FreeBSD 2.2.7 has been known to bootstrap completely; however, | |
1697 | it is unknown which version of binutils was used (it is assumed that it | |
1698 | was the system copy in @file{/usr/bin}) and C++ EH failures were noted. | |
1699 | ||
1700 | For FreeBSD using the ELF file format: DWARF 2 debugging is now the | |
1701 | default for all CPU architectures. It had been the default on | |
1702 | FreeBSD/alpha since its inception. You may use @option{-gstabs} instead | |
1703 | of @option{-g}, if you really want the old debugging format. There are | |
1704 | no known issues with mixing object files and libraries with different | |
1705 | debugging formats. Otherwise, this release of GCC should now match more | |
1706 | of the configuration used in the stock FreeBSD configuration of GCC. In | |
1707 | particular, @option{--enable-threads} is now configured by default. | |
1708 | However, as a general user, do not attempt to replace the system | |
1709 | compiler with this release. Known to bootstrap and check with good | |
1710 | results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3 and 5-CURRENT@. | |
1711 | ||
1712 | At this time, @option{--enable-threads} is not compatible with | |
1713 | @option{--enable-libgcj} on FreeBSD@. | |
1714 | ||
1715 | @html | |
1716 | </p> | |
1717 | <hr> | |
1718 | @end html | |
1719 | @heading @anchor{elxsi-elxsi-bsd}elxsi-elxsi-bsd | |
1720 | The Elxsi's C compiler has known limitations that prevent it from | |
1721 | compiling GCC@. Please contact @email{mrs@@wrs.com} for more details. | |
1722 | ||
1723 | @html | |
1724 | </p> | |
1725 | <hr> | |
1726 | @end html | |
1727 | @heading @anchor{h8300-hms}h8300-hms | |
1728 | Hitachi H8/300 series of processors. | |
1729 | ||
1730 | Please have a look at our @uref{binaries.html,,binaries page}. | |
1731 | ||
1732 | The calling convention and structure layout has changed in release 2.6. | |
1733 | All code must be recompiled. The calling convention now passes the | |
1734 | first three arguments in function calls in registers. Structures are no | |
1735 | longer a multiple of 2 bytes. | |
1736 | ||
1737 | @html | |
1738 | </p> | |
1739 | <hr> | |
1740 | @end html | |
1741 | @heading @anchor{hppa*-hp-hpux*}hppa*-hp-hpux* | |
1742 | ||
1743 | We @emph{highly} recommend using gas/binutils 2.8 or newer on all hppa | |
1744 | platforms; you may encounter a variety of problems when using the HP | |
1745 | assembler. | |
1746 | ||
1747 | Specifically, @option{-g} does not work on HP-UX (since that system | |
1748 | uses a peculiar debugging format which GCC does not know about), unless you | |
1749 | use GAS and GDB and configure GCC with the | |
1750 | @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and | |
1751 | @option{--with-as=@dots{}} options. | |
1752 | ||
1753 | If you wish to use pa-risc 2.0 architecture support, you must use either | |
1754 | the HP assembler, gas/binutils 2.11 or a recent | |
1755 | @uref{ftp://sources.redhat.com/pub/binutils/snapshots,,snapshot of gas}. | |
1756 | ||
1757 | More specific information to @samp{hppa*-hp-hpux*} targets follows. | |
1758 | ||
1759 | @html | |
1760 | </p> | |
1761 | <hr> | |
1762 | @end html | |
1763 | @heading @anchor{hppa*-hp-hpux9}hppa*-hp-hpux9 | |
1764 | ||
1765 | The HP assembler has major problems on this platform. We've tried to work | |
1766 | around the worst of the problems. However, those workarounds may be causing | |
1767 | linker crashes in some circumstances; the workarounds also probably prevent | |
1768 | shared libraries from working. Use the GNU assembler to avoid these problems. | |
1769 | ||
1770 | ||
1771 | The configuration scripts for GCC will also trigger a bug in the hpux9 | |
1772 | shell. To avoid this problem set @env{CONFIG_SHELL} to @file{/bin/ksh} | |
1773 | and @env{SHELL} to @file{/bin/ksh} in your environment. | |
1774 | ||
1775 | ||
1776 | @html | |
1777 | </p> | |
1778 | <hr> | |
1779 | @end html | |
1780 | @heading @anchor{hppa*-hp-hpux10}hppa*-hp-hpux10 | |
1781 | ||
1782 | For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch | |
1783 | @code{PHCO_19798} from HP@. HP has two sites which provide patches free of | |
1784 | charge: | |
1785 | ||
1786 | @itemize @bullet | |
1787 | @item | |
1788 | @html | |
1789 | <a href="http://us-support.external.hp.com">US, Canada, Asia-Pacific, and | |
1790 | Latin-America</a> | |
1791 | @end html | |
1792 | @ifnothtml | |
1793 | @uref{http://us-support.external.hp.com,,}US, Canada, Asia-Pacific, and | |
1794 | Latin-America | |
1795 | @end ifnothtml | |
1796 | @item | |
1797 | @uref{http://europe-support.external.hp.com,,Europe} | |
1798 | @end itemize | |
1799 | ||
1800 | The HP assembler on these systems is much better than the hpux9 assembler, | |
1801 | but still has some problems. Most notably the assembler inserts timestamps | |
1802 | into each object file it creates, causing the 3-stage comparison test to fail | |
1803 | during a @samp{make bootstrap}. You should be able to continue by | |
1804 | saying @samp{make all} after getting the failure from @samp{make | |
1805 | bootstrap}. | |
1806 | ||
1807 | ||
1808 | @html | |
1809 | </p> | |
1810 | <hr> | |
1811 | @end html | |
1812 | @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11 | |
1813 | ||
1814 | GCC 3.0 supports HP-UX 11. You must use GNU binutils 2.11 or above on | |
1815 | this platform. | |
1816 | ||
1817 | @html | |
1818 | </p> | |
1819 | <hr> | |
1820 | @end html | |
1821 | @heading @anchor{i370-*-*}i370-*-* | |
1822 | This port is very preliminary and has many known bugs. We hope to | |
1823 | have a higher-quality port for this machine soon. | |
1824 | ||
1825 | @html | |
1826 | </p> | |
1827 | <hr> | |
1828 | @end html | |
1829 | @heading @anchor{*-*-linux-gnu}*-*-linux-gnu | |
1830 | ||
1831 | If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install | |
1832 | out-of-the-box. You'll get compile errors while building @samp{libstdc++}. | |
1833 | The patch @uref{glibc-2.2.patch,,glibc-2.2.patch}, that is to be | |
1834 | applied in the GCC source tree, fixes the compatibility problems. | |
1835 | ||
1836 | @html | |
1837 | </p> | |
1838 | @end html | |
1839 | ||
1840 | @html | |
1841 | <p> | |
1842 | @end html | |
1843 | ||
1844 | Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync | |
1845 | since the latest exception handling changes for GCC@. Compiling glibc | |
1846 | with GCC 3.0 will give a binary incompatible glibc and therefore cause | |
1847 | lots of problems and might make your system completly unusable. This | |
1848 | will definitly need fixes in glibc but might also need fixes in GCC@. We | |
1849 | strongly advise to wait for glibc 2.2.4 and to read the release notes of | |
1850 | glibc 2.2.4 whether patches for GCC 3.0 are needed. You can use glibc | |
1851 | 2.2.3 with GCC 3.0, just do not try to recompile it. | |
1852 | ||
1853 | @html | |
1854 | </p> | |
1855 | <hr> | |
1856 | @end html | |
1857 | @heading @anchor{ix86-*-linux*oldld}i?86-*-linux*oldld | |
1858 | Use this configuration to generate @file{a.out} binaries on Linux-based | |
1859 | GNU systems if you do not have gas/binutils version 2.5.2 or later | |
1860 | installed. This is an obsolete configuration. | |
1861 | ||
1862 | @html | |
1863 | </p> | |
1864 | <hr> | |
1865 | @end html | |
1866 | @heading @anchor{ix86-*-linux*aout}i?86-*-linux*aout | |
1867 | Use this configuration to generate @file{a.out} binaries on Linux-based | |
1868 | GNU systems. This configuration is being superseded. You must use | |
1869 | gas/binutils version 2.5.2 or later. | |
1870 | ||
1871 | @html | |
1872 | </p> | |
1873 | <hr> | |
1874 | @end html | |
1875 | @heading @anchor{ix86-*-linux*}i?86-*-linux* | |
1876 | ||
1877 | You will need binutils 2.9.1.0.15 or newer for exception handling to work. | |
1878 | ||
1879 | If you receive Signal 11 errors when building on GNU/Linux, then it is | |
1880 | possible you have a hardware problem. Further information on this can be | |
1881 | found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}. | |
1882 | ||
1883 | @html | |
1884 | </p> | |
1885 | <hr> | |
1886 | @end html | |
1887 | @heading @anchor{ix86-*-sco}i?86-*-sco | |
1888 | Compilation with RCC is recommended. Also, it may be a good idea to | |
1889 | link with GNU malloc instead of the malloc that comes with the system. | |
1890 | ||
1891 | @html | |
1892 | </p> | |
1893 | <hr> | |
1894 | @end html | |
1895 | @heading @anchor{ix86-*-sco3.2v4}i?86-*-sco3.2v4 | |
1896 | Use this configuration for SCO release 3.2 version 4. | |
1897 | ||
1898 | @html | |
1899 | </p> | |
1900 | <hr> | |
1901 | @end html | |
1902 | @heading @anchor{ix86-*-sco3.2v5*}i?86-*-sco3.2v5* | |
1903 | Use this for the SCO OpenServer Release 5 family of operating systems. | |
1904 | ||
1905 | Unlike earlier versions of GCC, the ability to generate COFF with this | |
1906 | target is no longer provided. | |
1907 | ||
1908 | Earlier versions of GCC emitted DWARF 1 when generating ELF to allow | |
1909 | the system debugger to be used. That support was too burdensome to | |
1910 | maintain. GCC now emits only DWARF 2 for this target. This means you | |
1911 | may use either the UDK debugger or GDB to debug programs built by this | |
1912 | version of GCC@. | |
1913 | ||
1914 | Use of the @option{-march=pentiumpro} flag can result in | |
1915 | unrecognized opcodes when using the native assembler on OS versions before | |
1916 | 5.0.6. (Support for P6 opcodes was added to the native ELF assembler in | |
1917 | that version.) While it's rather rare to see these emitted by GCC yet, | |
1918 | errors of the basic form: | |
1919 | ||
1920 | @example | |
1921 | /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip | |
1922 | /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip | |
1923 | @end example | |
1924 | ||
1925 | are symptoms of this problem. You may work around this by not | |
1926 | building affected files with that flag, by using the GNU assembler, or | |
1927 | by using the assembler provided with the current version of the OS@. | |
1928 | Users of GNU assembler should see the note below for hazards on doing | |
1929 | so. | |
1930 | ||
1931 | The native SCO assembler that is provided with the OS at no | |
1932 | charge is normally required. If, however, you must be able to use | |
1933 | the GNU assembler (perhaps you're compiling code with asms that | |
1934 | require GAS syntax) you may configure this package using the flags | |
1935 | @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You must | |
1936 | use a recent version of GNU binutils; versions past 2.9.1 seem to work | |
1937 | well. | |
1938 | ||
1939 | In general, the @option{--with-gnu-as} option isn't as well tested | |
1940 | as the native assembler. | |
1941 | ||
1942 | Look in @file{gcc/config/i386/sco5.h} (search for ``messy'') for | |
1943 | additional OpenServer-specific flags. | |
1944 | ||
1945 | Systems based on OpenServer before 5.0.4 (@samp{uname -X} | |
1946 | will tell you what you're running) require TLS597 from | |
1947 | @uref{ftp://ftp.sco.com/TLS/,,ftp://ftp.sco.com/TLS/} | |
1948 | for C++ constructors and destructors to work right. | |
1949 | ||
1950 | The system linker in (at least) 5.0.4 and 5.0.5 will sometimes | |
1951 | do the wrong thing for a construct that GCC will emit for PIC | |
1952 | code. This can be seen as execution testsuite failures when using | |
1953 | @option{-fPIC} on @file{921215-1.c}, @file{931002-1.c}, @file{nestfunc-1.c}, and @file{gcov-1.c}. | |
1954 | For 5.0.5, an updated linker that will cure this problem is | |
1955 | available. You must install both | |
1956 | @uref{ftp://ftp.sco.com/Supplements/rs505a/,,ftp://ftp.sco.com/Supplements/rs505a/} | |
1957 | and @uref{ftp://ftp.sco.com/SLS/,,OSS499A}. | |
1958 | ||
1959 | The dynamic linker in OpenServer 5.0.5 (earlier versions may show | |
1960 | the same problem) aborts on certain G77-compiled programs. It's particularly | |
1961 | likely to be triggered by building Fortran code with the @option{-fPIC} flag. | |
1962 | Although it's conceivable that the error could be triggered by other | |
1963 | code, only G77-compiled code has been observed to cause this abort. | |
1964 | If you are getting core dumps immediately upon execution of your | |
1965 | G77 program---and especially if it's compiled with @option{-fPIC}---try applying | |
1966 | @uref{sco_osr5_g77.patch,,@file{sco_osr5_g77.patch}} to your @samp{libf2c} and | |
1967 | rebuilding GCC@. | |
1968 | Affected faults, when analyzed in a debugger, will show a stack | |
1969 | backtrace with a fault occurring in @code{rtld()} and the program | |
1970 | running as @file{/usr/lib/ld.so.1}. This problem has been reported to SCO | |
1971 | engineering and will hopefully be addressed in later releases. | |
1972 | ||
1973 | ||
1974 | @html | |
1975 | </p> | |
1976 | <hr> | |
1977 | @end html | |
1978 | @heading @anchor{ix86-*-udk}i?86-*-udk | |
1979 | ||
1980 | This target emulates the SCO Universal Development Kit and requires that | |
1981 | package be installed. (If it is installed, you will have a | |
1982 | @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the | |
1983 | @code{i?86-*-unixware7*} target | |
1984 | but is meant to be used when hosting on a system where UDK isn't the | |
1985 | default compiler such as OpenServer 5 or Unixware 2. This target will | |
1986 | generate binaries that will run on OpenServer, Unixware 2, or Unixware 7, | |
1987 | with the same warnings and caveats as the SCO UDK@. | |
1988 | ||
1989 | This target is a little tricky to build because we have to distinguish | |
1990 | it from the native tools (so it gets headers, startups, and libraries | |
1991 | from the right place) while making the tools not think we're actually | |
1992 | building a cross compiler. The easiest way to do this is with a configure | |
1993 | command like this: | |
1994 | ||
1995 | @samp{CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure | |
1996 | --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-} | |
1997 | ||
1998 | @emph{You should substitute @samp{i686} in the above command with the appropriate | |
1999 | processor for your host.} | |
2000 | ||
2001 | After the usual @samp{make bootstrap} and | |
2002 | @samp{make install}, you can then access the UDK-targeted GCC | |
2003 | tools by adding @command{udk-} before the commonly known name. For | |
2004 | example, to invoke the C compiler, you would use @command{udk-gcc}. | |
2005 | They will coexist peacefully with any native-target GCC tools you may | |
2006 | have installed. | |
2007 | ||
2008 | ||
2009 | @html | |
2010 | </p> | |
2011 | <hr> | |
2012 | @end html | |
2013 | @heading @anchor{ix86-*-isc}i?86-*-isc | |
2014 | It may be a good idea to link with GNU malloc instead of the malloc that | |
2015 | comes with the system. | |
2016 | ||
2017 | In ISC version 4.1, @command{sed} core dumps when building | |
2018 | @file{deduced.h}. Use the version of @command{sed} from version 4.0. | |
2019 | ||
2020 | @html | |
2021 | </p> | |
2022 | <hr> | |
2023 | @end html | |
2024 | @heading @anchor{ix86-*-esix}i?86-*-esix | |
2025 | It may be good idea to link with GNU malloc instead of the malloc that | |
2026 | comes with the system. | |
2027 | ||
2028 | @html | |
2029 | </p> | |
2030 | <hr> | |
2031 | @end html | |
2032 | @heading @anchor{ix86-ibm-aix}i?86-ibm-aix | |
2033 | You need to use GAS version 2.1 or later, and LD from | |
2034 | GNU binutils version 2.2 or later. | |
2035 | ||
2036 | @html | |
2037 | </p> | |
2038 | <hr> | |
2039 | @end html | |
2040 | @heading @anchor{ix86-sequent-bsd}i?86-sequent-bsd | |
2041 | Go to the Berkeley universe before compiling. | |
2042 | ||
2043 | @html | |
2044 | </p> | |
2045 | <hr> | |
2046 | @end html | |
2047 | @heading @anchor{ix86-sequent-ptx1*}i?86-sequent-ptx1*, i?86-sequent-ptx2* | |
2048 | You must install GNU @command{sed} before running @command{configure}. | |
2049 | ||
2050 | @html | |
2051 | </p> | |
2052 | <hr> | |
2053 | @end html | |
2054 | @heading @anchor{#ix86-*-sysv3*}i?86-*-sysv3* | |
2055 | The @code{fixproto} shell script may trigger a bug in the system shell. | |
2056 | If you encounter this problem, upgrade your operating system or | |
2057 | use @command{bash} (the GNU shell) to run @code{fixproto}. | |
2058 | ||
2059 | ||
2060 | @html | |
2061 | </p> | |
2062 | <hr> | |
2063 | @end html | |
2064 | @heading @anchor{i860-intel-osf*}i860-intel-osf* | |
2065 | On the Intel Paragon (an i860 machine), if you are using operating | |
2066 | system version 1.0, you will get warnings or errors about redefinition | |
2067 | of @code{va_arg} when you build GCC@. | |
2068 | ||
2069 | If this happens, then you need to link most programs with the library | |
2070 | @file{iclib.a}. You must also modify @file{stdio.h} as follows: before | |
2071 | the lines | |
2072 | ||
2073 | @example | |
2074 | #if defined(__i860__) && !defined(_VA_LIST) | |
2075 | #include <va_list.h> | |
2076 | @end example | |
2077 | ||
2078 | @noindent | |
2079 | insert the line | |
2080 | ||
2081 | @example | |
2082 | #if __PGC__ | |
2083 | @end example | |
2084 | ||
2085 | @noindent | |
2086 | and after the lines | |
2087 | ||
2088 | @example | |
2089 | extern int vprintf(const char *, va_list ); | |
2090 | extern int vsprintf(char *, const char *, va_list ); | |
2091 | #endif | |
2092 | @end example | |
2093 | ||
2094 | @noindent | |
2095 | insert the line | |
2096 | ||
2097 | @example | |
2098 | #endif /* __PGC__ */ | |
2099 | @end example | |
2100 | ||
2101 | These problems don't exist in operating system version 1.1. | |
2102 | ||
2103 | @html | |
2104 | </p> | |
2105 | <hr> | |
2106 | @end html | |
2107 | @heading @anchor{*-lynx-lynxos}*-lynx-lynxos | |
2108 | LynxOS 2.2 and earlier comes with GCC 1.x already installed as | |
2109 | @file{/bin/gcc}. You should compile with this instead of @file{/bin/cc}. | |
2110 | You can tell GCC to use the GNU assembler and linker, by specifying | |
2111 | @samp{--with-gnu-as --with-gnu-ld} when configuring. These will produce | |
2112 | COFF format object files and executables; otherwise GCC will use the | |
2113 | installed tools, which produce @file{a.out} format executables. | |
2114 | ||
2115 | @html | |
2116 | </p> | |
2117 | <hr> | |
2118 | <!-- rs6000-ibm-aix*, powerpc-ibm-aix* --> | |
2119 | @end html | |
2120 | @heading @anchor{*-ibm-aix*}*-ibm-aix* | |
2121 | ||
2122 | AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or | |
2123 | newer is recommended to build on this platform. | |
2124 | ||
2125 | Errors involving @code{alloca} when building GCC generally are due | |
2126 | to an incorrect definition of @code{CC} in the Makefile or mixing files | |
2127 | compiled with the native C compiler and GCC@. During the stage1 phase of | |
2128 | the build, the native AIX compiler @strong{must} be invoked as @command{cc} | |
2129 | (not @command{xlc}). Once @command{configure} has been informed of | |
2130 | @command{xlc}, one needs to use @samp{make distclean} to remove the | |
2131 | configure cache files and ensure that @env{CC} environment variable | |
2132 | does not provide a definition that will confuse @command{configure}. | |
2133 | If this error occurs during stage2 or later, then the problem most likely | |
2134 | is the version of Make (see above). | |
2135 | ||
2136 | Binutils 2.10 does not support AIX 4.3. Binutils available from the | |
2137 | @uref{http://www-1.ibm.com/servers/aix/products/aixos/linux/,,AIX | |
2138 | Toolbox for Linux: GNU and Open Source tools for AIX}; | |
2139 | website does work. Binutils 2.11 is expected to include AIX 4.3 | |
2140 | support. The GNU Assembler is necessary for @samp{libstdc++} to build. The | |
2141 | AIX native @command{ld} still is recommended. The native AIX tools do | |
2142 | interoperate with GCC@. | |
2143 | ||
2144 | Linking executables and shared libraries may produce warnings of | |
2145 | duplicate symbols. The assembly files generated by GCC for AIX always | |
2146 | have included multiple symbol definitions for certain global variable | |
2147 | and function declarations in the original program. The warnings should | |
2148 | not prevent the linker from producing a correct library or runnable | |
2149 | executable. | |
2150 | ||
2151 | AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and | |
2152 | 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1 | |
2153 | to parse archive libraries did not handle the new format correctly. | |
2154 | These routines are used by GCC and result in error messages during | |
2155 | linking such as ``not a COFF file''. The version of the routines shipped | |
2156 | with AIX 4.3.1 should work for a 32-bit environment. The @option{-g} | |
2157 | option of the archive command may be used to create archives of 32-bit | |
2158 | objects using the original ``small format''. A correct version of the | |
2159 | routines is shipped with AIX 4.3.2. | |
2160 | ||
2161 | Some versions of the AIX binder (linker) can fail with a relocation | |
2162 | overflow severe error when the @option{-bbigtoc} option is used to link | |
2163 | GCC-produced object files into an executable that overflows the TOC@. A fix | |
2164 | for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is | |
2165 | available from IBM Customer Support and from its | |
2166 | @uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com} | |
2167 | website as PTF U455193. | |
2168 | ||
2169 | The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core | |
2170 | with a segmentation fault when invoked by any version of GCC@. A fix for | |
2171 | APAR IX87327 is available from IBM Customer Support and from its | |
2172 | @uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com} | |
2173 | website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above. | |
2174 | ||
2175 | The initial assembler shipped with AIX 4.3.0 generates incorrect object | |
2176 | files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS | |
2177 | TO ASSEMBLE/BIND) is available from IBM Customer Support and from its | |
2178 | @uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com} | |
2179 | website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above. | |
2180 | ||
2181 | AIX provides National Language Support (NLS)@. Compilers and assemblers | |
2182 | use NLS to support locale-specific representations of various data | |
2183 | formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for | |
2184 | separating decimal fractions). There have been problems reported where | |
2185 | GCC does not produce the same floating-point formats that the assembler | |
2186 | expects. If one encounters this problem, set the @env{LANG} | |
2187 | environment variable to @samp{C} or @samp{En_US}. | |
2188 | ||
2189 | By default, GCC for AIX 4.1 and above produces code that can be used on | |
2190 | both Power or PowerPC processors. | |
2191 | ||
2192 | You can specify a default version for the @option{-mcpu=@var{cpu_type}} | |
2193 | switch by using the configure option @option{--with-cpu-@var{cpu_type}}. | |
2194 | ||
2195 | @html | |
2196 | </p> | |
2197 | <hr> | |
2198 | @end html | |
2199 | @heading @anchor{m32r-*-elf}m32r-*-elf | |
2200 | Mitsubishi M32R processor. | |
2201 | This configuration is intended for embedded systems. | |
2202 | ||
2203 | @html | |
2204 | </p> | |
2205 | <hr> | |
2206 | @end html | |
2207 | @heading @anchor{m68000-hp-bsd}m68000-hp-bsd | |
2208 | HP 9000 series 200 running BSD@. Note that the C compiler that comes | |
2209 | with this system cannot compile GCC; contact @email{law@@cygnus.com} | |
2210 | to get binaries of GCC for bootstrapping. | |
2211 | ||
2212 | @html | |
2213 | </p> | |
2214 | <hr> | |
2215 | @end html | |
2216 | @heading @anchor{m6811-elf}m6811-elf | |
2217 | Motorola 68HC11 family micro controllers. These are used in embedded | |
2218 | applications. There are no standard Unix configurations. | |
2219 | ||
2220 | @html | |
2221 | </p> | |
2222 | <hr> | |
2223 | @end html | |
2224 | @heading @anchor{m6812-elf}m6812-elf | |
2225 | Motorola 68HC12 family micro controllers. These are used in embedded | |
2226 | applications. There are no standard Unix configurations. | |
2227 | ||
2228 | @html | |
2229 | </p> | |
2230 | <hr> | |
2231 | @end html | |
2232 | @heading @anchor{m68k-altos}m68k-altos | |
2233 | Altos 3068. You must use the GNU assembler, linker and debugger. | |
2234 | Also, you must fix a kernel bug. | |
2235 | ||
2236 | @html | |
2237 | </p> | |
2238 | <hr> | |
2239 | @end html | |
2240 | @heading @anchor{m68k-apple-aux}m68k-apple-aux | |
2241 | Apple Macintosh running A/UX@. | |
2242 | You may configure GCC to use either the system assembler and | |
2243 | linker or the GNU assembler and linker. You should use the GNU configuration | |
2244 | if you can, especially if you also want to use G++. You enable | |
2245 | that configuration with the @option{--with-gnu-as} and @option{--with-gnu-ld} | |
2246 | options to @code{configure}. | |
2247 | ||
2248 | Note the C compiler that comes | |
2249 | with this system cannot compile GCC@. You can find binaries of GCC | |
2250 | for bootstrapping on @code{jagubox.gsfc.nasa.gov}. | |
2251 | You will also a patched version of @file{/bin/ld} there that | |
2252 | raises some of the arbitrary limits found in the original. | |
2253 | ||
2254 | @html | |
2255 | </p> | |
2256 | <hr> | |
2257 | @end html | |
2258 | @heading @anchor{m68k-att-sysv}m68k-att-sysv | |
2259 | AT&T 3b1, a.k.a.@: 7300 PC@. This version of GCC cannot | |
2260 | be compiled with the system C compiler, which is too buggy. | |
2261 | You will need to get a previous version of GCC and use it to | |
2262 | bootstrap. Binaries are available from the OSU-CIS archive, at | |
2263 | @uref{ftp://archive.cis.ohio-state.edu/pub/att7300/}. | |
2264 | ||
2265 | @html | |
2266 | </p> | |
2267 | <hr> | |
2268 | @end html | |
2269 | @heading @anchor{m68k-bull-sysv}m68k-bull-sysv | |
2270 | Bull DPX/2 series 200 and 300 with BOS-2.00.45 up to BOS-2.01. GCC works | |
2271 | either with native assembler or GNU assembler. You can use | |
2272 | GNU assembler with native COFF generation by providing @option{--with-gnu-as} to | |
2273 | the configure script or use GNU assembler with stabs-in-COFF encapsulation | |
2274 | by providing @samp{--with-gnu-as --stabs}. For any problem with the native | |
2275 | assembler or for availability of the DPX/2 port of GAS, contact | |
2276 | @email{F.Pierresteguy@@frcl.bull.fr}. | |
2277 | ||
2278 | @html | |
2279 | </p> | |
2280 | <hr> | |
2281 | @end html | |
2282 | @heading @anchor{m68k-crds-unox}m68k-crds-unox | |
2283 | Use @samp{configure unos} for building on Unos. | |
2284 | ||
2285 | The Unos assembler is named @code{casm} instead of @code{as}. For some | |
2286 | strange reason linking @file{/bin/as} to @file{/bin/casm} changes the | |
2287 | behavior, and does not work. So, when installing GCC, you should | |
2288 | install the following script as @file{as} in the subdirectory where | |
2289 | the passes of GCC are installed: | |
2290 | ||
2291 | @example | |
2292 | #!/bin/sh | |
2293 | casm $* | |
2294 | @end example | |
2295 | ||
2296 | The default Unos library is named @file{libunos.a} instead of | |
2297 | @file{libc.a}. To allow GCC to function, either change all | |
2298 | references to @option{-lc} in @file{gcc.c} to @option{-lunos} or link | |
2299 | @file{/lib/libc.a} to @file{/lib/libunos.a}. | |
2300 | ||
2301 | @cindex @code{alloca}, for Unos | |
2302 | When compiling GCC with the standard compiler, to overcome bugs in | |
2303 | the support of @code{alloca}, do not use @option{-O} when making stage 2. | |
2304 | Then use the stage 2 compiler with @option{-O} to make the stage 3 | |
2305 | compiler. This compiler will have the same characteristics as the usual | |
2306 | stage 2 compiler on other systems. Use it to make a stage 4 compiler | |
2307 | and compare that with stage 3 to verify proper compilation. | |
2308 | ||
2309 | (Perhaps simply defining @code{ALLOCA} in @file{x-crds} as described in | |
2310 | the comments there will make the above paragraph superfluous. Please | |
2311 | inform us of whether this works.) | |
2312 | ||
2313 | Unos uses memory segmentation instead of demand paging, so you will need | |
2314 | a lot of memory. 5 Mb is barely enough if no other tasks are running. | |
2315 | If linking @file{cc1} fails, try putting the object files into a library | |
2316 | and linking from that library. | |
2317 | ||
2318 | @html | |
2319 | </p> | |
2320 | <hr> | |
2321 | @end html | |
2322 | @heading @anchor{m68k-hp-hpux}m68k-hp-hpux | |
2323 | HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in | |
2324 | the assembler that prevents compilation of GCC@. This | |
2325 | bug manifests itself during the first stage of compilation, while | |
2326 | building @file{libgcc2.a}: | |
2327 | ||
2328 | @smallexample | |
2329 | _floatdisf | |
2330 | cc1: warning: `-g' option not supported on this version of GCC | |
2331 | cc1: warning: `-g1' option not supported on this version of GCC | |
2332 | ./xgcc: Internal compiler error: program as got fatal signal 11 | |
2333 | @end smallexample | |
2334 | ||
2335 | A patched version of the assembler is available as the file | |
2336 | @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you | |
2337 | have HP software support, the patch can also be obtained directly from | |
2338 | HP, as described in the following note: | |
2339 | ||
2340 | @quotation | |
2341 | This is the patched assembler, to patch SR#1653-010439, where the | |
2342 | assembler aborts on floating point constants. | |
2343 | ||
2344 | The bug is not really in the assembler, but in the shared library | |
2345 | version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is | |
2346 | SR#4701-078451. Anyway, the attached assembler uses the archive | |
2347 | library version of ``cvtnum(3c)'' and thus does not exhibit the bug. | |
2348 | @end quotation | |
2349 | ||
2350 | This patch is also known as PHCO_4484. | |
2351 | ||
2352 | In addition, if you wish to use gas, you must use | |
2353 | gas version 2.1 or later, and you must use the GNU linker version 2.1 or | |
2354 | later. Earlier versions of gas relied upon a program which converted the | |
2355 | gas output into the native HP-UX format, but that program has not been | |
2356 | kept up to date. gdb does not understand that native HP-UX format, so | |
2357 | you must use gas if you wish to use gdb. | |
2358 | ||
2359 | On HP-UX version 8.05, but not on 8.07 or more recent versions, the | |
2360 | @code{fixproto} shell script triggers a bug in the system shell. If you | |
2361 | encounter this problem, upgrade your operating system or use BASH (the | |
2362 | GNU shell) to run @code{fixproto}. This bug will cause the fixproto | |
2363 | program to report an error of the form: | |
2364 | ||
2365 | @example | |
2366 | ./fixproto: sh internal 1K buffer overflow | |
2367 | @end example | |
2368 | ||
2369 | To fix this, you can also change the first line of the fixproto script | |
2370 | to look like: | |
2371 | ||
2372 | @example | |
2373 | #!/bin/ksh | |
2374 | @end example | |
2375 | ||
2376 | ||
2377 | @html | |
2378 | </p> | |
2379 | <hr> | |
2380 | @end html | |
2381 | @heading @anchor{m68k-*-nextstep*}m68k-*-nextstep* | |
2382 | ||
2383 | Current GCC versions probably do not work on version 2 of the NeXT | |
2384 | operating system. | |
2385 | ||
2386 | On NeXTStep 3.0, the Objective-C compiler does not work, due, | |
2387 | apparently, to a kernel bug that it happens to trigger. This problem | |
2388 | does not happen on 3.1. | |
2389 | ||
2390 | You absolutely @strong{must} use GNU sed and GNU make on this platform. | |
2391 | ||
2392 | ||
2393 | On NeXTSTEP 3.x where x < 3 the build of GCC will abort during | |
2394 | stage1 with an error message like this: | |
2395 | ||
2396 | @example | |
2397 | _eh | |
2398 | /usr/tmp/ccbbsZ0U.s:987:Unknown pseudo-op: .section | |
2399 | /usr/tmp/ccbbsZ0U.s:987:Rest of line ignored. 1st junk character | |
2400 | valued 95 (_). | |
2401 | @end example | |
2402 | ||
2403 | The reason for this is the fact that NeXT's assembler for these | |
2404 | versions of the operating system does not support the @samp{.section} | |
2405 | pseudo op that's needed for full C++ exception functionality. | |
2406 | ||
2407 | As NeXT's assembler is a derived work from GNU as, a free | |
2408 | replacement that does can be obtained at | |
2409 | @uref{ftp://ftp.next.peak.org:/next-ftp/next/apps/devtools/as.3.3.NIHS.s.tar.gz,,ftp://ftp.next.peak.org:/next-ftp/next/apps/devtools/as.3.3.NIHS.s.tar.gz}. | |
2410 | ||
2411 | If you try to build the integrated C++ & C++ runtime libraries on this system | |
2412 | you will run into trouble with include files. The way to get around this is | |
2413 | to use the following sequence. Note you must have write permission to | |
2414 | the directory @var{prefix} you specified in the configuration process of GCC | |
2415 | for this sequence to work. | |
2416 | ||
2417 | @example | |
2418 | cd bld-gcc | |
2419 | make all-texinfo all-bison all-byacc all-binutils all-gas all-ld | |
2420 | cd gcc | |
2421 | make bootstrap | |
2422 | make install-headers-tar | |
2423 | cd .. | |
2424 | make bootstrap3 | |
2425 | @end example | |
2426 | ||
2427 | @html | |
2428 | </p> | |
2429 | <hr> | |
2430 | @end html | |
2431 | @heading @anchor{m68k-ncr-*}m68k-ncr-* | |
2432 | On the Tower models 4@var{n}0 and 6@var{n}0, by default a process is not | |
2433 | allowed to have more than one megabyte of memory. GCC cannot compile | |
2434 | itself (or many other programs) with @option{-O} in that much memory. | |
2435 | ||
2436 | To solve this problem, reconfigure the kernel adding the following line | |
2437 | to the configuration file: | |
2438 | ||
2439 | @smallexample | |
2440 | MAXUMEM = 4096 | |
2441 | @end smallexample | |
2442 | ||
2443 | ||
2444 | @html | |
2445 | </p> | |
2446 | <hr> | |
2447 | @end html | |
2448 | @heading @anchor{m68k-sun}m68k-sun | |
2449 | Sun 3. We do not provide a configuration file to use the Sun FPA by | |
2450 | default, because programs that establish signal handlers for floating | |
2451 | point traps inherently cannot work with the FPA@. | |
2452 | ||
2453 | @html | |
2454 | </p> | |
2455 | <hr> | |
2456 | @end html | |
2457 | @heading @anchor{m68k-sun-sunos4.1.1}m68k-sun-sunos4.1.1 | |
2458 | ||
2459 | It is reported that you may need the GNU assembler on this platform. | |
2460 | ||
2461 | ||
2462 | @html | |
2463 | </p> | |
2464 | <hr> | |
2465 | @end html | |
2466 | @heading @anchor{m88k-*-svr3}m88k-*-svr3 | |
2467 | Motorola m88k running the AT&T/Unisoft/Motorola V.3 reference port. | |
2468 | These systems tend to use the Green Hills C, revision 1.8.5, as the | |
2469 | standard C compiler. There are apparently bugs in this compiler that | |
2470 | result in object files differences between stage 2 and stage 3. If this | |
2471 | happens, make the stage 4 compiler and compare it to the stage 3 | |
2472 | compiler. If the stage 3 and stage 4 object files are identical, this | |
2473 | suggests you encountered a problem with the standard C compiler; the | |
2474 | stage 3 and 4 compilers may be usable. | |
2475 | ||
2476 | It is best, however, to use an older version of GCC for bootstrapping | |
2477 | if you have one. | |
2478 | ||
2479 | @html | |
2480 | </p> | |
2481 | <hr> | |
2482 | @end html | |
2483 | @heading @anchor{m88k-*-dgux}m88k-*-dgux | |
2484 | Motorola m88k running DG/UX@. To build 88open BCS native or cross | |
2485 | compilers on DG/UX, specify the configuration name as | |
2486 | @samp{m88k-*-dguxbcs} and build in the 88open BCS software development | |
2487 | environment. To build ELF native or cross compilers on DG/UX, specify | |
2488 | @samp{m88k-*-dgux} and build in the DG/UX ELF development environment. | |
2489 | You set the software development environment by issuing | |
2490 | @samp{sde-target} command and specifying either @samp{m88kbcs} or | |
2491 | @samp{m88kdguxelf} as the operand. | |
2492 | ||
2493 | If you do not specify a configuration name, @file{configure} guesses the | |
2494 | configuration based on the current software development environment. | |
2495 | ||
2496 | @html | |
2497 | </p> | |
2498 | <hr> | |
2499 | @end html | |
2500 | @heading @anchor{m88k-tektronix-sysv3}m88k-tektronix-sysv3 | |
2501 | Tektronix XD88 running UTekV 3.2e. Do not turn on | |
2502 | optimization while building stage1 if you bootstrap with | |
2503 | the buggy Green Hills compiler. Also, the bundled LAI | |
2504 | System V NFS is buggy so if you build in an NFS mounted | |
2505 | directory, start from a fresh reboot, or avoid NFS all together. | |
2506 | Otherwise you may have trouble getting clean comparisons | |
2507 | between stages. | |
2508 | ||
2509 | @html | |
2510 | </p> | |
2511 | <hr> | |
2512 | @end html | |
2513 | @heading @anchor{mips-*-*}mips-*-* | |
2514 | If you use the 1.31 version of the MIPS assembler (such as was shipped | |
2515 | with Ultrix 3.1), you will need to use the @option{-fno-delayed-branch} switch | |
2516 | when optimizing floating point code. Otherwise, the assembler will | |
2517 | complain when the GCC compiler fills a branch delay slot with a | |
2518 | floating point instruction, such as @code{add.d}. | |
2519 | ||
2520 | If on a MIPS system you get an error message saying ``does not have gp | |
2521 | sections for all it's [sic] sectons [sic]'', don't worry about it. This | |
2522 | happens whenever you use GAS with the MIPS linker, but there is not | |
2523 | really anything wrong, and it is okay to use the output file. You can | |
2524 | stop such warnings by installing the GNU linker. | |
2525 | ||
2526 | It would be nice to extend GAS to produce the gp tables, but they are | |
2527 | optional, and there should not be a warning about their absence. | |
2528 | ||
2529 | Users have reported some problems with version 2.0 of the MIPS | |
2530 | compiler tools that were shipped with Ultrix 4.1. Version 2.10 | |
2531 | which came with Ultrix 4.2 seems to work fine. | |
2532 | ||
2533 | Users have also reported some problems with version 2.20 of the | |
2534 | MIPS compiler tools that were shipped with RISC/os 4.x. The earlier | |
2535 | version 2.11 seems to work fine. | |
2536 | ||
2537 | Some versions of the MIPS linker will issue an assertion failure | |
2538 | when linking code that uses @code{alloca} against shared | |
2539 | libraries on RISC-OS 5.0, and DEC's OSF/1 systems. This is a bug | |
2540 | in the linker, that is supposed to be fixed in future revisions. | |
2541 | To protect against this, GCC passes @option{-non_shared} to the | |
2542 | linker unless you pass an explicit @option{-shared} or | |
2543 | @option{-call_shared} switch. | |
2544 | ||
2545 | @heading @anchor{mips-mips-bsd}mips-mips-bsd | |
2546 | MIPS machines running the MIPS operating system in BSD mode. It's | |
2547 | possible that some old versions of the system lack the functions | |
2548 | @code{memcpy}, @code{memmove}, @code{memcmp}, and @code{memset}. If your | |
2549 | system lacks these, you must remove or undo the definition of | |
2550 | @code{TARGET_MEM_FUNCTIONS} in @file{mips-bsd.h}. | |
2551 | ||
2552 | If you use the MIPS C compiler to bootstrap, it may be necessary | |
2553 | to increase its table size for switch statements with the | |
2554 | @option{-Wf,-XNg1500} option. If you use the @option{-O2} | |
2555 | optimization option, you also need to use @option{-Olimit 3000}. | |
2556 | Both of these options are automatically generated in the | |
2557 | @file{Makefile} that the shell script @file{configure} builds. | |
2558 | If you override the @code{CC} make variable and use the MIPS | |
2559 | compilers, you may need to add @option{-Wf,-XNg1500 -Olimit 3000}. | |
2560 | ||
2561 | @html | |
2562 | </p> | |
2563 | <hr> | |
2564 | @end html | |
2565 | @heading @anchor{mips-dec-*}mips-dec-* | |
2566 | MIPS-based DECstations can support three different personalities: | |
2567 | Ultrix, DEC OSF/1, and OSF/rose. (Alpha-based DECstation products have | |
2568 | a configuration name beginning with @samp{alpha*-dec}.) To configure GCC | |
2569 | for these platforms use the following configurations: | |
2570 | ||
2571 | @table @samp | |
2572 | @item mips-dec-ultrix | |
2573 | Ultrix configuration. | |
2574 | ||
2575 | @item mips-dec-osf1 | |
2576 | DEC's version of OSF/1. | |
2577 | ||
2578 | @item mips-dec-osfrose | |
2579 | Open Software Foundation reference port of OSF/1 which uses the | |
2580 | OSF/rose object file format instead of ECOFF@. Normally, you | |
2581 | would not select this configuration. | |
2582 | @end table | |
2583 | ||
2584 | If you use the MIPS C compiler to bootstrap, it may be necessary | |
2585 | to increase its table size for switch statements with the | |
2586 | @option{-Wf,-XNg1500} option. If you use the @option{-O2} | |
2587 | optimization option, you also need to use @option{-Olimit 3000}. | |
2588 | Both of these options are automatically generated in the | |
2589 | @file{Makefile} that the shell script @file{configure} builds. | |
2590 | If you override the @code{CC} make variable and use the MIPS | |
2591 | compilers, you may need to add @option{-Wf,-XNg1500 -Olimit 3000}. | |
2592 | ||
2593 | @html | |
2594 | </p> | |
2595 | <hr> | |
2596 | @end html | |
2597 | @heading @anchor{mips-mips-riscos*}mips-mips-riscos* | |
2598 | If you use the MIPS C compiler to bootstrap, it may be necessary | |
2599 | to increase its table size for switch statements with the | |
2600 | @option{-Wf,-XNg1500} option. If you use the @option{-O2} | |
2601 | optimization option, you also need to use @option{-Olimit 3000}. | |
2602 | Both of these options are automatically generated in the | |
2603 | @file{Makefile} that the shell script @file{configure} builds. | |
2604 | If you override the @code{CC} make variable and use the MIPS | |
2605 | compilers, you may need to add @samp{-Wf,-XNg1500 -Olimit 3000}. | |
2606 | ||
2607 | MIPS computers running RISC-OS can support four different | |
2608 | personalities: default, BSD 4.3, System V.3, and System V.4 | |
2609 | (older versions of RISC-OS don't support V.4). To configure GCC | |
2610 | for these platforms use the following configurations: | |
2611 | ||
2612 | @table @samp | |
2613 | @item mips-mips-riscos@var{rev} | |
2614 | Default configuration for RISC-OS, revision @var{rev}. | |
2615 | ||
2616 | @item mips-mips-riscos@var{rev}bsd | |
2617 | BSD 4.3 configuration for RISC-OS, revision @var{rev}. | |
2618 | ||
2619 | @item mips-mips-riscos@var{rev}sysv4 | |
2620 | System V.4 configuration for RISC-OS, revision @var{rev}. | |
2621 | ||
2622 | @html | |
2623 | </p> | |
2624 | <hr> | |
2625 | @end html | |
2626 | @item mips-mips-riscos@var{rev}sysv | |
2627 | System V.3 configuration for RISC-OS, revision @var{rev}. | |
2628 | @end table | |
2629 | ||
2630 | The revision @code{rev} mentioned above is the revision of | |
2631 | RISC-OS to use. You must reconfigure GCC when going from a | |
2632 | RISC-OS revision 4 to RISC-OS revision 5. This has the effect of | |
2633 | avoiding a linker bug. | |
2634 | ||
2635 | @html | |
2636 | </p> | |
2637 | <hr> | |
2638 | @end html | |
2639 | @heading @anchor{mips*-sgi-irix4*}mips*-sgi-irix4* | |
2640 | ||
2641 | In order to compile GCC on an SGI running IRIX 4, the ``c.hdr.lib'' | |
2642 | option must be installed from the CD-ROM supplied from Silicon Graphics. | |
2643 | This is found on the 2nd CD in release 4.0.1. | |
2644 | ||
2645 | On IRIX version 4.0.5F, and perhaps on some other versions as well, | |
2646 | there is an assembler bug that reorders instructions incorrectly. To | |
2647 | work around it, specify the target configuration | |
2648 | @samp{mips-sgi-irix4loser}. This configuration inhibits assembler | |
2649 | optimization. | |
2650 | ||
2651 | In a compiler configured with target @samp{mips-sgi-irix4}, you can turn | |
2652 | off assembler optimization by using the @option{-noasmopt} option. This | |
2653 | compiler option passes the option @option{-O0} to the assembler, to | |
2654 | inhibit reordering. | |
2655 | ||
2656 | The @option{-noasmopt} option can be useful for testing whether a problem | |
2657 | is due to erroneous assembler reordering. Even if a problem does not go | |
2658 | away with @option{-noasmopt}, it may still be due to assembler | |
2659 | reordering---perhaps GCC itself was miscompiled as a result. | |
2660 | ||
2661 | You may get the following warning on IRIX 4 platforms, it can be safely | |
2662 | ignored. | |
2663 | @example | |
2664 | warning: foo.o does not have gp tables for all its sections. | |
2665 | @end example | |
2666 | ||
2667 | @html | |
2668 | </p> | |
2669 | <hr> | |
2670 | @end html | |
2671 | @heading @anchor{mips*-sgi-irix5*}mips*-sgi-irix5* | |
2672 | ||
2673 | In order to compile GCC on an SGI running IRIX 5, the ``compiler_dev.hdr'' | |
2674 | subsystem must be installed from the IDO CD-ROM supplied by Silicon | |
2675 | Graphics. It is also available for download from | |
2676 | @uref{http://www.sgi.com/developers/devtools/apis/ido.html,,http://www.sgi.com/developers/devtools/apis/ido.html}. | |
2677 | ||
2678 | @code{make compare} may fail on version 5 of IRIX unless you add | |
2679 | @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the | |
2680 | assembler input file is stored in the object file, and that makes | |
2681 | comparison fail if it differs between the @code{stage1} and | |
2682 | @code{stage2} compilations. The option @option{-save-temps} forces a | |
2683 | fixed name to be used for the assembler input file, instead of a | |
2684 | randomly chosen name in @file{/tmp}. Do not add @option{-save-temps} | |
2685 | unless the comparisons fail without that option. If you do you | |
2686 | @option{-save-temps}, you will have to manually delete the @samp{.i} and | |
2687 | @samp{.s} files after each series of compilations. | |
2688 | ||
2689 | If you use the MIPS C compiler to bootstrap, it may be necessary | |
2690 | to increase its table size for switch statements with the | |
2691 | @option{-Wf,-XNg1500} option. If you use the @option{-O2} | |
2692 | optimization option, you also need to use @option{-Olimit 3000}. | |
2693 | ||
2694 | To enable debugging under IRIX 5, you must use GNU @command{as} 2.5 or later, | |
2695 | and use the @option{--with-gnu-as} configure option when configuring GCC. | |
2696 | GNU @command{as} is distributed as part of the binutils package. | |
2697 | ||
2698 | You must use GNU @command{as} on these platforms, as the native | |
2699 | assembler can not handle the code for exception handling support. Either | |
2700 | of these messages indicates that you are using the MIPS assembler when | |
2701 | instead you should be using GNU @command{as}: | |
2702 | ||
2703 | @example | |
2704 | as0: Error: ./libgcc2.c, line 1:Badly delimited numeric literal | |
2705 | .4byte $LECIE1-$LSCIE1 | |
2706 | as0: Error: ./libgcc2.c, line 1:malformed statement | |
2707 | @end example | |
2708 | ||
2709 | or: | |
2710 | ||
2711 | @example | |
2712 | as0: Error: ./libgcc2.c, line 1:undefined symbol in expression | |
2713 | .word $LECIE1-$LSCIE1 | |
2714 | @end example | |
2715 | ||
2716 | When building GCC, the build process loops rebuilding @command{cc1} over | |
2717 | and over again. This happens on @samp{mips-sgi-irix5.2}, and possibly | |
2718 | other platforms. It has been reported that this is a known bug in the | |
2719 | @command{make} shipped with IRIX 5.2. We recommend you use GNU | |
2720 | @command{make} instead of the vendor supplied @command{make} program; | |
2721 | however, you may have success with @command{smake} on IRIX 5.2 if you do | |
2722 | not have GNU @command{make} available. | |
2723 | ||
2724 | @html | |
2725 | </p> | |
2726 | <hr> | |
2727 | @end html | |
2728 | @heading @anchor{mips*-sgi-irix6}mips*-sgi-irix6 | |
2729 | ||
2730 | If you are using IRIX @command{cc} as your bootstrap compiler, you must | |
2731 | ensure that the N32 ABI is in use. To test this, compile a simple C | |
2732 | file with @command{cc} and then run @command{file} on the | |
2733 | resulting object file. The output should look like: | |
2734 | ||
2735 | @example | |
2736 | test.o: ELF N32 MSB @dots{} | |
2737 | @end example | |
2738 | ||
2739 | If you see: | |
2740 | ||
2741 | @example | |
2742 | test.o: ELF 32-bit MSB @dots{} | |
2743 | @end example | |
2744 | ||
2745 | or | |
2746 | ||
2747 | @example | |
2748 | test.o: ELF 64-bit MSB @dots{} | |
2749 | @end example | |
2750 | ||
2751 | then your version of @command{cc} uses the O32 or N64 ABI by default. You | |
2752 | should set the environment variable @env{CC} to @samp{cc -n32} | |
2753 | before configuring GCC@. | |
2754 | ||
2755 | GCC on IRIX 6 is usually built to support both the N32 and N64 ABIs. If | |
2756 | you build GCC on a system that doesn't have the N64 libraries installed, | |
2757 | you need to configure with @option{--disable-multilib} so GCC doesn't | |
2758 | try to use them. Look for @file{/usr/lib64/libc.so.1} to see if you | |
2759 | have the 64-bit libraries installed. | |
2760 | ||
2761 | You must @emph{not} use GNU @command{as} (which isn't built anyway as of | |
2762 | binutils 2.11.2) on IRIX 6 platforms; doing so will only cause problems. | |
2763 | ||
2764 | GCC does not currently support generating O32 ABI binaries in the | |
2765 | @samp{mips-sgi-irix6} configurations. It used to be possible to create a GCC | |
2766 | with O32 ABI only support by configuring it for the @samp{mips-sgi-irix5} | |
2767 | target, which doesn't currently (2001-06-13) work itself. It is | |
2768 | expected that O32 ABI support will be available again in a future release. | |
2769 | ||
2770 | GCC does not correctly pass/return structures which are | |
2771 | smaller than 16 bytes and which are not 8 bytes. The problem is very | |
2772 | involved and difficult to fix. It affects a number of other targets also, | |
2773 | but IRIX 6 is affected the most, because it is a 64 bit target, and 4 byte | |
2774 | structures are common. The exact problem is that structures are being padded | |
2775 | at the wrong end, e.g.@: a 4 byte structure is loaded into the lower 4 bytes | |
2776 | of the register when it should be loaded into the upper 4 bytes of the | |
2777 | register. | |
2778 | ||
2779 | GCC is consistent with itself, but not consistent with the SGI C compiler | |
2780 | (and the SGI supplied runtime libraries), so the only failures that can | |
2781 | happen are when there are library functions that take/return such | |
2782 | structures. There are very few such library functions. Currently this | |
2783 | is known to affect @code{inet_ntoa}, @code{inet_lnaof}, | |
2784 | @code{inet_netof}, @code{inet_makeaddr}, and @code{semctl}. | |
2785 | ||
2786 | See @uref{http://freeware.sgi.com/,,http://freeware.sgi.com/} for more | |
2787 | information about using GCC on IRIX platforms. | |
2788 | ||
2789 | @html | |
2790 | </p> | |
2791 | <hr> | |
2792 | @end html | |
2793 | @heading @anchor{mips-sony-sysv}mips-sony-sysv | |
2794 | Sony MIPS NEWS@. This works in NEWSOS 5.0.1, but not in 5.0.2 (which | |
2795 | uses ELF instead of COFF)@. Support for 5.0.2 will probably be provided | |
2796 | soon by volunteers. In particular, the linker does not like the | |
2797 | code generated by GCC when shared libraries are linked in. | |
2798 | ||
2799 | ||
2800 | @html | |
2801 | </p> | |
2802 | <hr> | |
2803 | @end html | |
2804 | @heading @anchor{ns32k-encore}ns32k-encore | |
2805 | Encore ns32000 system. Encore systems are supported only under BSD@. | |
2806 | ||
2807 | @html | |
2808 | </p> | |
2809 | <hr> | |
2810 | @end html | |
2811 | @heading @anchor{ns32k-*-genix}ns32k-*-genix | |
2812 | National Semiconductor ns32000 system. Genix has bugs in @code{alloca} | |
2813 | and @code{malloc}; you must get the compiled versions of these from GNU | |
2814 | Emacs. | |
2815 | ||
2816 | @html | |
2817 | </p> | |
2818 | <hr> | |
2819 | @end html | |
2820 | @heading @anchor{ns32k-sequent}ns32k-sequent | |
2821 | Go to the Berkeley universe before compiling. | |
2822 | ||
2823 | @html | |
2824 | </p> | |
2825 | <hr> | |
2826 | @end html | |
2827 | @heading @anchor{ns32k-utek}ns32k-utek | |
2828 | UTEK ns32000 system (``merlin''). The C compiler that comes with this | |
2829 | system cannot compile GCC; contact @samp{tektronix!reed!mason} to get | |
2830 | binaries of GCC for bootstrapping. | |
2831 | ||
2832 | ||
2833 | @html | |
2834 | </p> | |
2835 | <hr> | |
2836 | @end html | |
2837 | @heading @anchor{powerpc*-*-*}powerpc-*-* | |
2838 | ||
2839 | You can specify a default version for the @option{-mcpu=@var{cpu_type}} | |
2840 | switch by using the configure option @option{--with-cpu-@var{cpu_type}}. | |
2841 | ||
2842 | @html | |
2843 | </p> | |
2844 | <hr> | |
2845 | @end html | |
2846 | @heading @anchor{powerpc-*-elf}powerpc-*-elf, powerpc-*-sysv4 | |
2847 | PowerPC system in big endian mode, running System V.4. | |
2848 | ||
2849 | @html | |
2850 | </p> | |
2851 | <hr> | |
2852 | @end html | |
2853 | @heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu* | |
2854 | ||
2855 | You will need | |
2856 | @uref{ftp://ftp.varesearch.com/pub/support/hjl/binutils,,binutils 2.9.4.0.8} | |
2857 | or newer for a working GCC@. It is strongly recommended to recompile binutils | |
2858 | if you initially built it with gcc-2.7.2.x. | |
2859 | ||
2860 | @html | |
2861 | </p> | |
2862 | <hr> | |
2863 | @end html | |
2864 | @heading @anchor{powerpc-*-eabiaix}powerpc-*-eabiaix | |
2865 | Embedded PowerPC system in big endian mode with @option{-mcall-aix} selected as | |
2866 | the default. | |
2867 | ||
2868 | @html | |
2869 | </p> | |
2870 | <hr> | |
2871 | @end html | |
2872 | @heading @anchor{powerpc-*-eabisim}powerpc-*-eabisim | |
2873 | Embedded PowerPC system in big endian mode for use in running under the | |
2874 | PSIM simulator. | |
2875 | ||
2876 | @html | |
2877 | </p> | |
2878 | <hr> | |
2879 | @end html | |
2880 | @heading @anchor{powerpc-*-eabi}powerpc-*-eabi | |
2881 | Embedded PowerPC system in big endian mode. | |
2882 | ||
2883 | @html | |
2884 | </p> | |
2885 | <hr> | |
2886 | @end html | |
2887 | @heading @anchor{powerpcle-*-elf}powerpcle-*-elf, powerpcle-*-sysv4 | |
2888 | PowerPC system in little endian mode, running System V.4. | |
2889 | ||
2890 | @html | |
2891 | </p> | |
2892 | <hr> | |
2893 | @end html | |
2894 | @heading @anchor{powerpcle-*-eabisim}powerpcle-*-eabisim | |
2895 | Embedded PowerPC system in little endian mode for use in running under | |
2896 | the PSIM simulator. | |
2897 | ||
2898 | @html | |
2899 | </p> | |
2900 | <hr> | |
2901 | @end html | |
2902 | @heading @anchor{powerpcle-*-eabi}powerpcle-*-eabi | |
2903 | Embedded PowerPC system in little endian mode. | |
2904 | ||
2905 | @html | |
2906 | </p> | |
2907 | <hr> | |
2908 | @end html | |
2909 | @heading @anchor{powerpcle-*-winnt}powerpcle-*-winnt, powerpcle-*-pe | |
2910 | PowerPC system in little endian mode running Windows NT@. | |
2911 | ||
2912 | @html | |
2913 | </p> | |
2914 | <hr> | |
2915 | @end html | |
2916 | @heading @anchor{romp-*-aos}romp-*-aos, romp-*-mach | |
2917 | The only operating systems supported for the IBM RT PC are AOS and | |
2918 | MACH@. GCC does not support AIX running on the RT@. We recommend you | |
2919 | compile GCC with an earlier version of itself; if you compile GCC | |
2920 | with @command{hc}, the Metaware compiler, it will work, but you will get | |
2921 | mismatches between the stage 2 and stage 3 compilers in various files. | |
2922 | These errors are minor differences in some floating-point constants and | |
2923 | can be safely ignored; the stage 3 compiler is correct. | |
2924 | ||
2925 | @html | |
2926 | </p> | |
2927 | <hr> | |
2928 | @end html | |
2929 | @heading @anchor{*-*-solaris*}*-*-solaris* | |
2930 | ||
2931 | Starting with Solaris 2, Sun does not ship a C compiler any more. To | |
2932 | bootstrap and install GCC you first have to install a pre-built | |
2933 | compiler, see our @uref{binaries.html,,binaries page} for | |
2934 | details. | |
2935 | ||
2936 | Solaris' @file{/bin/sh} will often fail to configure @file{libstdc++-v3}, @file{boehm-gc} or | |
2937 | @file{libjava}. If you encounter this problem, set @env{CONFIG_SHELL} to | |
2938 | @file{/bin/ksh} in your environment and run @samp{make bootstrap} again. | |
2939 | Another possibility that sometimes helps is to remove | |
2940 | @file{*-*-solaris*/config.cache}. | |
2941 | ||
2942 | Sun @command{as} 4.X is broken in that it cannot cope with long symbol names. | |
2943 | A typical error message might look similar to the following: | |
2944 | ||
2945 | @samp{/usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: | |
2946 | error: can't compute value of an expression involving an external symbol.} | |
2947 | ||
2948 | This is Sun bug 4237974. This is fixed with patch 108908-02 and has | |
2949 | been fixed in later (5.x) versions of the assembler. | |
2950 | ||
2951 | @html | |
2952 | <p> | |
2953 | <hr> | |
2954 | @end html | |
2955 | @heading @anchor{sparc-sun-*}sparc-sun-* | |
2956 | Sometimes on a Sun 4 you may observe a crash in the program | |
2957 | @command{genflags} or @command{genoutput} while building GCC@. This is said to | |
2958 | be due to a bug in @command{sh}. You can probably get around it by running | |
2959 | @command{genflags} or @command{genoutput} manually and then retrying the | |
2960 | @command{make}. | |
2961 | ||
2962 | @html | |
2963 | <p> | |
2964 | <hr> | |
2965 | @end html | |
2966 | @heading @anchor{sparc-sun-solaris*}sparc-sun-solaris* | |
2967 | On Solaris 2, executables of GCC version 2.0.2 are commonly | |
2968 | available, but they have a bug that shows up when compiling current | |
2969 | versions of GCC: undefined symbol errors occur during assembly if you | |
2970 | use @option{-g}. | |
2971 | ||
2972 | The solution is to compile the current version of GCC without | |
2973 | @option{-g}. That makes a working compiler which you can use to recompile | |
2974 | with @option{-g}. | |
2975 | ||
2976 | Solaris 2 comes with a number of optional OS packages. Some of these | |
2977 | packages are needed to use GCC fully. If you did not install all | |
2978 | optional packages when installing Solaris, you will need to verify that | |
2979 | the packages that GCC needs are installed. | |
2980 | ||
2981 | To check whether an optional package is installed, use | |
2982 | the @code{pkginfo} command. To add an optional package, use the | |
2983 | @code{pkgadd} command. For further details, see the Solaris | |
2984 | documentation. | |
2985 | ||
2986 | For Solaris 2.0 and 2.1, GCC needs six packages: @samp{SUNWarc}, | |
2987 | @samp{SUNWbtool}, @samp{SUNWesu}, @samp{SUNWhea}, @samp{SUNWlibm}, and | |
2988 | @samp{SUNWtoo}. | |
2989 | ||
2990 | For Solaris 2.2, GCC needs an additional seventh package: @samp{SUNWsprot}. | |
2991 | ||
2992 | On Solaris 2, trying to use the linker and other tools in | |
2993 | @file{/usr/ucb} to install GCC has been observed to cause trouble. | |
2994 | For example, the linker may hang indefinitely. The fix is to remove | |
2995 | @file{/usr/ucb} from your @code{PATH}. | |
2996 | ||
2997 | All releases of GNU binutils prior to 2.11.2 have known bugs on this | |
2998 | platform. We recommend the use of GNU binutils 2.11.2 or the vendor | |
2999 | tools (Sun @command{as}, Sun @command{ld}). | |
3000 | ||
3001 | Unfortunately, C++ shared libraries, including @samp{libstdc++}, won't work | |
3002 | properly if assembled with Sun @command{as}: the linker will complain about | |
3003 | relocations in read-only sections, in the definition of virtual | |
3004 | tables. Also, Sun @command{as} fails to process long symbols resulting from | |
3005 | mangling template-heavy C++ function names. | |
3006 | ||
3007 | @html | |
3008 | </p> | |
3009 | <hr> | |
3010 | @end html | |
3011 | @heading @anchor{sparc-sun-solaris2.7}sparc-sun-solaris2.7 | |
3012 | ||
3013 | Sun patch 107058-01 (1999-01-13) for SPARC Solaris 7 triggers a bug in | |
3014 | the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8 | |
3015 | and later, including all EGCS releases. Sun formerly recommended | |
3016 | 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to | |
3017 | recommend it only for people who use Sun's compilers. | |
3018 | ||
3019 | Here are some workarounds to this problem: | |
3020 | @itemize @bullet | |
3021 | @item | |
3022 | Do not install Sun patch 107058-01 until after Sun releases a | |
3023 | complete patch for bug 4210064. This is the simplest course to take, | |
3024 | unless you must also use Sun's C compiler. Unfortunately 107058-01 | |
3025 | is preinstalled on some new Solaris-based hosts, so you may have to | |
3026 | back it out. | |
3027 | ||
3028 | @item | |
3029 | Copy the original, unpatched Solaris 7 | |
3030 | @command{/usr/ccs/bin/as} into | |
3031 | @command{/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/3.0/as}, | |
3032 | adjusting the latter name to fit your local conventions and software | |
3033 | version numbers. | |
3034 | ||
3035 | @item | |
3036 | Install Sun patch 106950-03 (1999-05-25) or later. Nobody with | |
3037 | both 107058-01 and 106950-03 installed has reported the bug with GCC | |
3038 | and Sun's dynamic linker. This last course of action is riskiest, | |
3039 | for two reasons. First, you must install 106950 on all hosts that | |
3040 | run code generated by GCC; it doesn't suffice to install it only on | |
3041 | the hosts that run GCC itself. Second, Sun says that 106950-03 is | |
3042 | only a partial fix for bug 4210064, but Sun doesn't know whether the | |
3043 | partial fix is adequate for GCC@. Revision -08 or later should fix | |
3044 | the bug, but (as of 1999-10-06) it is still being tested. | |
3045 | @end itemize | |
3046 | ||
3047 | ||
3048 | @html | |
3049 | <p> | |
3050 | <hr> | |
3051 | <!-- ripped from the same FAQ that I answered --> | |
3052 | @end html | |
3053 | @heading @anchor{*-sun-solaris2.8}*-sun-solaris2.8 | |
3054 | ||
3055 | Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or | |
3056 | newer: @command{g++} will complain that types are missing. These headers assume | |
3057 | that omitting the type means @code{int}; this assumption worked for C89 but | |
3058 | is wrong for C++, and is now wrong for C99 also. | |
3059 | ||
3060 | @command{g++} accepts such (illegal) constructs with the option @option{-fpermissive}; it | |
3061 | will assume that any missing type is @code{int} (as defined by C89). | |
3062 | ||
3063 | For Solaris 8, this is fixed by revision 24 or later of patch 108652 | |
3064 | (for SPARCs) or 108653 (for Intels). | |
3065 | ||
3066 | Solaris 8's linker fails to link some @samp{libjava} programs if | |
3067 | previously-installed GCC java libraries already exist in the configured | |
3068 | prefix. For this reason, @samp{libgcj} is disabled by default on Solaris 8. | |
3069 | If you use GNU ld, or if you don't have a previously-installed @samp{libgcj} in | |
3070 | the same prefix, use @option{--enable-libgcj} to build and install the | |
3071 | Java libraries. | |
3072 | ||
3073 | @html | |
3074 | <p> | |
3075 | <hr> | |
3076 | @end html | |
3077 | @heading @anchor{sparc-sun-sunos*}sparc-sun-sunos* | |
3078 | ||
3079 | A bug in the SunOS 4 linker will cause it to crash when linking | |
3080 | @option{-fPIC} compiled objects (and will therefore not allow you to build | |
3081 | shared libraries). | |
3082 | ||
3083 | To fix this problem you can either use the most recent version of | |
3084 | binutils or get the latest SunOS 4 linker patch (patch ID 100170-10) | |
3085 | from Sun's patch site. | |
3086 | ||
3087 | ||
3088 | @html | |
3089 | </p> | |
3090 | <hr> | |
3091 | @end html | |
3092 | @heading @anchor{sparc-unknown-linux-gnulibc1}sparc-unknown-linux-gnulibc1 | |
3093 | ||
3094 | It has been reported that you might need | |
3095 | @uref{ftp://ftp.yggdrasil.com/private/hjl,,binutils 2.8.1.0.23} | |
3096 | for this platform, too. | |
3097 | ||
3098 | ||
3099 | @html | |
3100 | </p> | |
3101 | <hr> | |
3102 | @end html | |
3103 | @heading @anchor{sparc64-*-*}sparc64-*-* | |
3104 | ||
3105 | GCC version 2.95 is not able to compile code correctly for | |
3106 | @code{sparc64} targets. Users of the Linux kernel, at least, | |
3107 | can use the @code{sparc32} program to start up a new shell | |
3108 | invocation with an environment that causes @command{configure} to | |
3109 | recognize (via @samp{uname -a}) the system as @samp{sparc-*-*} instead. | |
3110 | ||
3111 | ||
3112 | @html | |
3113 | </p> | |
3114 | <hr> | |
3115 | @end html | |
3116 | @heading @anchor{#*-*-sysv*}*-*-sysv* | |
3117 | On System V release 3, you may get this error message | |
3118 | while linking: | |
3119 | ||
3120 | @smallexample | |
3121 | ld fatal: failed to write symbol name @var{something} | |
3122 | in strings table for file @var{whatever} | |
3123 | @end smallexample | |
3124 | ||
3125 | This probably indicates that the disk is full or your ulimit won't allow | |
3126 | the file to be as large as it needs to be. | |
3127 | ||
3128 | This problem can also result because the kernel parameter @code{MAXUMEM} | |
3129 | is too small. If so, you must regenerate the kernel and make the value | |
3130 | much larger. The default value is reported to be 1024; a value of 32768 | |
3131 | is said to work. Smaller values may also work. | |
3132 | ||
3133 | On System V, if you get an error like this, | |
3134 | ||
3135 | @example | |
3136 | /usr/local/lib/bison.simple: In function `yyparse': | |
3137 | /usr/local/lib/bison.simple:625: virtual memory exhausted | |
3138 | @end example | |
3139 | ||
3140 | @noindent | |
3141 | that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}. | |
3142 | ||
3143 | On a System V release 4 system, make sure @file{/usr/bin} precedes | |
3144 | @file{/usr/ucb} in @code{PATH}. The @code{cc} command in | |
3145 | @file{/usr/ucb} uses libraries which have bugs. | |
3146 | ||
3147 | @html | |
3148 | </p> | |
3149 | <hr> | |
3150 | @end html | |
3151 | @heading @anchor{vax-dec-ultrix}vax-dec-ultrix | |
3152 | Don't try compiling with Vax C (@code{vcc}). It produces incorrect code | |
3153 | in some cases (for example, when @code{alloca} is used). | |
3154 | ||
3155 | @html | |
3156 | </p> | |
3157 | <hr> | |
3158 | @end html | |
3159 | @heading @anchor{we32k-*-*}we32k-*-* | |
3160 | These computers are also known as the 3b2, 3b5, 3b20 and other similar | |
3161 | names. (However, the 3b1 is actually a 68000.) | |
3162 | ||
3163 | Don't use @option{-g} when compiling with the system's compiler. The | |
3164 | system's linker seems to be unable to handle such a large program with | |
3165 | debugging information. | |
3166 | ||
3167 | The system's compiler runs out of capacity when compiling @file{stmt.c} | |
3168 | in GCC@. You can work around this by building @file{cpp} in GCC | |
3169 | first, then use that instead of the system's preprocessor with the | |
3170 | system's C compiler to compile @file{stmt.c}. Here is how: | |
3171 | ||
3172 | @smallexample | |
3173 | mv /lib/cpp /lib/cpp.att | |
3174 | cp cpp /lib/cpp.gnu | |
3175 | echo '/lib/cpp.gnu -traditional $@{1+"$@@"@}' > /lib/cpp | |
3176 | chmod +x /lib/cpp | |
3177 | @end smallexample | |
3178 | ||
3179 | The system's compiler produces bad code for some of the GCC | |
3180 | optimization files. So you must build the stage 2 compiler without | |
3181 | optimization. Then build a stage 3 compiler with optimization. | |
3182 | That executable should work. Here are the necessary commands: | |
3183 | ||
3184 | @smallexample | |
3185 | make LANGUAGES=c CC=stage1/xgcc CFLAGS="-Bstage1/ -g" | |
3186 | make stage2 | |
3187 | make CC=stage2/xgcc CFLAGS="-Bstage2/ -g -O" | |
3188 | @end smallexample | |
3189 | ||
3190 | You may need to raise the ULIMIT setting to build a C++ compiler, | |
3191 | as the file @file{cc1plus} is larger than one megabyte. | |
3192 | ||
3193 | @html | |
3194 | </p> | |
3195 | <hr> | |
3196 | @end html | |
3197 | @heading @anchor{windows}Microsoft Windows (32 bit) | |
3198 | ||
3199 | A port of GCC 2.95.x is included with the | |
3200 | @uref{http://www.cygwin.com/,,Cygwin environment}. | |
3201 | ||
3202 | Current (as of early 2001) snapshots of GCC will build under Cygwin | |
3203 | without modification. | |
3204 | ||
3205 | @html | |
3206 | </p> | |
3207 | <hr> | |
3208 | @end html | |
3209 | @heading @anchor{os2}OS/2 | |
3210 | ||
3211 | GCC does not currently support OS/2. However, Andrew Zabolotny has been | |
3212 | working on a generic OS/2 port with pgcc. The current code code can be found | |
3213 | at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}. | |
3214 | ||
3215 | An older copy of GCC 2.8.1 is included with the EMX tools available at | |
3216 | @uref{ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/,, | |
3217 | ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/}. | |
3218 | ||
3219 | @html | |
3220 | </p> | |
3221 | <hr> | |
3222 | @end html | |
3223 | @heading @anchor{older}Older systems | |
3224 | ||
3225 | GCC contains support files for many older (1980s and early | |
3226 | 1990s) Unix variants. For the most part, support for these systems | |
3227 | has not been deliberately removed, but it has not been maintained for | |
3228 | several years and may suffer from bitrot. Support from some systems | |
3229 | has been removed from GCC 3: fx80, ns32-ns-genix, pyramid, tahoe, | |
3230 | gmicro, spur; most of these targets had not been updated since GCC | |
3231 | version 1. | |
3232 | ||
3233 | Support for older systems as targets for cross-compilation is less | |
3234 | problematic than support for them as hosts for GCC; if an enthusiast | |
3235 | wishes to make such a target work again (including resurrecting any | |
3236 | of the targets that never worked with GCC 2, starting from the last | |
3237 | CVS version before they were removed), patches | |
3238 | @uref{../contribute.html,,following the usual requirements} | |
3239 | would be likely to be accepted, since they should not affect the | |
3240 | support for more modern targets. | |
3241 | ||
3242 | Support for old systems as hosts for GCC can cause problems if the | |
3243 | workarounds for compiler, library and operating system bugs affect the | |
3244 | cleanliness or maintainability of the rest of GCC@. In some cases, to | |
3245 | bring GCC up on such a system, if still possible with current GCC, may | |
3246 | require first installing an old version of GCC which did work on that | |
3247 | system, and using it to compile a more recent GCC, to avoid bugs in | |
3248 | the vendor compiler. Old releases of GCC 1 and GCC 2 are available in | |
3249 | the @file{old-releases} directory on the | |
3250 | @uref{../mirrors.html,,GCC mirror sites}. Header bugs may generally | |
3251 | be avoided using @command{fixincludes}, but bugs or deficiencies in | |
3252 | libraries and the operating system may still cause problems. | |
3253 | ||
3254 | For some systems, old versions of GNU binutils may also be useful, | |
3255 | and are available from @file{pub/binutils/old-releases} on | |
3256 | @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}. | |
3257 | ||
3258 | Some of the information on specific systems above relates to | |
3259 | such older systems, but much of the information | |
3260 | about GCC on such systems (which may no longer be applicable to | |
3261 | current GCC) is to be found in the GCC texinfo manual. | |
3262 | ||
3263 | @html | |
3264 | </p> | |
3265 | <hr> | |
3266 | @end html | |
3267 | @heading @anchor{elf_targets}all ELF targets (SVR4, Solaris, etc.) | |
3268 | ||
3269 | C++ support is significantly better on ELF targets if you use the | |
3270 | @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of | |
3271 | inlines, vtables and template instantiations will be discarded | |
3272 | automatically. | |
3273 | ||
3274 | ||
3275 | @html | |
3276 | </p> | |
3277 | <hr> | |
3278 | <p> | |
3279 | @end html | |
3280 | @ifhtml | |
3281 | @uref{./index.html,,Return to the GCC Installation page} | |
3282 | @end ifhtml | |
3283 | @end ifset | |
3284 | ||
3285 | @c *************************************************************************** | |
3286 | @c Part 6 The End of the Document | |
3287 | @ifinfo | |
3288 | @comment node-name, next, previous, up | |
3289 | @node Concept Index, , Specific, Top | |
3290 | @end ifinfo | |
3291 | ||
3292 | @ifinfo | |
3293 | @unnumbered Concept Index | |
3294 | ||
3295 | @printindex cp | |
3296 | ||
3297 | @contents | |
3298 | @end ifinfo | |
3299 | @bye |