Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#2335 closed bug (fixed)

Haddock's internal GHC version must match the configured GHC version

Reported by: bos Owned by:
Priority: high Milestone: 6.10.1
Component: Build System Version: 6.8.2
Keywords: Cc: batterseapower+GHC2335@…
Operating System: Linux Architecture: Unknown/Multiple
Type of failure: None/Unknown Test Case:
Blocked By: Blocking:
Related Tickets: Differential Rev(s):
Wiki Page:


I'm trying to build ghc- with haddock-, and I get the above error when the build tries to emit docs for the base package.

I'm not really sure how to make progress here. 2.0 is the default version of haddock distributed with Fedora 9. I don't know if haddock 0.8 has the same problem, but unfortunately I can't use it without tremendous bother.

Doubly unfortunately, I can't actually tell whether the error is coming from GHC, the system's Haddock, or some other place entirely.

What I'm trying to do is prepare the GHC 6.8.3 RPM for Fedora, so that we can roll it in short order once the official release is announced. I'm sorry to be so completely clueless :-(

Change History (5)

comment:1 Changed 10 years ago by igloo

Component: CompilerBuild System
difficulty: Unknown
Milestone: 6.10 branch
Priority: normalhigh

See the thread started here:

and continued here:

The short story is that you either need to go back to haddock 0.8, or do a bootstrapping dance (compile 6.8.3 without haddocking the libraries, compile haddock 2, do your final 6.8.3 build with haddocking).

If we (as a community) want to move to haddock 2 then I think we need to bundle it with GHC.

comment:2 Changed 10 years ago by simonmar

Milestone: 6.10 branch6.10.1

comment:3 Changed 10 years ago by batterseapower

Cc: batterseapower+GHC2335@… added

comment:4 Changed 10 years ago by igloo

Resolution: fixed
Status: newclosed

haddock 2 is now built while building ghc.

comment:5 Changed 10 years ago by simonmar

Architecture: MultipleUnknown/Multiple
Note: See TracTickets for help on using tickets.