Building the Glasgow tools can be complicated, mostly because there are so many permutations of what/why/how, e.g., "Build Happy with HBC, everything else with GHC, leave out profiling, and test it all on the `real' NoFib programs." Yeeps!
Happily, such complications don't apply to most people. A few common "strategies" serve most purposes. Pick one and proceed as suggested:
If you are going to do any building from sources (either from a source distribution or the CVS repository) then you need to read all of this manual in detail.
Here's a list of things to check before you get started.
http://www.dcs.gla.ac.uk/fp/software/ghc/ghc-bugs.htmlIf you feel there is still some shortcoming in our procedure or instructions, please report it. For GHC, please see the bug-reporting section of the User's guide (separate document), to maximise the usefulness of your report. If in doubt, please send a message to `glasgow-haskell-bugs@dcs.gla.ac.uk'.
The main question is whether or not the Haskell compiler (GHC) runs on your platform.
A "platform" is a architecture/manufacturer/operating-system combination, such as `sparc-sun-solaris2'. Other common ones are `alpha-dec-osf2', `hppa1.1-hp-hpux9', `i386-unknown-linux', `i386-unknown-solaris2', `i386-unknown-freebsd', `i386-unknown-cygwin32', `m68k-sun-sunos4', `mips-sgi-irix5', `sparc-sun-sunos4', `sparc-sun-solaris2', `powerpc-ibm-aix'.
Bear in mind that certain "bundles", e.g. parallel Haskell, may not work on all machines for which basic Haskell compiling is supported.
Some libraries may only work on a limited number of platforms; for example, a sockets library is of no use unless the operating system supports the underlying BSDisms.
The GHC hierarchy of Porting Goodness: (a) Best is a native-code generator; (b) next best is a "registerised" port; (c) the bare minimum is an "unregisterised" port. ("Unregisterised" is so terrible that we won't say more about it).
We use Sun4s running SunOS 4.1.3 and Solaris 2.5, and DEC Alphas running OSF/1 V2.0, so those are the "fully-supported" platforms, unsurprisingly. Both have native-code generators, for quicker compilations. The native-code generator for iX86 platforms (e.g., Linux ELF) is nearly working; but is not turned on by default.
Here's everything that's known about GHC ports. We identify platforms by their "canonical" CPU/Manufacturer/OS triple.
Note that some ports are fussy about which GCC version you use; or require GAS; or ...
http://mecca.spd.louisville.edu/~tjchol01/software/Profiling works, Concurrent/Parallel Haskell might work (AFAIK, untested).
Unless you hear otherwise, the other tools work if GHC works.
Haggis requires Concurrent Haskell to work.
Installing from binary distributions is easiest, and recommended! (Why binaries? Because GHC is a Haskell compiler written in Haskell, 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 distributions come in "bundles,"
one bundle per file called `<bundle>-<platform>.tar.gz'.
(See Section 3 What machines the Glasgow tools run on for what a platform is.)
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, `fptools', with the following structure:
This structure is designed so that you can unpack multiple bundles (including ones from different releases or platforms) into a single `fptools' directory:
% cd /your/scratch/space % gunzip < ghc-x.xx-sun-sparc-solaris2.tar.gz | tar xvf - % gunzip < happy-x.xx-sun-sparc-sunos4.tar.gz | tar xvf -
When you do multiple unpacks like this, the top level `Makefile', `README', and `INSTALL' get overwritten each time. That's fine -- they should be the same. Likewise, the `ANNOUNCE-<bundle>' and `NEWS-<bundle>' files will be duplicated across multiple platforms, so they will be harmlessly overwritten when you do multiple unpacks. Finally, the `share/' stuff will get harmlessly overwritten when you do multiple unpacks for one bundle on different platforms.
OK, so let's assume that you have unpacked your chosen bundles into a scratch directory `fptools'. What next? Well, you will at least need to run the `configure' script by changing your directory to `fptools' and typing `./configure'. That should convert `Makefile.in' to `Makefile'.
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 (where `make' is GNU make - you might have to type `gmake' to get it). 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 priviledges (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 follows.
To install an `fptools' package, you'll have to do the following:
When installing the user-invokable binaries, this installation procedure will install GHC as `ghc-x.xx' where `x.xx' is the version number of GHC. It will also make a link (in the binary installation directory) from `ghc' to `ghc-x.xx'. If you install multiple versions of GHC then the last one "wins", and "`ghc'" will invoke the last one installed. You can change this manually if you want. But regardless, `ghc-x.xx' should always invoke GHC version `x.xx'.
There are plenty of "non-basic" GHC bundles. The files for them are called `ghc-x.xx-<bundle>-<platform>.tar.gz', where the `<platform>' is as above, and `<bundle>' is one of these:
One likely scenario is that you will grab three binary bundles -- basic, profiling, and concurrent.
The way to do this is, of course, to compile and run this program
(in a file `Main.hs'):
main = putStr "Hello, world!\n"
First, give yourself a convenient way to execute the driver script `ghc/driver/ghc', perhaps something like...
% ln -s /local/src/ghc-x.xx/ghc/driver/ghc ~/bin/alpha/ghc % rehash
Compile the program, using the `-v' (verbose) flag to verify that libraries, etc., are being found properly:
% ghc -v -o hello Main.hs
Now run it:
% ./hello Hello, world!
Some simple-but-profitable tests are to compile and run the notorious `nfib' program, using different numeric types. Start with `nfib :: Int -> Int', and then try `Integer', `Float', `Double', `Rational' and maybe `Complex Float'. Code for this is distributed in `ghc/misc/examples/nfib/'.
For more information on how to "drive" GHC, either do `ghc -help' or consult the User's Guide (distributed in `ghc/docs/users_guide').
Here are the gory details about some utility programs you may need; `perl' and `gcc' are the only important ones. (PVM is important if you're going for Parallel Haskell.) The `configure' script will tell you if you are missing something.
find bunch-of-dirs -name '*.o' -print | xargs ar q ...Unfortunately the Solaris `xargs' (the shell-script equivalent of `map') only "bites off" the `.o' files a few at a time -- with near-infinite rebuilding of the symbol table in the `.a' file. The best solution is to install a sane `xargs' from the GNU findutils distribution. You can unpack, build, and install the GNU version in the time the Solaris `xargs' mangles just one GHC library.
Two `fptools' projects are worth a quick note at this point, because they are useful for all the others:
You've been rash enough to want to build some of the Glasgow Functional Programming tools (GHC, Happy, nofib, etc) from source. You've slurped the source, from the CVS repository or from a source distribution, and now you're sitting looking at a huge mound of bits, wondering what to do next.
Gingerly, you type `make all'. Wrong already!
This rest of this guide is intended for duffers like me, who aren't really interested in Makefiles and systems configurations, but who need a mental model of the interlocking pieces so that they can make them work, extend them consistently when adding new software, and lay hands on them gently when they don't work.
The source code is held in your source tree. The root directory of your source tree must contain the following directories and files:
All the other directories are individual projects of the `fptools' system -- for example, the Glasgow Haskell Compiler (`ghc'), the Happy parser generator (`happy'), the `nofib' benchmark suite, and so on. You can have zero or more of these. Needless to say, some of them are needed to build others. For example, you need `happy' to build `ghc'. You can either grab `happy' too, or else you can use a version of `happy' that's already installed on your system, or grab a binary distribution of `happy' and install it.
The important thing to remember is that even if you want only one project (`happy', say), you must have a source tree whose root directory contains `Makefile', `mk/', `configure.in', and the project(s) you want (`happy/' in this case). You cannot get by with just the `happy/' directory.
While you can build a system in the source tree, we don't recommend it. We often want to build multiple versions of our software for different architectures, or with different options (e.g. profiling). It's very desirable to share a single copy of the source code among all these builds.
So for every source tree we have zero or more build trees. Each build tree is initially an exact copy of the source tree, except that each file is a symbolic link to the source file, rather than being a copy of the source file. There are "standard" Unix utilities that make such copies, so standard that they go by different names: `lndir', `mkshadowdir' are two (If you don't have either, the source distribution includes sources for the `X11' `lndir' -- check out `fptools/glafp-utils/lndir' ).
The build tree does not need to be anywhere near the source tree in the file system. Indeed, one advantage of separating the build tree from the source is that the build tree can be placed in a non-backed-up partition, saving your systems support people from backing up untold megabytes of easily-regenerated, and rapidly-changing, gubbins. The golden rule is that (with a single exception -- Section 6.3 Getting the build you want) absolutely everything in the build tree is either a symbolic link to the source tree, or else is mechanically generated. It should be perfectly OK for your build tree to vanish overnight; an hour or two compiling and you're on the road again.
You need to be a bit careful, though, that any new files you create (if you do any development work) are in the source tree, not a build tree!
Remember, that the source files in the build tree are symbolic links to the files in the source tree. (The build tree soon accumulates lots of built files like `Foo.o', as well.) You can delete a source file from the build tree without affecting the source tree (though it's an odd thing to do). On the other hand, if you edit a source file from the build tree, you'll edit the source-tree file directly. (You can set up Emacs so that if you edit a source file from the build tree, Emacs will silently create an edited copy of the source file in the build tree, leaving the source file unchanged; but the danger is that you think you've edited the source file whereas actually all you've done is edit the build-tree copy. More commonly you do want to edit the source file.)
Like the source tree, the top level of your build tree must (a linked copy of) the root directory of the `fptools' suite. Inside Makefiles, the root of your build tree is called `$(FPTOOLS_TOP)'. In the rest of this document path names are relative to `$(FPTOOLS_TOP)' unless otherwise stated. For example, the file `ghc/mk/target.mk' is actually `$(FPTOOLS_TOP)/ghc/mk/target.mk'.
When you build `fptools' you will be compiling code on a particular host platform, to run on a particular target platform (usually the same as the host platform). The difficulty is that there are minor differences between different platforms; minor, but enough that the code needs to be a bit different for each. There are some big differences too: for a different architecture we need to build GHC with a different native-code generator.
There are also knobs you can turn to control how the `fptools' software is built. For example, you might want to build GHC optimised (so that it runs fast) or unoptimised (so that you can compile it fast after you've modified it. Or, you might want to compile it with debugging on (so that extra consistency-checking code gets included) or off. And so on.
All of this stuff is called the configuration of your build. You set the configuration using an exciting three-step process.
./configure`configure''s mission is to scurry round your computer working out what architecture it has, what operating system, whether it has the `vfork' system call, where `yacc' is kept, whether `gcc' is available, where various obscure `#include' files are, whether it's a leap year, and what the systems manager had for lunch. It communicates these snippets of information in two ways:
And that's it for configuration. Simple, eh?
What do you put in your build-specific configuration file `mk/build.mk'? For almost all purposes all you will do is put make variable definitions that override those in `mk/config.mk.in'. The whole point of `mk/config.mk.in' -- and its derived counterpart `mk/config.mk' -- is to define the build configuration. It is heavily commented, as you will see if you look at it. So generally, what you do is edit `mk/config.mk.in' (read-only), and add definitions in `mk/build.mk' that override any of the `config.mk' definitions that you want to change. (The override occurs because the main boilerplate file, `mk/boilerplate.mk', includes `build.mk' after `config.mk'.)
For example, `config.mk.in' contains the definition:
ProjectsToBuild = glafp-utils literate happy ghc hslibs
The accompanying comment explains that this is the list of enabled projects; that is, if (after configuring) you type `gmake all' in `FPTOOLS_TOP' three specified projects will be made. If you want to add `green-card', you can add this line to `build.mk':
ProjectsToBuild += green-card
or, if you prefer,
ProjectsToBuild = glafp-utils literate happy ghc hslibs green-card
(GNU `make' allows existing definitions to have new text appended using the "`+='" operator, which is quite a convenient feature.)
When reading `config.mk.in', remember that anything between "`...`''" signs is going to be substituted by `configure' later. You can override the resulting definition if you want, but you need to be a bit surer what you are doing. For example, there's a line that says:
YACC = @Yacc@
This defines the Make variables `YACC' to the pathname for a Yacc that `configure' finds somewhere. If you have your own pet Yacc you want to use instead, that's fine. Just add this line to `mk/build.mk':
YACC = myyacc
You do not have to have a `mk/build.mk' file at all; if you don't, you'll get all the default settings from `mk/config.mk.in'.
You can also use `build.mk' to override anything that `configure' got wrong. One place where this happens often is with the definition of `FPTOOLS_TOP_ABS': this variable is supposed to be the canonical path to the top of your source tree, but if your system uses an automounter then the correct directory is hard to find automatically. If you find that `configure' has got it wrong, just put the correct definition in `build.mk'.
Let's summarise the steps you need to carry to get yourself a fully-configured build tree from scratch.
cd myfptools
mkshadowdir . /scratch/joe-bloggs/myfptools-sun4
You probably want to give the build tree a name that
suggests its main defining characteristic (in your mind at least),
in case you later add others.
cd /scratch/joe-bloggs/myfptools-sun4
autoconf
(You can skip this step if you are starting from a source distribution,
and you already have `configure' and `mk/config.h.in'.)
./configure
emacs mk/build.mk
You can make subsequent changes to `mk/build.mk' as often as you like. You do not have to run any further configuration programs to make these changes take effect. In theory you should, however, say `gmake clean', `gmake all', because configuration option changes could affect anything -- but in practice you are likely to know what's affected.
At this point you have made yourself a fully-configured build tree, so you are ready to start building real things.
The first thing you need to know is that you must use GNU `make', usually called `gmake', not standard Unix `make'. If you use standard Unix `make' you will get all sorts of error messages (but no damage) because the `fptools' `Makefiles' use GNU `make''s facilities extensively.
In any directory you should be able to make the following:
All of these standard targets automatically recurse into sub-directories. Certain other standard targets do not:
Foo.o : Baz.hiwhich says that the object file `Foo.o' depends on the interface file `Baz.hi' generated by compiling module `Baz'. The `.depend' file is automatically included by every Makefile.
Most `Makefiles' have targets other than these. You can find this out by looking in the `Makefile' itself.
`make' is great if everything works -- you type `gmake install' and, lo, the right things get compiled and installed in the right places. Our goal is to make this happen often, but somehow it often doesn't; instead some wierd error message eventually emerges from the bowels of a directory you didn't know existed.
The purpose of this section is to give you a road-map to help you figure out what is going right and what is going wrong.
To get started, let us look at the `Makefile' for an imaginary small `fptools' project, `small'. Each project in `fptools' has its own directory in `FPTOOLS_TOP', so the `small' project will have its own directory `FPOOLS_TOP/small/'. Inside the `small/' directory there will be a `Makefile', looking something like this:
# Makefile for fptools project "small" TOP = .. include $(TOP)/mk/boilerplate.mk SRCS = $(wildcard *.lhs) $(wildcard *.c) HS_PROG = small include $(TOP)/target.mk
This `Makefile' has three sections:
include ../mk/boilerplate.mk # NO NO NOWhy? Because the `boilerplate.mk' file needs to know where it is, so that it can, in turn, `include' other files. (Unfortunately, when an `include'd file does an `include', the filename is treated relative to the directory in which `gmake' is being run, not the directory in which the `included' sits.) In general, every file `foo.mk' assumes that `$(TOP)/mk/foo.mk' refers to itself. It is up to the `Makefile' doing the `include' to ensure this is the case. Files intended for inclusion in other `Makefile's are written to have the following property: after `foo.mk' is `include'd, it leaves `TOP' containing the same value as it had just before the `include' statement. In our example, this invariant guarantees that the `include' for `target.mk' will look in the same directory as that for `boilerplate.mk'.
In our example `Makefile', most of the work is done by the two `include'd files. When you say `gmake all', the following things happen:
All `Makefile's should follow the above three-section format.
Larger projects are usually structured into a nummber of sub-directories, each of which has its own `Makefile'. (In very large projects, this sub-structure might be iterated recursively, though that is rare.) To give you the idea, here's part of the directory structure for the (rather large) `ghc' project:
$(FPTOOLS_TOP)/ghc/
Makefile
mk/
boilerplate.mk
rules.mk
docs/
Makefile
...source files for documentation...
driver/
Makefile
...source files for driver...
compiler/
Makefile
parser/...source files for parser...
renamer/...source files for renamer...
...etc...
The sub-directories `docs', `driver', `compiler', and so on, each contains a sub-component of `ghc', and each has its own `Makefile'. There must also be a `Makefile' in `$(FPTOOLS_TOP)/ghc'. It does most of its work by recursively invoking `gmake' on the `Makefile's in the sub-directories. We say that `ghc/Makefile' is a non-leaf `Makefile', because it does little except organise its children, while the `Makefile's in the sub-directories are all leaf `Makefile's. (In principle the sub-directories might themselves contain a non-leaf `Makefile' and several sub-sub-directories, but that does not happen in `ghc'.)
The `Makefile' in `ghc/compiler' is considered a leaf `Makefile' even though the `ghc/compiler' has sub-directories, because these sub-directories do not themselves have `Makefile' in them. They are just used to structure the collection of modules that make up `ghc', but all are managed by the single `Makefile' in `ghc/compiler'.
You will notice that `ghc/' also contains a directory `ghc/mk/'. It contains `ghc'-specific `Makefile' boilerplate code. More precisely:
So these two files are the place to look for `ghc'-wide customisation of the standard boilerplate.
Every `Makefile' includes a `boilerplate.mk' file at the top, and `target.mk' file at the bottom. In this section we discuss what is in these files, and why there have to be two of them. In general:
SRC_HC_OPTS += -Othereby adding "`-O'" to the end of `SRC_HC_OPTS'.
$(HS_PROG) : $(OBJS)
$(HC) $(LD_OPTS) $< -o $@
If this rule was in `boilerplate.mk' then `$(HS_PROG)' and `$(OBJS)'
would not have their final values at the moment `gmake' encountered the
rule. Alas, `gmake' takes a snapshot of their current values, and
wires that snapshot into the rule.
(In contrast, the commands executed when the rule "fires" are
only substituted at the moment of firing.)
So, the rule must follow the definitions given in the `Makefile' itself.
If you look at `$(FPTOOLS_TOP)/mk/boilerplate.mk' you will find that it consists of the following sections, each held in a separate file:
Any of the variables and pattern rules defined by the boilerplate file can easily be overridden in any particular `Makefile', because the boilerplace `include' comes first. Definitions after this `include' directive simply override the default ones in `boilerplate.mk'.
The file `suffix.mk' defines standard pattern rules that say how to build one kind of file from another, for example, how to build a `.o' file from a `.c' file. (GNU `make''s pattern rules are more powerful and easier to use than Unix `make''s suffix rules.)
Almost all the rules look something like this:
%.o : %.c
@$(RM) $@
$(CC) $(CC_OPTS) -c $< -o $@
Here's how to understand the rule. It says that something.o (say `Foo.o') can be built from something.c (`Foo.c'), by invoking the C compiler (path name held in `$(CC)'), passing to it the options `$(CC_OPTS)' and the rule's dependent file of the rule `$<' (`Foo.c' in this case), and putting the result in the rule's target `$@' (`Foo.o' in this case).
Every program is held in a `make' variable defined in `mk/config.mk' -- look in `mk/config.mk' for the complete list. One important one is the Haskell compiler, which is called `$(HC)'.
Every programs options are are held in a `make' variables called `<prog>_OPTS'. the `<prog>_OPTS' variables are defined in `mk/opts.mk'. Almost all of them are defined like this:
CC_OPTS = $(SRC_CC_OPTS) $(WAY$(_way)_CC_OPTS) $($*_CC_OPTS) $(EXTRA_CC_OPTS)
The four variables from which `CC_OPTS' is built have the following meaning:
gmake libHS.a EXTRA_CC_OPTS="-v"
`target.mk' contains canned rules for all the standard targets described in Section 6.6 Standard targets. It is complicated by the fact that you don't want all of these rules to be active in every `Makefile'. Rather than have a plethora of tiny files which you can include selectively, there is a single file, `target.mk', which selectively includes rules based on whether you have defined certain variables in your `Makefile'. This section explains what rules you get, what variables control them, and what the rules do. Hopefully, you will also get enough of an idea of what is supposed to happen that you can read and understand any wierd special cases yourself.
All of these rules are "double-colon" rules, thus
install :: $(HS_PROG)
...how to install it...
GNU `make' treats double-colon rules as separate entities. If there are several double-colon rules for the same target it takes each in turn and fires it if its dependencies say to do so. This means that you can, for example, define both `HS_PROG' and `LIBRARY', which will generate two rules for `install'. When you type `gmake install' both rules will be fired, and both the program and the library will be installed, just as you wanted.
In leaf `Makefiles' the variable `SUBDIRS' is undefined. In non-leaf `Makefiles', `SUBDIRS' is set to the list of sub-directories that contain subordinate `Makefile's. It is up to you to set `SUBDIRS' in the `Makefile'. There is no automation here -- `SUBDIRS' is too important automate.
When `SUBDIRS' is defined, `target.mk' includes a rather neat rule for the standard targets (Section 6.6 Standard targets) that simply invokes `make' recursively in each of the sub-directories.
These recursive invocations are guaranteed to occur in the order in which the list of directories is specified in `SUBDIRS'. This guarantee can be important. For example, when you say `gmake boot' it can be important that the recursive invocation of `make boot' is done in one sub-directory (the include files, say) before another (the source files). Generally, put the most independent sub-directory first, and the most dependent last.
We sometimes want to build essentially the same system in several different "ways". For example, we want to build `ghc''s `Prelude' libraries with and without profiling, with and without concurrency, and so on, so that there is an appropriately-built library archive to link with when the user compiles his program. It would be possible to have a completely separate build tree for each such "way", but it would be horribly bureaucratic, especially since often only parts of the build tree need to be constructed in multiple ways.
Instead, the `template.mk' contains some clever magic to allow you to build several versions of a system; and to control locally how many versions are built and how they differ. This section explains the magic.
The files for a particular way are distinguished by munging the suffix. The "normal way" is always built, and its files have the standard suffices `.o', `.hi', and so on. In addition, you can build one or more extra ways, each distinguished by a way tag. The object files and interface files for one of these extra ways are distinguished by their suffix. For example, way `mp' has files `.mp_o' and `.mp_hi'. Library archives have their way tag the other side of the dot, for boring reasons; thus, `libHS_mp.a'.
A `make' variable called `way' holds the current way tag. `way' is only ever set on the command line of a recursive invocation of `gmake'. It is never set inside a `Makefile'. So it is a global constant for any one invocation of `gmake'. Two other `make' variables, `way_' and `_way' are immediately derived from `$(way)' and never altered. If `way' is not set, then neither are `way_' and `_way', and the invocation of `make' will build the "normal way". If `way' is set, then the other two variables are set in sympathy. For example, if `$(way)' is "`mp'", then `way_' is set to "`mp_'" and `_way' is set to "`_mp'". These three variables are then used when constructing file names.
So how does `make' ever get recursively invoked with `way' set? There are two ways in which this happens:
%.$(way_)o : %.lhs
$(HC) $(HC_OPTS) $< -o $@
Neat, eh?
Sometimes the canned rule just doesn't do the right thing. For example, in the `nofib' suite we want the link step to print out timing information. The thing to do here is not to define `HS_PROG' or `C_PROG', and instead define a special purpose rule in your own `Makefile'. By using different variable names you will avoid the canned rules being included, and conflicting with yours.
This section is for people trying to get GHC going by using the supplied intermediate C (`.hc') files. This would probably be because no binaries have been provided, or because the machine is not "fully supported."
The intermediate C files are normally made available together with a source release, please check the announce message for exact directions of where to find them. If we've haven't made them available or you can't find them, please ask.
Assuming you've got them, unpack them on top of a fresh source tree. Then follow the `normal' instructions in section 6 Building from source for setting up a build tree and configuring it. The only extra thing to remember when booting from `.hc' files is to add the following line to the `build.mk' file:
GhcWithHscBuiltViaC=YES
and proceed with doing a `make boot' followed by a `make all'.
That's the mechanics of the boot process, but, of course, if you're trying to boot on a platform that is not supported and significantly `different' from any of the supported ones, this is only the start of the adventure...(ToDo: porting tips - stuff to look out for, etc.)
WARNINGS about pitfalls and known "problems":
export TMPDIR=<dir>in your `build.mk' file. Then GHC and the other `fptools' programs will use the appropriate directory in all cases.
ar: filename GlaIOMonad__1_2s.o truncated to GlaIOMonad_ ar: filename GlaIOMonad__2_2s.o truncated to GlaIOMonad_ ...
SPECIALISATION MESSAGES (Desirable):
*** INSTANCES
{-# SPECIALIZE instance Eq [Class] #-}
{-# SPECIALIZE instance Eq (Class, [Class]) #-}
{-# SPECIALIZE instance Outputable [ClassOp] #-}
{-# SPECIALIZE instance Outputable [Id] #-}
% cd ghc/compiler % make EXTRA_HC_OPTS=-H32m # or some nice big number
Giant error 'do'ing getopts.pl: at ./lit2pgm.BOOT line 27.This indicates that your `perl' was mis-installed; the binary is unable to find the files for its "built-in" library. Speak to your perl installer, then re-try.
% cd $(libdir)/ghc-x.xx/sparc-sun-sunos4 % foreach i ( `find . -name '*.a' -print` ) # or other-shell equiv... ? ranlib $i ? # or, on some machines: ar s $i ? endWe'd be interested to know if this is still necessary.
SLIT("Hello, world")
Some `cpp's treat the comma inside the string as separating two macro arguments,
so you get
:731: macro `SLIT' used with too many (2) argsAlas, `cpp' doesn't tell you the offending file! Workaround: don't put wierd things in string args to `cpp' macros.
One of the most important features of GNU `make' that we use is the ability for a `Makefile' to include another named file, very like `cpp''s `#include' directive.
This document was generated on 23 January 1998 using the texi2html translator version 1.51.