Subject: Problem configuring c2hs with Cabal-1.2
I just downloaded c2hs (HEAD version) and tried to run "runhaskell Setup.hs configure" using the ghc 6.8 release candidate (i.e., Cabal 1.2), and got the following error:
Configuring c2hs-0.15.0... Setup.hs: Error: Non-empty library, but empty exposed modules list. Cabal may not build this library correctly
The .cabal file is parseable by ghc-6.6.1 (with Cabal 1.1.6.2). It's unclear to me whether this counts as a c2hs bug or a Cabal bug (maybe the above message should only be a warning?), so I'm cc'ing both lists. Also note that regardless, c2hs will need to be updated to work with base-2.0; when I tried ghc-6.8 with Cabal-1.1.6, I got the following error:
base/state/CIO.hs:71:7: Could not find module `System.Cmd': it is a member of package process-1.0, which is hidden
Best, -Judah
On Thu, 2007-09-13 at 15:17 -0700, Judah Jacobson wrote:
I just downloaded c2hs (HEAD version) and tried to run "runhaskell Setup.hs configure" using the ghc 6.8 release candidate (i.e., Cabal 1.2), and got the following error:
Configuring c2hs-0.15.0... Setup.hs: Error: Non-empty library, but empty exposed modules list. Cabal may not build this library correctly
The .cabal file is parseable by ghc-6.6.1 (with Cabal 1.1.6.2). It's unclear to me whether this counts as a c2hs bug or a Cabal bug (maybe the above message should only be a warning?), so I'm cc'ing both lists.
We debated for a while whether this was a cabal or c2hs bug. In the end we decided that Cabal was right, though in current Cabal versions the error message explaining why it's wrong has been improved.
Also note that regardless, c2hs will need to be updated to work with base-2.0
Yes, I'll do an updated release that's compatible with 6.8 and also addresses some other packaging complaints. Duncan
participants (2)
-
Duncan Coutts -
Judah Jacobson