Haddock vs GHC version

Neil Mitchell ndmitchell at gmail.com
Wed Apr 22 06:52:48 EDT 2009


>> How come it's picking up a different haddock? Is that an error with
>> the findExecutable, or is it deliberately trying to pick a newer
>> version?
> It's not looking for a newer version. It's looking for the first version
> that is on the Windows %PATH% env var.
> It looks like your real Windows %PATH% is not set to the same thing as
> your MSYS $PATH. I thought that MSYS made these consistent but perhaps
> not. In ghci, see what System.Environment.getEnv "PATH" says. Is it the
> same as MSYS's echo $PATH? I wonder if running export PATH in MSYS makes
> any difference.

I'm running under Windows command prompt under XP, so MSYS issues are

$ echo %PATH%
C:\Program Files\MiKTeX 2.7\miktex\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\Syste
m32\Wbem;c:\Program Files\IBM\WebSphere MQ\bin;c:\Program Files\IBM\WebSphere MQ
\Tools\c\Samples\Bin;C:\Program Files\Windows Imaging\;C:\Program Files\Graphviz
2.22\bin;C:\ghc\ghc-6.10.2\bin;C:\ghc\ghc-6.8.3\bin;C:\Program Files\Gtk2Hs\bin;
C:\bin;C:\Program Files\Haskell\bin;C:\Program Files\Microsoft

I've got a haddock in C:\Program Files\Haskell\bin and another in
C:\ghc\ghc-6.10.2\bin (and probably 6.8.3 as well). Is Cabal searching
the path in the right order?



More information about the cabal-devel mailing list