On 15 June 2010 15:13, Stephen Tetley wrote:
>
> There is actually no corresponding *lib* directory, but haddock still
> works fine.
This is a mistake on my part - I do have a corresponding lib directory
which includes a package.conf.d directory - for GHC-6.12.1 (I was
looking at the directory t
Hello all
I don't know if this helps at all, but for a GHC 6.12.1 installed from
the ghc-installer rather than HP I get:
Cygwin prompt on WinXP...
$ ./haddock.exe --print-ghc-libdir
C:\ghc\ghc-6.12.1\bin\..\lib
There is actually no corresponding *lib* directory, but haddock still
works fine.
B
I haven't been following closely, but how did you install haddock? From a binary dist? Is it possible that one of the Windows binary dists has a "baked-in" location for something on the E: drive, which existed on the packager's machine but not on the final installed machine?Regards,
MalcolmOn
2010/6/14 Dominic Steinitz :
> ..\ThirdParty\Haskell_Platform\2010.1.0.0\bin\haddock.exe BackendC\Core.hs
>
> haddock.exe: can't find a package database at
> E:\ghc\ghc-6.12.1lib\package.conf.d
>
> But if I do haddock --help there is no option to set the package database and
> I
> don't even have
..\ThirdParty\Haskell_Platform\2010.1.0.0\bin\haddock.exe BackendC\Core.hs
haddock.exe: can't find a package database at
E:\ghc\ghc-6.12.1lib\package.conf.d
But if I do haddock --help there is no option to set the package database and I
don't even have an E: drive.
I'm on windows in case that w
