| 1 | <html lang="en"><head>
|
|---|
| 2 | <title>Downloading GCC</title>
|
|---|
| 3 | <meta http-equiv="Content-Type" content="text/html">
|
|---|
| 4 | <meta name=description content="Downloading GCC">
|
|---|
| 5 | <meta name=generator content="makeinfo 4.0">
|
|---|
| 6 | <link href="http://texinfo.org/" rel=generator-home>
|
|---|
| 7 | </head><body>
|
|---|
| 8 |
|
|---|
| 9 | <p>G<p>CC is distributed via <a href="http://gcc.gnu.org/cvs.html">CVS</a> and FTP
|
|---|
| 10 | tarballs compressed with <code>gzip</code> or
|
|---|
| 11 | <code>bzip2</code>. It is possible to download a full distribution or specific
|
|---|
| 12 | components.
|
|---|
| 13 |
|
|---|
| 14 | <p>Please refer to our <a href="http://gcc.gnu.org/releases.html">releases web page</a>
|
|---|
| 15 | for information on how to obtain GCC.
|
|---|
| 16 |
|
|---|
| 17 | <p>The full distribution includes the C, C++, Objective-C, Fortran, Java,
|
|---|
| 18 | and Ada (in case of GCC 3.1 and later) compilers. The full distribution
|
|---|
| 19 | also includes runtime libraries for C++, Objective-C, Fortran, and Java.
|
|---|
| 20 | In GCC 3.0 and later versions, GNU compiler testsuites are also included
|
|---|
| 21 | in the full distribution.
|
|---|
| 22 |
|
|---|
| 23 | <p>If you choose to download specific components, you must download the core
|
|---|
| 24 | GCC distribution plus any language specific distributions you wish to
|
|---|
| 25 | use. The core distribution includes the C language front end as well as the
|
|---|
| 26 | shared components. Each language has a tarball which includes the language
|
|---|
| 27 | front end as well as the language runtime (when appropriate).
|
|---|
| 28 |
|
|---|
| 29 | <p>Unpack the core distribution as well as any language specific
|
|---|
| 30 | distributions in the same directory.
|
|---|
| 31 |
|
|---|
| 32 | <p>If you also intend to build binutils (either to upgrade an existing
|
|---|
| 33 | installation or for use in place of the corresponding tools of your
|
|---|
| 34 | OS), unpack the binutils distribution either in the same directory or
|
|---|
| 35 | a separate one. In the latter case, add symbolic links to any
|
|---|
| 36 | components of the binutils you intend to build alongside the compiler
|
|---|
| 37 | (<code>bfd</code>, <code>binutils</code>, <code>gas</code>, <code>gprof</code>, <code>ld</code>,
|
|---|
| 38 | <code>opcodes</code>, <small>...</small>) to the directory containing the GCC sources.
|
|---|
| 39 |
|
|---|
| 40 | <hr />
|
|---|
| 41 | <p>
|
|---|
| 42 | <a href="./index.html">Return to the GCC Installation page</a>
|
|---|
| 43 |
|
|---|
| 44 | </body></html>
|
|---|
| 45 |
|
|---|
