prerequisites.html revision 1.8
1<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 2<html> 3<!-- Copyright (C) 1988-2017 Free Software Foundation, Inc. 4 5Permission is granted to copy, distribute and/or modify this document 6under the terms of the GNU Free Documentation License, Version 1.3 or 7any later version published by the Free Software Foundation; with no 8Invariant Sections, the Front-Cover texts being (a) (see below), and 9with the Back-Cover Texts being (b) (see below). A copy of the 10license is included in the section entitled "GNU 11Free Documentation License". 12 13(a) The FSF's Front-Cover Text is: 14 15A GNU Manual 16 17(b) The FSF's Back-Cover Text is: 18 19You have freedom to copy and modify this GNU Manual, like GNU 20 software. Copies published by the Free Software Foundation raise 21 funds for GNU development. --> 22<!-- Created by GNU Texinfo 6.4, http://www.gnu.org/software/texinfo/ --> 23<head> 24<title>Installing GCC</title> 25 26<meta name="description" content="Installing GCC"> 27<meta name="keywords" content="Installing GCC"> 28<meta name="resource-type" content="document"> 29<meta name="distribution" content="global"> 30<meta name="Generator" content="makeinfo"> 31<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> 32<style type="text/css"> 33<!-- 34a.summary-letter {text-decoration: none} 35blockquote.indentedblock {margin-right: 0em} 36blockquote.smallindentedblock {margin-right: 0em; font-size: smaller} 37blockquote.smallquotation {font-size: smaller} 38div.display {margin-left: 3.2em} 39div.example {margin-left: 3.2em} 40div.lisp {margin-left: 3.2em} 41div.smalldisplay {margin-left: 3.2em} 42div.smallexample {margin-left: 3.2em} 43div.smalllisp {margin-left: 3.2em} 44kbd {font-style: oblique} 45pre.display {font-family: inherit} 46pre.format {font-family: inherit} 47pre.menu-comment {font-family: serif} 48pre.menu-preformatted {font-family: serif} 49pre.smalldisplay {font-family: inherit; font-size: smaller} 50pre.smallexample {font-size: smaller} 51pre.smallformat {font-family: inherit; font-size: smaller} 52pre.smalllisp {font-size: smaller} 53span.nolinebreak {white-space: nowrap} 54span.roman {font-family: initial; font-weight: normal} 55span.sansserif {font-family: sans-serif; font-weight: normal} 56ul.no-bullet {list-style: none} 57--> 58</style> 59 60 61</head> 62 63<body lang="en"> 64<h1 class="settitle" align="center">Installing GCC</h1> 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82<a name="index-Prerequisites"></a> 83 84<p>GCC requires that various tools and packages be available for use in the 85build procedure. Modifying GCC sources requires additional tools 86described below. 87</p> 88<a name="Tools_002fpackages-necessary-for-building-GCC"></a> 89<h3 class="heading">Tools/packages necessary for building GCC</h3> 90<dl compact="compact"> 91<dt>ISO C++98 compiler</dt> 92<dd><p>Necessary to bootstrap GCC, although versions of GCC prior 93to 4.8 also allow bootstrapping with a ISO C89 compiler and versions 94of GCC prior to 3.4 also allow bootstrapping with a traditional 95(K&R) C compiler. 96</p> 97<p>To build all languages in a cross-compiler or other configuration where 983-stage bootstrap is not performed, you need to start with an existing 99GCC binary (version 3.4 or later) because source code for language 100frontends other than C might use GCC extensions. 101</p> 102<p>Note that to bootstrap GCC with versions of GCC earlier than 3.4, you 103may need to use <samp>--disable-stage1-checking</samp>, though 104bootstrapping the compiler with such earlier compilers is strongly 105discouraged. 106</p> 107</dd> 108<dt>C standard library and headers</dt> 109<dd> 110<p>In order to build GCC, the C standard library and headers must be present 111for all target variants for which target libraries will be built (and not 112only the variant of the host C++ compiler). 113</p> 114<p>This affects the popular ‘<samp>x86_64-unknown-linux-gnu</samp>’ platform (among 115other multilib targets), for which 64-bit (‘<samp>x86_64</samp>’) and 32-bit 116(‘<samp>i386</samp>’) libc headers are usually packaged separately. If you do a 117build of a native compiler on ‘<samp>x86_64-unknown-linux-gnu</samp>’, make sure you 118either have the 32-bit libc developer package properly installed (the exact 119name of the package depends on your distro) or you must build GCC as a 12064-bit only compiler by configuring with the option 121<samp>--disable-multilib</samp>. Otherwise, you may encounter an error such as 122‘<samp>fatal error: gnu/stubs-32.h: No such file</samp>’ 123</p> 124</dd> 125<dt>GNAT</dt> 126<dd> 127<p>In order to build the Ada compiler (GNAT) you must already have GNAT 128installed because portions of the Ada frontend are written in Ada (with 129GNAT extensions.) Refer to the Ada installation instructions for more 130specific information. 131</p> 132</dd> 133<dt>A “working” POSIX compatible shell, or GNU bash</dt> 134<dd> 135<p>Necessary when running <code>configure</code> because some 136<code>/bin/sh</code> shells have bugs and may crash when configuring the 137target libraries. In other cases, <code>/bin/sh</code> or <code>ksh</code> 138have disastrous corner-case performance problems. This 139can cause target <code>configure</code> runs to literally take days to 140complete in some cases. 141</p> 142<p>So on some platforms <code>/bin/ksh</code> is sufficient, on others it 143isn’t. See the host/target specific instructions for your platform, or 144use <code>bash</code> to be sure. Then set <code>CONFIG_SHELL</code> in your 145environment to your “good” shell prior to running 146<code>configure</code>/<code>make</code>. 147</p> 148<p><code>zsh</code> is not a fully compliant POSIX shell and will not 149work when configuring GCC. 150</p> 151</dd> 152<dt>A POSIX or SVR4 awk</dt> 153<dd> 154<p>Necessary for creating some of the generated source files for GCC. 155If in doubt, use a recent GNU awk version, as some of the older ones 156are broken. GNU awk version 3.1.5 is known to work. 157</p> 158</dd> 159<dt>GNU binutils</dt> 160<dd> 161<p>Necessary in some circumstances, optional in others. See the 162host/target specific instructions for your platform for the exact 163requirements. 164</p> 165</dd> 166<dt>gzip version 1.2.4 (or later) or</dt> 167<dt>bzip2 version 1.0.2 (or later)</dt> 168<dd> 169<p>Necessary to uncompress GCC <code>tar</code> files when source code is 170obtained via FTP mirror sites. 171</p> 172</dd> 173<dt>GNU make version 3.80 (or later)</dt> 174<dd> 175<p>You must have GNU make installed to build GCC. 176</p> 177</dd> 178<dt>GNU tar version 1.14 (or later)</dt> 179<dd> 180<p>Necessary (only on some platforms) to untar the source code. Many 181systems’ <code>tar</code> programs will also work, only try GNU 182<code>tar</code> if you have problems. 183</p> 184</dd> 185<dt>Perl version 5.6.1 (or later)</dt> 186<dd> 187<p>Necessary when targeting Darwin, building ‘<samp>libstdc++</samp>’, 188and not using <samp>--disable-symvers</samp>. 189Necessary when targeting Solaris 2 with Sun <code>ld</code> and not using 190<samp>--disable-symvers</samp>. The bundled <code>perl</code> in Solaris 8 191and up works. 192</p> 193<p>Necessary when regenerating <samp>Makefile</samp> dependencies in libiberty. 194Necessary when regenerating <samp>libiberty/functions.texi</samp>. 195Necessary when generating manpages from Texinfo manuals. 196Used by various scripts to generate some files included in SVN (mainly 197Unicode-related and rarely changing) from source tables. 198</p> 199</dd> 200<dt><code>jar</code>, or InfoZIP (<code>zip</code> and <code>unzip</code>)</dt> 201<dd> 202<p>Necessary to build libgcj, the GCJ runtime. 203</p> 204</dd> 205</dl> 206 207<p>Several support libraries are necessary to build GCC, some are required, 208others optional. While any sufficiently new version of required tools 209usually work, library requirements are generally stricter. Newer 210versions may work in some cases, but it’s safer to use the exact 211versions documented. We appreciate bug reports about problems with 212newer versions, though. If your OS vendor provides packages for the 213support libraries then using those packages may be the simplest way to 214install the libraries. 215</p> 216<dl compact="compact"> 217<dt>GNU Multiple Precision Library (GMP) version 4.3.2 (or later)</dt> 218<dd> 219<p>Necessary to build GCC. If a GMP source distribution is found in a 220subdirectory of your GCC sources named <samp>gmp</samp>, it will be built 221together with GCC. Alternatively, if GMP is already installed but it 222is not in your library search path, you will have to configure with the 223<samp>--with-gmp</samp> configure option. See also <samp>--with-gmp-lib</samp> 224and <samp>--with-gmp-include</samp>. 225</p> 226</dd> 227<dt>MPFR Library version 2.4.2 (or later)</dt> 228<dd> 229<p>Necessary to build GCC. It can be downloaded from 230<a href="http://www.mpfr.org/">http://www.mpfr.org/</a>. If an MPFR source distribution is found 231in a subdirectory of your GCC sources named <samp>mpfr</samp>, it will be 232built together with GCC. Alternatively, if MPFR is already installed 233but it is not in your default library search path, the 234<samp>--with-mpfr</samp> configure option should be used. See also 235<samp>--with-mpfr-lib</samp> and <samp>--with-mpfr-include</samp>. 236</p> 237</dd> 238<dt>MPC Library version 0.8.1 (or later)</dt> 239<dd> 240<p>Necessary to build GCC. It can be downloaded from 241<a href="http://www.multiprecision.org/">http://www.multiprecision.org/</a>. If an MPC source distribution 242is found in a subdirectory of your GCC sources named <samp>mpc</samp>, it 243will be built together with GCC. Alternatively, if MPC is already 244installed but it is not in your default library search path, the 245<samp>--with-mpc</samp> configure option should be used. See also 246<samp>--with-mpc-lib</samp> and <samp>--with-mpc-include</samp>. 247</p> 248</dd> 249<dt>isl Library version 0.16, 0.15, or 0.14.</dt> 250<dd> 251<p>Necessary to build GCC with the Graphite loop optimizations. 252It can be downloaded from <a href="ftp://gcc.gnu.org/pub/gcc/infrastructure/">ftp://gcc.gnu.org/pub/gcc/infrastructure/</a>. 253If an isl source distribution is found 254in a subdirectory of your GCC sources named <samp>isl</samp>, it will be 255built together with GCC. Alternatively, the <samp>--with-isl</samp> configure 256option should be used if isl is not installed in your default library 257search path. 258</p> 259</dd> 260</dl> 261 262<a name="Tools_002fpackages-necessary-for-modifying-GCC"></a> 263<h3 class="heading">Tools/packages necessary for modifying GCC</h3> 264<dl compact="compact"> 265<dt>autoconf version 2.64</dt> 266<dt>GNU m4 version 1.4.6 (or later)</dt> 267<dd> 268<p>Necessary when modifying <samp>configure.ac</samp>, <samp>aclocal.m4</samp>, etc. 269to regenerate <samp>configure</samp> and <samp>config.in</samp> files. 270</p> 271</dd> 272<dt>automake version 1.11.6</dt> 273<dd> 274<p>Necessary when modifying a <samp>Makefile.am</samp> file to regenerate its 275associated <samp>Makefile.in</samp>. 276</p> 277<p>Much of GCC does not use automake, so directly edit the <samp>Makefile.in</samp> 278file. Specifically this applies to the <samp>gcc</samp>, <samp>intl</samp>, 279<samp>libcpp</samp>, <samp>libiberty</samp>, <samp>libobjc</samp> directories as well 280as any of their subdirectories. 281</p> 282<p>For directories that use automake, GCC requires the latest release in 283the 1.11 series, which is currently 1.11.6. When regenerating a directory 284to a newer version, please update all the directories using an older 1.11 285to the latest released version. 286</p> 287</dd> 288<dt>gettext version 0.14.5 (or later)</dt> 289<dd> 290<p>Needed to regenerate <samp>gcc.pot</samp>. 291</p> 292</dd> 293<dt>gperf version 2.7.2 (or later)</dt> 294<dd> 295<p>Necessary when modifying <code>gperf</code> input files, e.g. 296<samp>gcc/cp/cfns.gperf</samp> to regenerate its associated header file, e.g. 297<samp>gcc/cp/cfns.h</samp>. 298</p> 299</dd> 300<dt>DejaGnu 1.4.4</dt> 301<dt>Expect</dt> 302<dt>Tcl</dt> 303<dd> 304<p>Necessary to run the GCC testsuite; see the section on testing for 305details. Tcl 8.6 has a known regression in RE pattern handling that 306make parts of the testsuite fail. See 307<a href="http://core.tcl.tk/tcl/tktview/267b7e2334ee2e9de34c4b00d6e72e2f1997085f">http://core.tcl.tk/tcl/tktview/267b7e2334ee2e9de34c4b00d6e72e2f1997085f</a> 308for more information. This bug has been fixed in 8.6.1. 309</p> 310</dd> 311<dt>autogen version 5.5.4 (or later) and</dt> 312<dt>guile version 1.4.1 (or later)</dt> 313<dd> 314<p>Necessary to regenerate <samp>fixinc/fixincl.x</samp> from 315<samp>fixinc/inclhack.def</samp> and <samp>fixinc/*.tpl</samp>. 316</p> 317<p>Necessary to run ‘<samp>make check</samp>’ for <samp>fixinc</samp>. 318</p> 319<p>Necessary to regenerate the top level <samp>Makefile.in</samp> file from 320<samp>Makefile.tpl</samp> and <samp>Makefile.def</samp>. 321</p> 322</dd> 323<dt>Flex version 2.5.4 (or later)</dt> 324<dd> 325<p>Necessary when modifying <samp>*.l</samp> files. 326</p> 327<p>Necessary to build GCC during development because the generated output 328files are not included in the SVN repository. They are included in 329releases. 330</p> 331</dd> 332<dt>Texinfo version 4.7 (or later)</dt> 333<dd> 334<p>Necessary for running <code>makeinfo</code> when modifying <samp>*.texi</samp> 335files to test your changes. 336</p> 337<p>Necessary for running <code>make dvi</code> or <code>make pdf</code> to 338create printable documentation in DVI or PDF format. Texinfo version 3394.8 or later is required for <code>make pdf</code>. 340</p> 341<p>Necessary to build GCC documentation during development because the 342generated output files are not included in the SVN repository. They are 343included in releases. 344</p> 345</dd> 346<dt>TeX (any working version)</dt> 347<dd> 348<p>Necessary for running <code>texi2dvi</code> and <code>texi2pdf</code>, which 349are used when running <code>make dvi</code> or <code>make pdf</code> to create 350DVI or PDF files, respectively. 351</p> 352</dd> 353<dt>Sphinx version 1.0 (or later)</dt> 354<dd> 355<p>Necessary to regenerate <samp>jit/docs/_build/texinfo</samp> from the <samp>.rst</samp> 356files in the directories below <samp>jit/docs</samp>. 357</p> 358</dd> 359<dt>SVN (any version)</dt> 360<dt>SSH (any version)</dt> 361<dd> 362<p>Necessary to access the SVN repository. Public releases and weekly 363snapshots of the development sources are also available via FTP. 364</p> 365</dd> 366<dt>GNU diffutils version 2.7 (or later)</dt> 367<dd> 368<p>Useful when submitting patches for the GCC source code. 369</p> 370</dd> 371<dt>patch version 2.5.4 (or later)</dt> 372<dd> 373<p>Necessary when applying patches, created with <code>diff</code>, to one’s 374own sources. 375</p> 376</dd> 377<dt>ecj1</dt> 378<dt>gjavah</dt> 379<dd> 380<p>If you wish to modify <samp>.java</samp> files in libjava, you will need to 381configure with <samp>--enable-java-maintainer-mode</samp>, and you will need 382to have executables named <code>ecj1</code> and <code>gjavah</code> in your path. 383The <code>ecj1</code> executable should run the Eclipse Java compiler via 384the GCC-specific entry point. You can download a suitable jar from 385<a href="ftp://sourceware.org/pub/java/">ftp://sourceware.org/pub/java/</a>, or by running the script 386<code>contrib/download_ecj</code>. 387</p> 388</dd> 389<dt>antlr.jar version 2.7.1 (or later)</dt> 390<dt>antlr binary</dt> 391<dd> 392<p>If you wish to build the <code>gjdoc</code> binary in libjava, you will 393need to have an <samp>antlr.jar</samp> library available. The library is 394searched for in system locations but can be specified with 395<samp>--with-antlr-jar=</samp> instead. When configuring with 396<samp>--enable-java-maintainer-mode</samp>, you will need to have one of 397the executables named <code>cantlr</code>, <code>runantlr</code> or 398<code>antlr</code> in your path. 399</p> 400</dd> 401</dl> 402 403<hr /> 404<p> 405<p><a href="./index.html">Return to the GCC Installation page</a> 406</p> 407 408 409 410 411 412 413 414 415 416 417 418 419 420</body> 421</html> 422