This is the case on Windows (as we have no shell wrappers), and mingw's
shell doesn't like an empty list of things in a "for" command.

This means -e must be separated from its argument by a space.
It therefore doesn't try to parse "-exclude-module" as
"execute xclude-module".

We weren't printing any warning for a commandline like
    ghc -M Foo.hs -optdep--exclude-module=Bar -fffi
but the last 2 flags are both deprecated.

Now that we make bindists during validate, we can't assume that ISCC
is available.

This is a follow up to the patch tha fixes Trac #3439.
We had forgotten the dynamic linker, which needs to
know all these ticky symbols too.

This function was barfing on a type family tycon; which in turn
crashed the compiler (when -ticky is in use) because of the use in
CmmTicky.hs.  There's no need for it to reject such tycons, so I just
made it return Nothing rather than falling over.

This improves the performance of the mark/compact and mark/region
collectors, and paves the way for doing mark/region with smaller
region sizes, in the style of Immix.

Fixes compilation with gcc 4.4

We now use a tarball of it, so we don't want to get it from a darcs repo.

This implements the Haskell Prime proposal
  http://hackage.haskell.org/trac/haskell-prime/wiki/ExplicitForall

Flag is -XExplicitForAll

Implied by Opt_RankNTypes, Opt_Rank2Types, Opt_ScopedTypeVariables, 
           Opt_LiberalTypeSynonyms, Opt_ExistentialQuantification, 
           Opt_PolymorphicComponents 

Evac_thr.c and Scav_thr.c had no dependencies

If the two InstalledPackageIds are the same, then the packages are
interchangeable and we don't need to explicitly remove one of them.

We used to call the bootstrapping compiler to get its --supported-languages
but that doesn't work when it doesn't support all the extensions that we
need. In particular, compiling the new bytestring which needs NamedFieldPuns
broken when building with 6.8.2.
There's now a rather ugly sed script to extract the extensions from
DynFlags.hs.

To quiet those warnings from make about not being able to delete
directories.

Since we started using "| $$$$(dir $$$$@)/." they've started causing
problems for unknown reasons.

rather than our own copies