Ticket #939 (closed bug: invalid)

Opened 7 years ago

Last modified 5 years ago

Possible bug building wxhaskell

Reported by: dagit@… Owned by:
Priority: normal Milestone:
Component: Compiler Version: 6.6
Keywords: Cc:
Operating System: Unknown/Multiple Architecture: x86
Type of failure: Difficulty: Unknown
Test Case: Blocked By:
Blocking: Related Tickets:

Description

I appologize if this isn't a GHC bug but since it started happening after a GHC upgrade I suspect it's a GHC bug.

After upgrading to ghc6.6 on windows (using the release binary) I tried to install the current wxhaskell release found here:  http://wxhaskell.sourceforge.net/download.html (version wxhaskell-src-0.9.4-1.zip)

I have used wxhaskell on this machine before with older version of ghc (including ghc6.5, specifically visual haskell) so my environment for building the wxhaskell source was already setup. When I first got the error below I thought maybe my version of wxhaskell was messed up so I redownloaded the above zip file and unzipped a fresh copy.

I unziped the source then I typed: configure && make

Things went along fairly smoothly for a while then suddenly I got this error message: ghc -c wx/src/Graphics/UI/WX/Types.hs -o out/wx/imports/Graphics/UI/WX/Types.o -iout/wx/imports -odir out/wx/imports -hidir out/wx/imports -fvia-C -package-name wx -iout/wx/imports

wx/src/Graphics/UI/WX/Types.hs:94:0:

Bad interface file: out/wx/imports/Graphics/UI/WXCore/Types.hi

Something is amiss; requested module wx:Graphics.UI.WXCore.Types differs from name found in the interface file wxcore:Graphics.UI.WXCore.Types

make: *** [out/wx/imports/Graphics/UI/WX/Types.o] Error 1

Change History

Changed 7 years ago by duncan

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

It's not a GHC bug. It's a problem with the way wxHaskell is built. Admitidedly this is due to a slight change in the way GHC manages packages but it's not a bug as such, wxHaskell just needs fixing.

What needs to happen is that the packages must be registered locally before they get used in other packages. Also, instead of importing the modules from the other package directly from the directory with -i foo/, it must be via -package foo.

So you'll need to get in contact with someone who knows enough about wxHaskell's build system to fix it. Try asking on the ghc-users or haskell-cafe mailing lists.

Changed 7 years ago by duncan

I should note that several other packages had this exact same problem and I fixed a couple of them (buddha & Gtk2Hs), but sadly I'm not at all familiar with the wxHaskell build system.

Changed 5 years ago by simonmar

  • os changed from Unknown to Unknown/Multiple
Note: See TracTickets for help on using tickets.