X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Finstalling.xml;h=09ce12dbc97af7c92fc62c68ef6f0c8b320f27e0;hb=3d6517d241095806c3247dc045a8071c09c96fc4;hp=71113ee51b4530979ae69e3df959e27372be5805;hpb=455a8da72d0340c1e9b9c6c946ca2aba7c78e59a;p=ghc-hetmet.git diff --git a/docs/users_guide/installing.xml b/docs/users_guide/installing.xml index 71113ee..09ce12d 100644 --- a/docs/users_guide/installing.xml +++ b/docs/users_guide/installing.xml @@ -10,10 +10,7 @@ Installing from binary distributions is easiest, and recommended! so you've got to bootstrap it somehow. We provide machine-generated C-files-from-Haskell for this purpose, but it's really quite a pain to use them. If you must build GHC from its sources, using a -binary-distributed GHC to do so is a sensible way to proceed. For the -other fptools programs, many are written in -Haskell, so binary distributions allow you to install them without -having a Haskell compiler.) +binary-distributed GHC to do so is a sensible way to proceed.) This guide is in several parts: @@ -40,7 +37,7 @@ having a Haskell compiler.) When a platform-specific package is available - For certain platforms, we provide GHC binaries packaged + Most common OSes provide GHC binaries packaged using the native package format for the platform. This is likely to be by far the best way to install GHC for your platform if one of these packages is available, since @@ -48,39 +45,7 @@ having a Haskell compiler.) system normally provides a way to uninstall the package at a later date. - We generally provide the following packages: - - - - RedHat or SuSE Linux/x86 - - RPM source & binary packages for RedHat and SuSE - Linux (x86 only) are available for most major - releases. - - - - - Debian Linux/x86 - - Debian packages for Linux (x86 only), also for most - major releases. - - - - - FreeBSD/x86 - - On FreeBSD/x86, GHC can be installed using either - the ports tree (cd /usr/ports/lang/ghc && make - install) or from a pre-compiled package - available from your local FreeBSD mirror. - - - - - Other platform-specific packages may be available, check - the GHC download page for details. + Check the distribution packages page to see if there is a package available for your platform. @@ -91,151 +56,19 @@ having a Haskell compiler.) -Binary distributions come in “bundles,” one bundle per file called -bundle-platform.tar.gz. (See the building guide for the definition of a platform.) Suppose that you untar a binary-distribution bundle, thus: +Binary distributions come in “bundles,” called +ghc-version-platform.tar.bz2. (See the building guide for the definition of a platform.) Suppose that you untar a binary-distribution bundle, thus: - % cd /your/scratch/space -% gunzip < ghc-x.xx-sun-sparc-solaris2.tar.gz | tar xvf - - - - - -Then you should find a single directory, -ghc-version, with the -following structure: - - - -binary distribution, layout -directory layout (binary distributions) - - - -Makefile.in - - -the raw material from which the Makefile -will be made (). - - - -configure - - -the configuration script (). - - - -README - - -Contains this file summary. - - - -INSTALL - - -Contains this description of how to install -the bundle. - - - -ANNOUNCE - - -The announcement message for the bundle. - - - -NEWS - - -release notes for the bundle—a longer version -of ANNOUNCE. For GHC, the release notes are contained in the User -Guide and this file isn't present. - - - - bin/platform - - -contains platform-specific executable -files to be invoked directly by the user. These are the files that -must end up in your path. - - - -lib/platform/ - - -contains platform-specific support -files for the installation. Typically there is a subdirectory for -each fptools project, whose name is the name of the project with its -version number. For example, for GHC there would be a sub-directory -ghc-x.xx/ where x.xx is the version number of GHC in the bundle. +% bunnzip2 < ghc-version-platform.tar.bz2 | tar xvf - -These sub-directories have the following general structure: - - - - - - -libHSstd.a etc: - - -supporting library archives. - - - -ghc-iface.prl etc: - - -support scripts. - - - -import/ - - -Interface files (.hi) for the prelude. - - - -include/ - - -A few C #include files. - - - - - - -share/ - - -contains platform-independent support files -for the installation. Again, there is a sub-directory for each -fptools project. - - - -html/ - - -contains HTML documentation files (one -sub-directory per project). - - - +Then you should find the bundle contents inside a single directory, +ghc-version. @@ -247,21 +80,7 @@ next? Well, you will at least need to run the configureconfigure script by changing directory into the top-level directory for the bundle and typing ./configure. That should convert -Makefile.in to Makefile. - - - -installing in-place -in-place installation -You can now either start using the tools in-situ without going -through any installation process, just type make in-place to set the -tools up for this. You'll also want to add the path which make will -now echo to your PATH environment variable. This option is useful if -you simply want to try out the package and/or you don't have the -necessary privileges (or inclination) to properly install the tools -locally. Note that if you do decide to install the package `properly' -at a later date, you have to go through the installation steps that -follow. +Makefile-vars.in to Makefile-vars.