GitLab

Old aliases kept for compatibility

Ready to make the 1.6 branch

GHC < 6.10 put "$topdir/include/mingw" in rts's installDirs. This
breaks when you want to use a different gcc, so we need to filter
it out.

We need to tell the gcc bundled with GHC on Windows where its mingw
include directory is

ie preserves any existing user-supplied path and args

This is like openBinaryTempFile except it doesn't mark the permissions
with 600. This means datafailes get the right permissions when they are
installed.

This should really be in the base package.

Now it matches Control.Exception's type

This time it should work on linux too! But more significantly
it should work when the user specifies a particular gcc. It
would be very bad if the user gave an alternative gcc but we
still gave it -B for the lib files of ghc's gcc. This go is
rather cleaner as it uses the new program post-conf system.

The post-conf action gets given the configured program and is
allowed to do more IO and can add any extra required program
args. Should make it easier to do the gcc -B thing or ld -x

Needs cpp pragma as it has to work with just ghc --make
Did I ever mention I that hate cpp and compat modules?

Convert any '-' in the package name to '_' when generating the
path env var as most shells do not allow '-' in env var names.

This needs a bit of a kludge, as the vanilla way doesn't really exist
as far as the build system is concerned. It's just the absence of way.

which did not have isInfixOf

As with the Paths_pkgname module, we map '-' to '_' as the
former is not a valid character in cpp macro identifiers.
Fixes cpp redefinition warnings. First reported by gwern.

Otherwise we don't get links to types from packages that we don't
directly depend on.

It was still defining CABAL_VERSION=1,5,3

Also, ban rather than just warn about the -optl-Wl,-s hack
now that Cabal strips exes by default.

due to the PackageSet/Index api changes

We allow extra rgs and the location of programs to be given to
the build and haddock commands, not just at configure time. The
code to do this is now simpler and more general. This should not
be the default use mode however since it involves configuring
the programs each time where as doing it at configure time allows
it to be done once and saved. Further, specifying a different
version of the program at build time than at configure time is
likely to fail, especially for the compiler programs. Changing
the compiler really requires reconfiguring.