-
Notifications
You must be signed in to change notification settings - Fork 709
"Dependency on unbuildable library" with three sublibraries #6470
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@chris-martin Have you found a workaround? I've also run into this. |
For some reason this only seems to happen when using the |
I cannot reproduce this with |
Hah, I was just about to suggest that after seeing the changes here! That's great! |
@phadej can this be closed or does it need regression tests? |
This looks like haskell/cabal#6470 which has (apparantly) been fixed for a while.
This looks like haskell/cabal#6470 which has (apparantly) been fixed for a while.
This looks like haskell/cabal#6470 which has (apparantly) been fixed for a while.
This looks like haskell/cabal#6470 which has (apparantly) been fixed for a while.
For a minimal reproduction of the problem, try using this
demo.cabal
file (no other files required):Cabal cannot build this project:
It seems to require three sublibraries to reproduce this issue - it is important both that
demo:a
depends ondemo:b
, and thatdemo:b
depends ondemo:c
. If we remove either of thosebuild-depends
lines, the package does build.The alternative or perhaps further issue here is that the error message does not explain why the
demo:b
library is unbuildable. But it seems rather suspicious that the presence ofdemo:a
depending ondemo:b
somehow causesdemo:b
to become unbuildable.The text was updated successfully, but these errors were encountered: