Where is DOWNLOAD???

[Igor Tolstik]

 
Sorry! Where is DOWNLOAD???
 
GCC: Anonymous read-only CVS access 
In an ongoing effort to accelerate development of GCC and provide an open 
development environment, we are making our CVS source repository available 
read-only to the public at large.
That way you can pick up any version (including releases) of GCC that is in 
our repository or our web 
pages .
In addition, you can browse our CVS history online at

  subversions.gnu.org 
  using viewcvs, or 
  gcc.gnu.org using 
  cvsweb. 
Using the CVS repository
If you don't already have CVS, we recommend you pick up a recent copy from CVShome.org . (Note that CVS versions up to 
1.10.4 have "Y2K problems".)
Assuming you have CVS installed on your machine you can check out the GCC 
sources with the following sequence of commands:
Set CVSROOT in your environment to 
:pserver:anoncvs@subversions.gnu.org:/cvsroot/gcc . Alternately add 
-d :pserver:anoncvs@subversions.gnu.org:/cvsroot/gcc in the CVS 
commands below (place it immediately after cvs , before any other 
arguments).
Issue the command cvs login . You will be prompted for a 
password; reply with the empty string.
Issue the command 

  cvs -z 9 co gcc to check out the compiler 
sources, respectively 

  cvs -z 9 co wwwdocs
to check out our web pages.
Once you've got the repository checked out, cvs update will sync 
your local copy with the repository. See the CVS manual for additional 
information on how to use CVS.
Generated files
Our CVS source tree contains a number of files that are generated from other 
source files by build tools such as Bison, Autoconf, and Gperf. Bison is now 
required when using CVS to access our sources, but all other generated files are 
included in the source tree so that GCC can be built without these build tools. 
The CVS checkout and update operations do not insure that the timestamps of 
generated files are later than those of the files they are generated from. The 
script contrib/gcc_update updates the timestamps for all these 
generated files. See the comments in that script for instructions on running 
it.
GCC's build system (in particular Make) uses file timestamps to determine if 
a generated file needs to be updated by running a particular build tool. Because 
of this, GCC's build system may believe that a generated file needs regenerating 
even though its source has not changed, and require a particular build tool to 
rebuild that generated file. If the appropriate build tool is installed on your 
system, then this will not be a problem. If you do not intend to make changes to 
the source, you can avoid installing these build tools by running 
contrib/gcc_update .
There has been some discussion of removing these generated files from GCC's 
CVS source tree (there is no discussion of removing them from the released 
source tarballs). If that happens then building GCC from the CVS source tree 
would require installing the above mentioned build tools. Installing these build 
tools is not particularly difficult, but can be time consuming especially if you 
only occasionally install GCC on a particular system.
The build tools that GCC uses are all available from the GNU Project (see http://www.gnu.org ), are often already available 
on many systems, and can often be found already built for some systems. A 
partial list of these build tools is: Autoconf, Bison, Xgettext, Automake, and 
Gperf.


Conflicts when using cvs update
It is not uncommon to get CVS conflict messages for some generated files when 
updating your local sources from the CVS repository. Typically such conflicts 
occur with autoconf generated files.
As long as you haven't been making modifications to the generated files or 
the generator files, it is safe to delete the offending file, then run cvs 
update again to get a new copy.
CVS tags and checkouts
You can check out the latest version of the GCC 3.0 release branch with the 
following command:

  cvs -z 9 co -rgcc-3_0-branch gcc
By changing the -r argument above you can check out particular 
releases or snapshots or the latest snapshot. Other tags/branches you may want 
to check out include:

  gcc_latest_snapshot 
  gcc_ss_ yyyymmdd 
  gcc_3_2_release 
  gcc-3_2-branch 
  gcc_3_1_1_release 
  gcc_3_1_release 
  gcc-3_1-branch 
  gcc_3_0_4_release 
  gcc_3_0_3_release 
  gcc_3_0_2_release 
  gcc_3_0_1_release 
  gcc_3_0_release 
  gcc-3_0-branch 
  gcc-2_95_3 
  gcc-2_95_2-release 
  gcc-2_95_1-release 
  gcc-2_95-release 
  gcc-2_95-branch 
  egcs_1_1_2_release 
  egcs_1_1_1_release 
  egcs_1_1_release 
  egcs_1_1_branch 
  egcs_1_0_3_release 
  egcs_1_0_2_release 
  egcs_1_0_1_release 
  egcs_1_0_release 
  egcs_ss_ yyyymmdd For snapshots prior to 19990913 
  gnu-win32-b20-branch 
  dfa-branch. This branch contains the insn scheduler with an automaton 
  based pipeline hazard recognizer. 
  cfg-branch 

  ast-optimizer-branch 

  x86-64-branch. This branch contains a stable development version for 
  x86-64 development and is maintained by Jan Hubicka < jh@suse.cz > and Andreas Jaeger < aj@suse.de >. 
  pch-branch. This branch contains work-in-progress towards a precompiled 
  header implementation, including lots of garbage collector changes. As yet, 
  the branch contains no actual precompiled header work; a public 
  announcement will be made on the GCC 
  mailing list when it is ready for testing. 
  cp-parser-branch. This branch contains a new hand-written recursive 
  descent parser for C++. 
  tree-ssa-20020619-branch 
  
Web pages
The web pages for the GCC project are also in the CVS repository and you can 
check them out, submit patches, etc just like you do for the compiler itself. 
Use cvs co wwwdocs to check out the web pages.
The host system
The setup of the machine running the gcc.gnu.org site is also available, 
through cvsweb 
and anonymous read-only CVS. Use the same procedure as above, but replace the 
repository bits with :pserver:anoncvs@gcc.gnu.org:/cvs/sourceware 
and infra .


Please send FSF & GNU inquiries & questions to gnu@gnu.org . There are also other ways to contact the 
FSF.
These pages are maintained by The GCC 
team .
Please send comments on these web pages and GCC to gcc@gnu.org or gcc@gcc.gnu.org , send other questions to gnu@gnu.org . 
Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite 330, 
Boston, MA 02111, USA.
Verbatim copying and distribution of this entire article is permitted in any 
medium, provided this notice is preserved.

  
  
    Last modified 2002-08-19 
     
Attachment:
valid-xhtml10
Description: Binary data