GHC 6.8.2, Haddock not finding std libs

Please test as much as possible
One difference between 6.8.1 and 6.8.2 that I see is in running "runhaskell Setup.hs haddock" with Haddock 0.8 on Windows XP. Haddock is no longer able to resolve the names from the standard libraries. Running Haddock for Xyz-0.1... Warning: Xyz: the following names could not be resolved: FilePath Show Eq String Maybe Bool Char Int Thanks, Greg

On Fri, 2007-12-07 at 14:24 -0800, Greg Fitzgerald wrote:
Please test as much as possible
One difference between 6.8.1 and 6.8.2 that I see is in running "runhaskell Setup.hs haddock" with Haddock 0.8 on Windows XP. Haddock is no longer able to resolve the names from the standard libraries.
Really? I get the opposite. In 6.8.1 the ghc-pkg entries for the haddock files were messed somehow so Cabal would always ignore those packages and not ask haddock to try and generate links to them. From my testing that's fixed in the 6.8.2 snapshots.
Running Haddock for Xyz-0.1... Warning: Xyz: the following names could not be resolved: FilePath Show Eq String Maybe Bool Char Int
Did Cabal earlier give warnings like: The documentation for package base-3.0.0.0 is not installed. No links to it will be generated. That's what I was getting previously. Perhaps you can investigate further and give some more details. Duncan

Hi Greg, On Fri, Dec 07, 2007 at 02:24:18PM -0800, Greg Fitzgerald wrote:
Please test as much as possible
One difference between 6.8.1 and 6.8.2 that I see is in running "runhaskell Setup.hs haddock" with Haddock 0.8 on Windows XP. Haddock is no longer able to resolve the names from the standard libraries.
Running Haddock for Xyz-0.1... Warning: Xyz: the following names could not be resolved: FilePath Show Eq String Maybe Bool Char Int
Thanks for the report! The problem is that the bindists are made with a haddock that makes platform independent haddock files (which means we treat Int as being 64-bit), but the current release doesn't understand that (on 32-bit platforms it tries to read Ints as 32-bit). There should be a new haddock release shortly, which fixes that as well as an HTML link bug. Or you can get the latest source with darcs from http://darcs.haskell.org/haddock/ Thanks Ian

Haddock is no longer able to resolve the names from the standard libraries. There should be a new haddock release shortly, which fixes that as well as an HTML link bug. Or you can get the latest source with darcs
The darcs version fixes the issue. Thanks Ian! -Greg

On Mon, Dec 10, 2007 at 10:27:02AM -0800, Greg Fitzgerald wrote:
Haddock is no longer able to resolve the names from the standard libraries. There should be a new haddock release shortly, which fixes that as well as an HTML link bug. Or you can get the latest source with darcs
The darcs version fixes the issue. Thanks Ian!
Thanks for confirming! Ian
participants (3)
-
Duncan Coutts
-
Greg Fitzgerald
-
Ian Lynagh