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