I can't remember where this bug showed up, but we were abstracting over a
coercion variable (co :: a ~ T), without also abstracting over 'a'.

The fix is simple.

This fixes Trac #2024; worth merging onto 6.8 branch.

Rules for imported things are now kept in the global rule base, not
attached to the global Id.  The rule-check pass hadn't kept up.

This should fix it.

Add dyn-wrapper.c used as cross-plattform launch wrapper for executables using dynamic libraries in non-standard places

The core type-matcher Unify.match was previouly using tcView to expand
types, because it must treat newtypes as distinct from their representation.
But that meant that it also treated the PredType {C Int} as distinct from
its representation type (:TC Int).  And that in turn was causing a rule
not to fire, because the argument types didn't match up.

For this to happen we need to get a situation where we have

  a = :DC blah blah	-- Dictionary
  ....(f a).....

Now a has type (:TC Int), bu the RULE for f expects an argument 
of type {C Int}.  Roman found that just this was happening.

I can't think how this one escaped for so long, but
	(error "foo") 
should have arityType ABot, just as 'error' itself does.

This improves eta expansion.  I spotted it when looking at the function

  Data.Array.Parallel.Arr.BBArr.writeMBB

in the ndp package.

We were making filenames like
dist/build/GHC/Base.p_.o
rather than
dist/build/GHC/Base.p_o

Split off a FastBool module, to avoid a circular import with Panic

Patch from Bertram Felgenhauer <int-e@gmx.de>

Fixes the build on OpenBSD (trac #2009). Based on a patch from kili.