-
Notifications
You must be signed in to change notification settings - Fork 844
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
Can't build reactive-banana-wx #2269
Comments
You have two different versions of Cabal installed:
What's the output for the following?
|
I know of 2 or 3 cabal installations on my system. I've tried doing |
Sorry, I meant the output for |
No problem, thanks for your help. Output below:
As a reminder (in case you have been thinking about things other than this ticket 😄 ), those are the two conflicting Cabal versions from the error message. I'm guessing that part of this is because I'm using |
Oh, I see. |
The bad news: I encountered this issue today and-- as a result-- I stumbled upon this unresolved issue. The good news: it appears as though I've found a solution. In short, it looks like, perhaps, something had changed in Cabal. The workaround is to simply add # Specifies the GHC version and set of packages available (e.g., lts-3.5, nightly-2015-09-21, ghc-7.10.2)
resolver: lts-5.0
# Local packages, usually specified by relative directory name
packages:
- '.'
# Packages to be pulled from upstream that are not in the resolver (e.g., acme-missiles-0.3)
extra-deps:
- Cabal-1.22.5.0
- cabal-macosx-0.2.3.4
- reactive-banana-1.1.0.1
- reactive-banana-wx-1.1.1.0
- wx-0.92.2.0
- wxcore-0.92.2.0
- wxc-0.92.2.0
- wxdirect-0.92.2.0
explicit-setup-deps:
"reactive-banana-wx": true Now we have a happy reactive 🍌 setup (well, at least it compiles ;)). Good luck! |
Glad it's resolved for you! This issue should also be fixed in stack >= 1.1.2 Are you on an older version? |
@mgsloan good catch. I'm on 1.0.2 :x I don't update my work laptop stack often enough. 👍 |
I am using stack
|
I think this issue got closed by mistake. Apparently this issue is supposed to be fixed in the latest version of stack, but I have the latest version of stack and am still having this issue (I created this ticket). I have been using stack |
@DevJac Perhaps it is a cabal regression, then. Can you please paste the |
@DevJac Oh, sorry, I thought @DeathByTape opened the issue. NVM I see it is in your original log:
Note there is indeed a single Cabal dep, Basically, |
|
Steps to reproduce:
stack new test simple
cd
to the newtest
directoryAdd
reactive-banana-wx
to yourbuild-depends
intest.cabal
Run
stack solver --update-config
Add the following to your
stack.yaml
file (as described in issue cabal-macosx module not found when building #1316):Run
stack build
in thetest
director created in step 1.When I do this, I get the following output and error:
The text was updated successfully, but these errors were encountered: