rather then the bootstrapping compiler. This fixes problems where the
bootstrapping compiler dynamically links against libraries not on the
target machine.

Thorikil ran into this when doing a PPC OS X build. We now also don't
use -m32 on PPC/OSX, but I don't think it should be necessary. We can
add it back if it does turn out to be.

Stops user-installed packages breaking the build

The latter is only used when compiling .hc files, whereas we need it for
.c files too.

We used to set it only in machdepCCOpts, so this is more consistent

Recent versions of AS_LITERAL_IF don't like *'s.  Fix from

http://blog.gmane.org/gmane.comp.sysutils.autoconf.general/month=20100701

We were using it only when building the RTS, and only on certain
platforms. However, some versions of OS X need the flag, while others
don't support it, so we now test for it properly.

It now understand the ghc-stage[123] names we use in-tree, and it won't
go looking for any old ghc-pkg if it can't find the one that matches
ghc.

rather than assuming that all GNU ar's do.
Apparently OpenBSD's older version doesn't.

Patch contributed by asuffield@suffields.me.uk

Not everything is fixed yet; see #3642

Now that the haskell98 dependency of GHC has been removed, the
Happy-generated parsers must import Data.Array rather than Array, and
that change was made in Happy 1.16.

The build system should use 'find' and 'sort' that are discovered by
configure, not the ones in your path.  On Windows the ones in your path
might well be the non-Unixy Windows versions.

This patch fixes the ones I tripped over. There may be more.

It wasn't failing even when the DTD was not found.

 * use --nonet, so xmllint and co don't go off trying to download
   stuff from the web

 * use the http:// reference for the stylesheet, so we don't have to
   search the filesystem for it (should speedup ./configure)

Now configure looks for it as an installed program instead.

Now we have variables for whether or not to build the docbook docs as
HTML, as PS, and as PDF. The configure script output now matches what
the build system will do (except it cannot take account of any
mk/build.mk settings, of course).

We only need the forwardslash mode now, so always use that mode and
don't accept any arguments.