2010/6/14 Dominic Steinitz :

...

Try "--optghc=-package-conf --optghc=<file>", to point Haddock at the custom DB.

Hi David, Thanks for the quick response. No dice I am afraid. Dominic. BTW this (using optghc) used to work on previous versions of haddock (iirc 2.4 and 2.5).

..\ThirdParty\Haskell_Platform\2010.1.0.0\bin\haddock.exe --optghc=-package-conf --optghc=c:\p4wksp\steinitd_fpf_exdate_ws\FPF_Dev.br\ThirdParty\haskell _packages\fpf.package.conf backendc\PAD2C.hs

haddock.exe: can't find a package database at E:\ghc\ghc-6.12.1 \lib\package.conf.d

OK, it seems like the path from the ghc-paths package overrided what you specified. I'm not sure this will work, but you could try: haddock -B c:\p4wksp\steinitd_fpf_exdate_ws\FPF_Dev.br\ThirdParty\haskell_packages\fpf.package.conf David

David Waern writes:

2010/6/14 David Waern :

...

OK, it seems like the path from the ghc-paths package overrided what you specified. I'm not sure this will work, but you could try:

 haddock -B

c:\p4wksp\steinitd_fpf_exdate_ws\FPF_Dev.br\ThirdParty\haskell_packages\fpf.pack age.conf

Sorry, that should be

haddock -B

c:\p4wksp\steinitd_fpf_exdate_ws\FPF_Dev.br\ThirdParty\haskell_packages

David

Better but no cigar. ..\ThirdParty\Haskell_Platform\2010.1.0.0\bin\haddock.exe -B c:\p4wksp\steinitd_fpf_exdate_ws\FPF_Dev.br\ThirdParty\haskell_packages\fpf.pack age.conf backendc\PAD2C.hs haddock.exe: can't find a package database at C:\p4wksp\steinitd_fpf_exdate_ws\FPF_Dev.br\ThirdParty\haskell_packages\fpf.pack age.conf\package.conf.d And indeed I do not have a directory called package.conf.d. So I created one and copied our custom package databse into it but still no luck: ..\ThirdParty\Haskell_Platform\2010.1.0.0\bin\haddock.exe -B c:\p4wksp\steinitd_fpf_exdate_ws\FPF_Dev.br\ThirdParty\haskell_packages backendc\PAD2C.hs haddock: internal Haddock or GHC error: C:\p4wksp\steinitd_fpf_exdate_ws\FPF_Dev.br\ThirdParty\haskell_packages\package. conf.d\package.cache: openBinaryFile: does not exist (No such file or directory) I'm not what this file is. Is it the same as the index file that cabal uses? Dominic.

David Waern writes:

I think using --optghc=-package-conf is the correct way to point to another package DB, so I'll look into why it doesn't work.

Perhaps another line of attack would be to see why haddock thinks I have an "E:" drive?

2010/6/15 David Waern :

2010/6/15 Dominic Steinitz :

...

David Waern writes:

...

I think using --optghc=-package-conf is the correct way to point to another package DB, so I'll look into why it doesn't work.

Perhaps another line of attack would be to see why haddock thinks I have an "E:" drive?

Right. However I suspect it's not a problem with Haddock but rather something to do with the platform.

Here's something similar: http://trac.haskell.org/haskell-platform/ticket/119 I tried myself on windows, and haddock --print-ghc-libdir yields: E:\ghc\ghc-6.12.1\lib and I don't have an E: either. So Haddock seems to be more or less broken on windows in the current platform. David

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. Best wishes Stephen

malcolm.wallace writes:

I haven't been following closely, but how did you install haddock? From a

one of the Windows binary dists has a "baked-in" location for something on

binary dist? Is it possible that the E: drive, which existed on

the packager's machine but not on the final installed machine?

We are on the Haskell Platform 2010.1.0.0 and haddock comes as a .exe with it. Does anyone have any suggestions or do I have to start building haddock myself? Thanks, Dominic.