Ticket #3531 (closed bug: fixed)

Opened 2 years ago

Last modified 2 years ago

Haddock needs tcRnGetInfo, hence GhcWithInterpreter YES

Reported by: donn Owned by: igloo
Priority: high Milestone: 6.12.1
Component: Build System Version: 6.11
Keywords: Cc:
Operating System: NetBSD Architecture: x86
Type of failure: Difficulty: Unknown
Test Case: Blocked By:
Blocking: Related Tickets:

Description

"Unregisterized" cross compile fails on stage2 build of Haddock because, in Interface.AttachInstances?, TcRnDriver? doesn't export tcRnGetInfo.

Presumably because #ifdef GCHI is false when GhcWithInterpreter? is NO.

From 6.11.20090919

Attachments

Change History

Changed 2 years ago by kili

  Changed 2 years ago by simonmar

  • owner set to simonmar
  • difficulty set to Unknown
  • priority changed from normal to high
  • milestone set to 6.12.1

  Changed 2 years ago by simonmar

  • status changed from new to closed
  • resolution set to fixed

Pushed, thanks! 

Sun Sep 20 19:13:19 BST 2009  Matthias Kilian <kili@outback.escape.de>
  * Don't build haddock if HADDOC_DOCS = NO, and disable HADDOC_DOCS if GhcWithInterpreter = NO

follow-up: ↓ 4   Changed 2 years ago by igloo

  • status changed from closed to reopened
  • resolution fixed deleted

Is there a reason for this function to be enabled only if GHCi is?

in reply to: ↑ 3   Changed 2 years ago by kili

Replying to igloo:

Is there a reason for this function to be enabled only if GHCi is?

It would be possible to compile and export tcRnGetInfo (and some other functions used by it) unconditionally. In addition, tcRnLookupName would have to be exported unconditionally, and the definition of InteractiveEval?.lookupName would have to be copied to haddock.

I could make a patch, but imho this would be a very ugly workaround.

  Changed 2 years ago by simonmar

  • owner changed from simonmar to igloo
  • status changed from reopened to new

Igloo is going to merge this ticket with #3558

  Changed 2 years ago by igloo

  • status changed from new to closed
  • resolution set to fixed

This bug has been fixed by the above patch, and #3558 is a task for us to do it better in the future.

Note: See TracTickets for help on using tickets.