Changes between Version 10 and Version 11 of Building/GettingTheSources


Ignore:
Timestamp:
Jul 11, 2007 1:10:33 PM (8 years ago)
Author:
simonpj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Building/GettingTheSources

    v10 v11  
    3535}}} 
    3636 
    37 '''NOTE''': You really want {{{--partial}}} when grabbing GHC.  There are some 15000 patches in the repository, which take a long time to download without {{{--partial}}}.  The {{{darcs-all}}} script automatically adds {{{--partial}}} for the packages.  However, if you are a developer and intend to make changes to your GHC source tree, then we recommend ''not'' using `--partial`, and adding `--complete` to the `darcs-all` command-line which disables its default use of `--partial`.  We avoid `--partial` when developing due to bugs in darcs that affect moving patches between partial repositories.  Getting GHC without `--partial` may take a while, so we occasionally make tarballs of the full GHC repo, which you can look for in [http://darcs.haskell.org/ here] (look for files named `ghc-HEAD-<date>.tar.bz2`). 
     37'''NOTE''': You really want {{{--partial}}} when grabbing GHC.  There are some 15000 patches in the repository, which take a long time to download without {{{--partial}}}.  The {{{darcs-all}}} script automatically adds {{{--partial}}} for the packages.  However, if you are a developer and intend to make changes to your GHC source tree, then we recommend ''not'' using `--partial`, and adding `--complete` to the `darcs-all` command-line which disables its default use of `--partial`.  We avoid `--partial` when developing due to bugs in darcs that affect moving patches between partial repositories. 
     38 
     39Getting GHC without `--partial` may take a while, so we occasionally make tarballs of the full GHC repo, which you can look for in [http://darcs.haskell.org/ here] (look for files named `ghc-HEAD-<date>.tar.bz2`).  However, if you do this, do it as follows  
     40{{{ 
     41   $ ..untar tarball.. 
     42   $ cd ghc 
     43   $ darcs pull -a 
     44   $ ./darcs-all get 
     45}}} 
     46If you do `darcs-all`, and that pulls in a patch that modifies the `darcs-all` script itself, then bizarre things can (or at least could in the past) happen.  The safe thing to do is to get your main `ghc` repo up to date (the `darcs pull` line) and then run the script. 
    3847 
    3948The above will grab the "core" set of packages.  This is the minimal set of packages required to bootstrap GHC.  If you want to get a more comprehensive set of packages and include them in your GHC build, then you can say: