-
Notifications
You must be signed in to change notification settings - Fork 138
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
Lookup.hs build failure #420
Comments
Is ghc-7.10.1.20150715 the actual 7.10.1 release or a release candidate for 7.10.2? LH should build without issue against the official 7.10.1 release :( Sent from my iPhone
|
It's the 7.10.1 From the Herbert V. Riedell GHC PPA: https://launchpad.net/~hvr/+archive/ubuntu/ghc ghc --version lists:
but the binary is installed as 7.10.2. I'll See about getting a different version and let you know how it goes. |
I just downgraded to the actual 7.10.1, and it now compiles. |
Thanks. I looked into it and 7.10.2 has a small API change that we'll need to account for when it comes out. |
+1 I am new to Haskell and have no idea how to downgrade my GHC, been fruitlessly struggling with it for one hour. They don't bother making GHC pkgs for OS X anymore, as you're simply supposed to use the latest Haskell bundle. The make file conflicts with the Library convention that is normally used so it appears to be extremely inconvenient to install them in parallel. So yeah this breaks liquidhaskell for me right now. |
Also can you try to install "stack" and then do "stack install" ?
|
It installed ghc to |
I think the main problem is that stack does not recognise ghc version differences that small. "ghc-7.10" is the smallest possible resolver it accepts. It doesn't really give me a good impression that the ghc maintainers think back compatibility breaking changes only deserve a build/revision increment. You can clearly see the change here: https://downloads.haskell.org/~ghc/7.10.2/docs/html/libraries/ghc-7.10.2/TcRnDriver.html |
The GHC developers take API compatibility very seriously, generally refusing to change APIs in minor releases. In this case there was a feature (the implicit call-stacks) that multiple people asked to have back-ported to 7.10.2 that caused the API change. GHC HQ compiled all of stackage against the change before consenting to the back-port and found only a single package that was affected. So they decided in this case that the benefits outweighed the cost of fixing a few packages. I'll have a patch for LH and 7.10.2 on Monday, sorry for the inconvenience! Sent from my iPhone
|
Ah, very interesting. Thanks for the insightful response. |
Thanks a ton Eric!
|
LH should now compile against 7.10.2 as of 949d52a, but not against 7.10.1. This is because 7.10.2 includes some changes in the desugarer and using @ranjitjhala if you and/or Ben can put together a few notes about the work you've been doing with fixpoint in its |
Eric, the stuff Ben and I are doing is NOT in fixpoint master so should On Tue, Aug 11, 2015 at 4:59 AM, Eric Seidel [email protected]
Ranjit. |
The --native flag and a bunch of changes to the SmtLib2 module are in master. Is that stuff not ready to be mentioned in the Readme/Changelog? Sent from my iPhone
|
Yes not ready -- probably there by mistake...
|
@ranjitjhala here are all the commits in fixpoint's master since the last release, FYI ucsd-progsys/liquid-fixpoint@liquid-fixpoint-0.3.0.1...master#diff-d434977ac1a410b490aedf45f2ee7598 |
Ah ok thanks! So here's the deal: all the stuff actually belongs in cut solver but we've been pulling into master periodically to make sure we don't drift too far. But none of the changes are really "user facing" hence I thought no need to put anything into changes.md Does that make sense?
|
While trying to rebuild
liquid
I get the following error while compilingsrc/Language/Haskell/Liquid/Bare/Lookup.hs
:versions:
cabal: 1.22.4.0
ghc: 7.10.1.20150715
kernel: 3.19.0-21-generic x64
branch: master
commit: 8ae41ba
The text was updated successfully, but these errors were encountered: