From: gccadmin@sources.redhat.com
To: gcc@gcc.gnu.org
Subject: gcc-ss-20011203 is now available
Date: Mon, 03 Dec 2001 19:13:00 -0000 [thread overview]
Message-ID: <20011204031351.20651.qmail@sources.redhat.com> (raw)
gcc-ss-20011203 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/2001-12-03
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the current development mainline
which is going to become GCC 3.1.
You'll find:
gcc-20011203.tar.gz The full gcc snapshot, including all
languages runtime libraries.
gcc-core-20011203.tar.gz Just the C front end and core compiler.
gcc-tests-20011203.tar.gz The GCC testsuite.
gcc-g++-20011203.tar.gz The g++ language and runtime.
gcc-g++-tests-20011203.tar.gz The testsuite for G++.
gcc-g77-20011203.tar.gz The g77 language and runtime.
gcc-g77-testsuite-20011203.tar.gz The testsuite for G77.
gcc-objc-20011203.tar.gz The Objective-C front end and runtime.
gcc-java-20011203.tar.gz The Java front end.
gcc-chill-20011203.tar.gz The Chill front end and runtime.
If you are using an x86 GNU/Linux system that uses RPMs to handle
installation, you may find the daily RPM snapshots at:
http://www.codesourcery.com/gcc-snapshots.html
easier to install.
Diffs from 20011126 are available.
Note at times you may find newer directories on the server with limited
permissions. These represent snapshots that have not yet been verified
as correct, or are known to be incorrect.
When a particular snapshot is ready for public consumption the directory
permissions are relaxed, the LATEST-IS- file is updated and a message is
sent to the gcc list.
Using a snapshot before it's officially made available is an unwise thing
to do since it may become impossible to update to an official snapshot.
The "gcc_latest_snapshot" tag has been moved. You can use
cvs update -rgcc_latest_snapshot to update your CVS tree to the latest
official snapshot.
next reply other threads:[~2001-12-04 3:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 19:13 gccadmin [this message]
2001-12-04 7:11 ` Andreas Schwab
2001-12-04 7:59 ` Joseph S. Myers
2001-12-04 12:16 ` guerby
2001-12-04 12:24 ` Joseph S. Myers
2001-12-04 12:30 ` Phil Edwards
2001-12-04 12:36 ` Joseph S. Myers
2001-12-04 12:46 ` Phil Edwards
2001-12-04 12:50 ` Assembly in Gcc Mark Cuss
2001-12-04 13:03 ` Graham Stott
2001-12-04 13:27 ` Mark Cuss
2001-12-04 19:00 ` Tim Prince
2001-12-11 11:14 ` Embedded Assembly and MMX in GCC Mark Cuss
2001-12-11 12:35 ` Alexandre Oliva
2001-12-11 13:00 ` Mark Cuss
2001-12-11 13:18 ` Alexandre Oliva
2001-12-11 14:09 ` Mark Cuss
2001-12-12 3:48 ` Andreas Schwab
2001-12-11 14:38 ` Craig Rodrigues
2001-12-04 19:54 ` gcc-ss-20011203 is now available Mark Mitchell
2001-12-04 8:17 Richard Kenner
2001-12-04 8:32 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011204031351.20651.qmail@sources.redhat.com \
--to=gccadmin@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).