| 1 | <html>
|
|---|
| 2 |
|
|---|
| 3 | <head>
|
|---|
| 4 | <title>GCC Snapshots</title>
|
|---|
| 5 | </head>
|
|---|
| 6 |
|
|---|
| 7 | <body>
|
|---|
| 8 | <h1>GCC Snapshots</h1>
|
|---|
| 9 |
|
|---|
| 10 | <hr />
|
|---|
| 11 |
|
|---|
| 12 | <p>The <a href ="http://gcc.gnu.org/">GCC Project</a> makes
|
|---|
| 13 | periodic snapshots of the GCC source tree available to the public
|
|---|
| 14 | for testing purposes.</p>
|
|---|
| 15 |
|
|---|
| 16 | <p>If you are planning to download and use one of our snapshots, then
|
|---|
| 17 | we highly recommend you join the GCC developers list. Details for
|
|---|
| 18 | how to sign up can be found on the GCC project home page.</p>
|
|---|
| 19 |
|
|---|
| 20 |
|
|---|
| 21 | <blockquote>
|
|---|
| 22 | <p> <a href="@LONG_DATE@/gcc-@DATE@.tar.gz">
|
|---|
| 23 | gcc</a> @TEXT_DATE@ snapshot, includes all languages.
|
|---|
| 24 |
|
|---|
| 25 | <p> <a href="@LONG_DATE@/gcc-@LAST_DATE@-@DATE@.diff.gz">
|
|---|
| 26 | gcc-@LAST_DATE@-@DATE@</a> patch file to bring gcc-@LAST_DATE@ up to
|
|---|
| 27 | gcc-@DATE@.
|
|---|
| 28 |
|
|---|
| 29 | <p> <a href="@LONG_DATE@/gcc-core-@DATE@.tar.gz">
|
|---|
| 30 | gcc-core</a> @TEXT_DATE@ snapshot, includes just the C front
|
|---|
| 31 | end and core compiler.
|
|---|
| 32 |
|
|---|
| 33 | <p> <a href="@LONG_DATE@/gcc-core-@LAST_DATE@-@DATE@.diff.gz">
|
|---|
| 34 | gcc-core-@LAST_DATE@-@DATE@</a> patch file to bring gcc-core-@LAST_DATE@
|
|---|
| 35 | up to gcc-core-@DATE@.
|
|---|
| 36 |
|
|---|
| 37 | <p> <a href="@LONG_DATE@/gcc-g++-@DATE@.tar.gz">
|
|---|
| 38 | gcc-g++</a> @TEXT_DATE@ snapshot, includes just the G++ front
|
|---|
| 39 | end and runtime.
|
|---|
| 40 |
|
|---|
| 41 | <p> <a href="@LONG_DATE@/gcc-g++-@LAST_DATE@-@DATE@.diff.gz">
|
|---|
| 42 | gcc-g++-@LAST_DATE@-@DATE@</a> patch file to bring gcc-g++-@LAST_DATE@
|
|---|
| 43 | up to gcc-g++-@DATE@.
|
|---|
| 44 |
|
|---|
| 45 | <p> <a href="@LONG_DATE@/gcc-g77-@DATE@.tar.gz">
|
|---|
| 46 | gcc-g77</a> @TEXT_DATE@ snapshot, includes just the G77 front
|
|---|
| 47 | end and runtime.
|
|---|
| 48 |
|
|---|
| 49 | <p> <a href="@LONG_DATE@/gcc-g77-@LAST_DATE@-@DATE@.diff.gz">
|
|---|
| 50 | gcc-g77-@LAST_DATE@-@DATE@</a> patch file to bring gcc-g77-@LAST_DATE@
|
|---|
| 51 | up to gcc-g77-@DATE@.
|
|---|
| 52 |
|
|---|
| 53 | <p> <a href="@LONG_DATE@/gcc-java-@DATE@.tar.gz">
|
|---|
| 54 | gcc-java</a> @TEXT_DATE@ snapshot, includes just the Java
|
|---|
| 55 | front end.
|
|---|
| 56 |
|
|---|
| 57 | <p> <a href="@LONG_DATE@/gcc-java-@LAST_DATE@-@DATE@.diff.gz">
|
|---|
| 58 | gcc-java-@LAST_DATE@-@DATE@</a> patch file to bring gcc-java-@LAST_DATE@
|
|---|
| 59 | up to gcc-java-@DATE@.
|
|---|
| 60 |
|
|---|
| 61 | <p> <a href="@LONG_DATE@/gcc-objc-@DATE@.tar.gz">
|
|---|
| 62 | gcc-objc</a> @TEXT_DATE@ snapshot, includes just the Objective-C
|
|---|
| 63 | front end and runtime.
|
|---|
| 64 |
|
|---|
| 65 | <p> <a href="@LONG_DATE@/gcc-objc-@LAST_DATE@-@DATE@.diff.gz">
|
|---|
| 66 | gcc-objc-@LAST_DATE@-@DATE@</a> patch file to bring gcc-objc-@LAST_DATE@
|
|---|
| 67 | up to gcc-objc-@DATE@.
|
|---|
| 68 |
|
|---|
| 69 | <p> <a href="@LONG_DATE@/gcc-ada-@DATE@.tar.gz">
|
|---|
| 70 | gcc-ada</a> @TEXT_DATE@ snapshot, includes just the Ada
|
|---|
| 71 | front end and runtime.
|
|---|
| 72 |
|
|---|
| 73 | <p> <a href="@LONG_DATE@/gcc-ada-@LAST_DATE@-@DATE@.diff.gz">
|
|---|
| 74 | gcc-ada-@LAST_DATE@-@DATE@</a> patch file to bring gcc-ada-@LAST_DATE@
|
|---|
| 75 | up to gcc-ada-@DATE@.
|
|---|
| 76 |
|
|---|
| 77 | </blockquote>
|
|---|
| 78 |
|
|---|
| 79 | <p>If you are using an x86 GNU/Linux system that uses RPMs to handle
|
|---|
| 80 | installation, you may find the daily RPM snapshots at:
|
|---|
| 81 | <a href="http://www.codesourcery.com/gcc-snapshots.html">
|
|---|
| 82 | http://www.codesourcery.com/gcc-snapshots.html </a>
|
|---|
| 83 | easier to install.</p>
|
|---|
| 84 |
|
|---|
| 85 | <p>Note at times you may find newer directories on the server with limited
|
|---|
| 86 | permissions. These represent snapshots that have not yet been verified
|
|---|
| 87 | as correct, or are known to be incorrect.</p>
|
|---|
| 88 |
|
|---|
| 89 | <p>When a particular snapshot is ready for public consumption the directory
|
|---|
| 90 | permissions are relaxed, the LATEST-IS- file is updated and a message is
|
|---|
| 91 | sent to the GCC list.</p>
|
|---|
| 92 |
|
|---|
| 93 | <p>Using a snapshot before it's officially made available is an unwise thing
|
|---|
| 94 | to do since it may become impossible to update to an official snapshot.</p>
|
|---|
| 95 |
|
|---|
| 96 | <p>Old snapshots can be found on the ftp server <a
|
|---|
| 97 | href="ftp://gcc.gnu.org/pub/gcc/snapshots/">ftp://gcc.gnu.org:/pub/gcc/snapshots</a>.</p>
|
|---|
| 98 |
|
|---|
| 99 | <hr />
|
|---|
| 100 |
|
|---|
| 101 | <address>
|
|---|
| 102 | <a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a>
|
|---|
| 103 | <a href="mailto:gcc-bugs@gcc.gnu.org">gcc-bugs@gcc.gnu.org</a>
|
|---|
| 104 |
|
|---|
| 105 | <p>Last modified @TEXT_DATE@</p>
|
|---|
| 106 | </address>
|
|---|
| 107 | </body>
|
|---|
| 108 |
|
|---|
| 109 | </html>
|
|---|
