dependencies are checked even if buildable is False

[bos]

I have a little portion of a .cabal file that looks like this:

executable judy
  main-is: Judy.hs

  buildable: False
  ghc-options: -Wall -rtsopts
  build-depends:
    base == 4.*,
    criterion,
    judy -- DELIBERATELY NOT PRESENT

With cabal-install 1.19.2, I get the following error:

    $ cabal configure
    Resolving dependencies...
*** cabal: Could not resolve dependencies:
    trying: criterion-examples-0 (user goal)
*** next goal: judy (dependency of criterion-examples-0)
    Dependency tree exhaustively searched.

This seems weird and non-intuitive and wrong.

[bos]

Turns out this is an ancient bug, first reported as #224.

[kosmikus]

It's unclear if the old bug is really the same. I've done a quick test, and fixing it in the modular solver itself is nearly trivial. However, cabal-install performs a sanity check on the build plan the solver produces, and omitting the dependencies for non-buildable components from the build plan causes the sanity check to fail. I'm somewhat less familiar with that code, but I'll try to look at it.

Another potential option is to filter out the non-buildable components from the index before even passing the index to the solver, but that seems like a hack.

[TomMD]

Judging by the age, am I correct in assuming no one is working this bug and no solution has been agreed upon? This bug hinders any cross compilation (ios, android, halvm) project. If someone is willing to give a pointer on solution method then I'll look into making a patch and pull request.

[kosmikus]

This had indeed dropped off my radar again. I'm currently travelling, but I'll try to make another attempt next week. Of course, if someone else wants to fix it in the meantime, feel free to do so.

[nh2]

I'm also suffering from this problem. @kosmikus, are you still interested in working on it?

[snoyberg]

I just got bit by this too. (Thanks @23Skidoo for so quickly pointing out that it was a dupe.) However, I think the "solver" label is not correct: using runghc Setup.hs configure can trigger this behavior too.