which contains GHC itself and the "boot" libraries.
- 2. Check out the source code from darcs
- ---------------------------------------
+ 2. Check out the source code from git
+ -------------------------------------
- The recommended way to get a darcs checkout is to start off by
- downloading a snapshot with a name like:
+ First get the GHC git repository:
- ghc-HEAD-2009-09-09-ghc-corelibs-testsuite.tar.bz2
+ $ git clone http://darcs.haskell.org/ghc.git/
- from:
-
- http://darcs.haskell.org/
-
- and then untar it and bring it up-to-date with:
-
- $ cd ghc
- $ ./darcs-all get
-
-
- Alternatively you can use darcs to get the repos, but it will take a
- lot longer. First get the GHC darcs repository:
-
- $ darcs get http://darcs.haskell.org/ghc/
-
- Then run the darcs-all script in that repository
+ Then run the sync-all script in that repository
to get the other repositories:
$ cd ghc
- $ chmod +x darcs-all
- $ ./darcs-all get
+ $ ./sync-all get
This checks out the "boot" packages.
is itself written in Haskell. For instructions on how to port GHC to a
new platform, see the Building Guide.
-If you're building from darcs sources (as opposed to a source
+If you're building from git sources (as opposed to a source
distribution) then you also need to install Happy [4] and Alex [5].
For building library documentation, you'll need Haddock [6]. To build
$ make install
The "perl boot" step is only necessary if this is a tree checked out
-from darcs. For source distributions downloaded from GHC's web site,
+from git. For source distributions downloaded from GHC's web site,
this step has already been performed.
These steps give you the default build, which includes everything
optimised and built in various ways (eg. profiling libs are built).
-It can take a long time. To customise the build, see the file
-HACKING.
+It can take a long time. To customise the build, see the file HACKING.