From: law@sourceware.cygnus.com
To: gcc@gcc.gnu.org
Subject: gcc-ss-20000731 is now available
Date: Mon, 31 Jul 2000 16:52:00 -0000 [thread overview]
Message-ID: <20000731235207.25046.qmail@sourceware.cygnus.com> (raw)
egcs-ss-20000731 is now available on
egcs.cygnus.com:/pub/egcs/snapshots/2000-07-31
(and on various mirrors, see the egcs home page for mirror sites).
You'll find:
egcs-20000731.tar.gz The full egcs snapshot, including all
languages runtime libraries.
egcs-core-20000731.tar.gz Just the C front end and core compiler.
egcs-g++-20000731.tar.gz The g++ language and runtime.
egcs-g77-20000731.tar.gz The g77 language and runtime.
egcs-objc-20000731.tar.gz The Objective-C font end and runtime.
egcs-java-20000731.tar.gz The Java font end.
egcs-chill-20000731.tar.gz The Chill font 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 20000724 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 egcs 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.
reply other threads:[~2000-07-31 16:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20000731235207.25046.qmail@sourceware.cygnus.com \
--to=law@sourceware.cygnus.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).