Changes between Version 56 and Version 57 of Building/GettingTheSources


Ignore:
Timestamp:
Mar 31, 2011 8:40:15 PM (4 years ago)
Author:
igloo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Building/GettingTheSources

    v56 v57  
    5656
    5757
    58 == Getting a complete repository tarball ==
    59 
    60 Sometimes it's easier to download the entire set of repositories, complete with history, as a tarball and unpack it onto your system.  These bundles are on [http://darcs.haskell.org/] usually in three files of the form
    61    * `ghc-HEAD-2007-08-29-ghc-corelibs-testsuite.tar.bz2` (100Mbytes)
    62    * `ghc-HEAD-2007-08-29-ghc-corelibs.tar.bz2` (90 Mbytes)
    63    * `ghc-HEAD-2007-08-29-ghc.tar.bz2` (60 Mbytes)
    64 Each of these is a subset of the previous one; pick the smallest one that has what you need.  Of course, the dates may vary. 
    65 
    66 Here's how to use the bundles:
    67 
    68  1. Unpack the bundle, which will create a directory called `ghc`.  You can rename this directory freely.
    69  0. Change into the new directory, and pull patches from the main GHC repository:
    70 {{{
    71    $ cd ghc
    72    $ darcs pull -a
    73 }}}
    74  0. Some core libraries might have been added to HEAD which were not in the last tarball. This means that after doing the last pull (which updates the list of core libraries) we need to do this to get any new libraries:
    75 {{{
    76    $ chmod +x darcs-all
    77    $ ./darcs-all get
    78 }}}
    79  0. Now use the `darcs-all` script to pull patches from all the library repositories that came in the tarball, and the testsuite repository:
    80 {{{
    81    $ ./darcs-all pull -a
    82 }}}
    83    The command `darcs-all` automates the fetching of the repositories for the libraries.
    84 
    85 If you omit step (3), then `darcs-all` will pull patches into the GHC repository too. If one of those patches modifies the `darcs-all` script itself, then bizarre things can happen (or at least: in the past, they could happen.) The safe thing to do is to get your main `ghc` repo up to date (step 3) and then run the script.
    86 
    87 If you see any of the following error messages on Windows (the filename varies)
    88 {{{
    89 Warning: ./compiler/main/DynFlags.hs-0: renameFile: permission denied (Permission denied)
    90 darcs failed:  Error applying hunk to file ./compiler/main/DynFlags.hs
    91 Error applying patch to the working directory.
    92 }}}
    93 {{{
    94 darcs failed:  ./ghc.mk-0: renameFile: permission denied (Permission denied)
    95 Your repository is now in an inconsistent state.
    96 This must be fixed by running darcs repair.
    97 }}}
    98 after doing {{{darcs pull -a}}}, then use newest darcs. Version 2.0.2 is broken, version 2.3.1 works.
    99 
    10058== Windows ==
    10159