X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fbuilding%2Fbuilding.xml;h=3bfe2941f9deb9cb441c0d5a80e304cda6b888f4;hb=fc04400c0b39f4598e20c5a23875f9a9629aa13a;hp=aed9ec5a6c0ba04b52c9bdd9ee5087d39a7a533b;hpb=dcfa2d6e88bcab484d2477d6cfbc9b5e073e752a;p=ghc-hetmet.git diff --git a/docs/building/building.xml b/docs/building/building.xml index aed9ec5..3bfe294 100644 --- a/docs/building/building.xml +++ b/docs/building/building.xml @@ -407,12 +407,12 @@ setsockopt IPTOS_THROUGHPUT: Invalid argument result in checking out the entire repository instead of just the fpconfig bit. $ cd directory -$ cvs checkout ghc hslibs libraries +$ cvs checkout ghc libraries The second command here checks out the relevant modules you want to work on. For a GHC build, for instance, you need at least the ghc, - hslibs and libraries + and libraries modules (for a full list of the projects available, see ). @@ -605,7 +605,7 @@ $ lndir source-tree $ cvs co -r ghc-4-06 fpconfig $ cd fptools -$ cvs co -r ghc-4-06 ghc hslibs +$ cvs co -r ghc-4-06 ghc libraries @@ -793,8 +793,7 @@ $ cvs checkout nofib/spectral hslibsproject - Supplemental libraries for GHC - (required for building GHC). + Old, now deprecated, libraries. Everything in here is in libraries. @@ -843,8 +842,8 @@ $ cvs checkout nofib/spectral So, to build GHC you need at least the - ghc, libraries and - hslibs projects (a GHC source distribution will + ghc and libraries + projects (a GHC source distribution will already include the bits you need). @@ -2752,8 +2751,8 @@ directive. - EXCLUDE_SRCS - EXCLUDE_SRCS + EXCLUDED_SRCS + EXCLUDED_SRCS Set to a list of source files (relative to the @@ -2771,7 +2770,7 @@ directive. EXTRA_SRCS - EXCLUDE_SRCS + EXTRA_SRCS Set to a list of extra source files (perhaps @@ -2952,6 +2951,58 @@ directive. ones in boilerplate.mk. + + Platform settings + Platform settings + + + There are three platforms of interest when building GHC: + + + + The build platform + + The platform on which we are doing this build. + + + + + The host platform + + The platform on which these binaries will run. + + + + + The target platform + + The platform for which this compiler will generate code. + + + + + These platforms are set when running the + configure script, using the + , , and + options. The mk/config.mk + file defines several symbols related to the platform settings (see + mk/config.mk for details). + + We don't currently support build & host being different, because + the build process creates binaries that are both run during the build, + and also installed. + + If host and target are different, then we are building a + cross-compiler. For GHC, this means a compiler + which will generate intermediate .hc files to port to the target + architecture for bootstrapping. The libraries and stage 2 compiler + will be built as HC files for the target system (see for details. + + More details on when to use BUILD, HOST or TARGET can be found in + the comments in config.mk. + + Pattern rules and options Pattern rules @@ -3540,20 +3591,19 @@ $ make install Bootstrapping GHC on a system without GHC already installed is achieved by taking the intermediate C files (known - as HC files) from a GHC compilation on a supported system to the - target machine, and compiling them using gcc to get a working - GHC. + as HC files) from another GHC compilation, compiling them using gcc to + get a working GHC. NOTE: GHC versions 5.xx were hard to bootstrap from C. We recommend using GHC 6.0.1 or later. HC files are platform-dependent, so you have to get a set - that were generated on similar hardware. There may be some - supplied on the GHC download page, otherwise you'll have to - compile some up yourself, or start from - unregisterised HC files - see . + that were generated on the same platform. There + may be some supplied on the GHC download page, otherwise you'll have to + compile some up yourself, or start from + unregisterised HC files - see . The following steps should result in a working GHC build with full libraries: @@ -3567,7 +3617,7 @@ $ make install corresponding Haskell source (.hs or .lhs) in the compiler subdirectory ghc/compiler and in the libraries - (subdirectories of hslibs and + (subdirectories of libraries). @@ -3696,7 +3746,7 @@ $ ./configure --enable-hc-boot --enable-hc-boot-unregisterised $ cd T/ghc/includes -$ make ghcconfig.h +$ make @@ -3722,11 +3772,12 @@ $ ./configure GhcUnregisterised = YES GhcLibHcOpts = -O -fvia-C -keep-hc-files +GhcRtsHcOpts = -keep-hc-files GhcLibWays = SplitObjs = NO GhcWithNativeCodeGen = NO GhcWithInterpreter = NO -GhcStage1HcOpts = -O -fasm +GhcStage1HcOpts = -O GhcStage2HcOpts = -O -fvia-C -keep-hc-files SRC_HC_OPTS += -H32m GhcBootLibs = YES @@ -3755,20 +3806,19 @@ GhcBootLibs = YES Copy - T/ghc/includes/ghcconfig.h + T/ghc/includes/ghcautoconf.h, T/ghc/includes/DerivedConstants.h, and T/ghc/includes/GHCConstants.h to H/ghc/includes. Note that we are building on the host machine, using the - target machine's config.h file. This + target machine's configuration files. This is so that the intermediate C files generated here will be suitable for compiling on the target system. - - Touch ghcconfig.h, just to make - sure it doesn't get replaced during the build: -$ touch H/ghc/includes/ghcconfig.h + Touch the generated configuration files, just to make + sure they don't get replaced during the build: +$ touch H/ghc/includes/{ghcautoconf.h,DerivedConstants.h.GHCConstants.h.mkDerivedConstants.c,mkDerivedConstantsHdr,mkDerivedConstants.o,mkGHCConstants,mkGHCConstants.o} @@ -3790,14 +3840,14 @@ $ make boot stage=2 && make stage=2 -$ cd H/ghc/lib +$ cd H/ghc/lib/compat $ make clean -$ make -k UseStage1=YES \ - EXTRA_HC_OPTS='-O -fvia-C -keep-hc-files' +$ rm .depend +$ make boot UseStage1=YES +$ make -k UseStage1=YES EXTRA_HC_OPTS='-O -fvia-C -keep-hc-files' $ cd H/ghc/utils $ make clean -$ make -k UseStage1=YES \ - EXTRA_HC_OPTS='-O -fvia-C -keep-hc-files' +$ make -k UseStage1=YES EXTRA_HC_OPTS='-O -fvia-C -keep-hc-files' @@ -4768,6 +4818,11 @@ so you will need to add emacs/bin to your PATH + + You might want to install GLUT in your MSYS/Cygwin + installation, otherwise the GLUT package will not be built with + GHC. + Finally, check out a copy of GHC sources from