Changes between Version 22 and Version 23 of Commentary/Libraries


Ignore:
Timestamp:
Oct 1, 2009 1:26:30 PM (6 years ago)
Author:
simonmar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Commentary/Libraries

    v22 v23  
    33All GHC build trees contain a set of libraries, called the '''Boot Packages'''.  These are the libraries that GHC's source code imports.  Obviously you need the boot packages to build GHC at all. 
    44 
    5 The Boot Packages, along with the other subcomponents of the GHC build system, are in the file `packages` in a GHC tree. To get a list of them, you can run `make show VALUE=PACKAGES` in a configured GHC build tree.  (This variable is set in `$(TOP)/ghc.mk`.) 
     5The Boot Packages, along with the other subcomponents of the GHC build system, are in the file `packages` in a GHC tree. To get a list of them, do the following in a configured GHC build tree: 
    66 
    7 You can see exactly which versions of what packages GHC depends on by looking in `$(TOP)/compiler/ghc.cabal.in`. 
     7To find out which packages are currently zero-boot packages, do the following in a GHC build: 
     8{{{ 
     9$ make show VALUE=PACKAGES 
     10}}} 
     11 
     12(The `PACKAGES` variable is set in `$(TOP)/`[[GhcFile(ghc.mk)]].) 
     13 
     14You can see exactly which versions of what packages GHC depends on by looking in `$(TOP)/`[[GhcFile(compiler/ghc.cabal.in)]]. 
    815 
    916Boot packages can be classified in three different ways: 
     
    3845 
    3946As time goes on, a Zero-boot package may become an ordinary boot package, because the bootstrap compiler is expected to have (a sufficiently up to date) version of the package already. 
     47 
     48To find out which packages are currently zero-boot packages, do the following in a GHC build: 
     49{{{ 
     50$ make show VALUE=BOOT_PKGS 
     51}}} 
    4052 
    4153The current Zero-boot packages are: