haddock suggestion -- %{FILE}

Duncan Coutts duncan.coutts at worc.ox.ac.uk
Tue Jan 9 13:25:10 EST 2007

On Tue, 2007-01-09 at 09:32 -0800, Conal Elliott wrote:
> The only pre-processing is what's caused by using the cabal directive
> "Extensions: CPP".

> Fiddling with flags, I see that -optP-P is the culprit.  Removing it:
> bash-3.2$ ghc -E -cpp -o z src/Graphics/UI/TV/Input.hs
> -Dmingw32_BUILD_OS -Dmingw32_HOST_OS -Di386_BUILD_ARCH
> -Di386_HOST_ARCH -D__GLASGOW_HASKELL__=606 -D__HADDOCK__; head -3 z
> # 1 "src/Graphics/UI/TV/Input.hs"
> # 1 "<built-in>"
> # 1 "<command line>"
> bash-3.2$ 

> Any ideas?  - Conal

So for a quick hack, modify Cabal to unconditionally omit -optP-P and
see if that makes all your links come out right.

Probably the right thing to do however is to have Cabal use the -optP-P
option only when we're using haddock-0.7 or older (otherwise haddock-0.7
users will get a lexical error when haddock encounters the C line

I think at the moment Cabal doesn't check haddock's version number at
all. So that's something to look at if you or anyone else want to come
up with a patch for this.


More information about the Libraries mailing list