-
Notifications
You must be signed in to change notification settings - Fork 100
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
ghc-mod and GHC 8.2.x #282
Comments
I haven't used |
Hmm, for me doing identifier completions and querying types under the cursor is really important. How about in the short term we go with your option 2? I'm also curious whether viable ghc-mod replacements exist. |
As a new user, this has been very frustrating. I had high hopes for this when I first came across it. Wish there was at least some kind of workaround mentioned in the docs because it is evident a lot of users are having this issue. |
Hi @bidhan-a, I am a bit strapped for OSS time at the moment. Would you be interested in submitting a PR for this? I would be happy to help guide you to the spots in the code we could change. As a start, in |
Hi @jship , I'd be glad to help out in any way I can since I'm really looking forward to making it work on my machine. As per your suggestion, I have modified the I have tested the modified script and the installer successfully moves past that point, but unfortunately it exits with another error after a while. The error looks similar to the one described in 278 and 270. Here's the complete log if it helps:
Any way I can get around this one? I have the latest version of Stack by the way. Thanks. |
Hi @jship , Still no luck. I'm getting a similar error even after merging #276 .
It seems the problem is with the "hscope" library this time. On a side note, I've included the following URL as a reference for the user in case they want to manually install ghc-mod. Thanks! |
Looks like the upper bound on GHC 8.2.2's bundled |
I'm getting the following error now, similar to the one described in #270 .
|
Hmm, what version of stack do you have? Can do a If it winds up that you have the latest stack, we may be able to get past this by changing this line to:
This would ensure we are not doing the dependency solving with cabal 2, which apparently stack is having some trouble with. I recommend first upgrading stack if needed and trying again before changing that line. |
I have the latest version of Stack (1.6.3) on my machine. I'll try the other option and let you know how it goes. |
Unfortunately, I'm getting the same error, except for the "Warning: Installed version of cabal-install (2.0.0.1) is newer than stack has been tested with. If you run into difficulties, consider downgrading." part. |
@bidhan-a: So you are no longer seeing Can you do a:
Based on #270 and #272, I'm wondering if there is some weirdness in your environment. Can you also do a:
Thank you for being so helpful on this! 👍 |
HI @jship , No problem at all. That's correct. I'm no longer seeing that particular warning. Here are the results:
Thanks. |
Hmm, the plot thickens then! I feel like the next steps would be to try it on a clean VM. Are you doing any cleanup in between runs? If you want, you can try doing the install on a clean VM. A "worst case" kind of workaround would be to explicitly install the helper binaries using a known compatible resolver until we can figure out something better. I think lts-7.24 was the last known one to work. In this case, we wouldn't even use |
Hi @jship , Yes, I've done cleanups between runs. I also tested it on another Ubuntu system and I got the same result. I have tested it on a VM using both Ubuntu and Fedora distros, but to no avail. Would you be able to point me in the right direction regarding how to get the workaround to work? I guess the "worst case" scenario will be good enough for people like me who just want to get this working, until there's a better solution. Thanks |
@bidhan-a, I merged your changes into my fork and was able to get the installer working with this additional (somewhat hacky) commit: jship@c05e841 Will open a PR with more detail. |
@jship , thanks a lot! The installer worked on my machine too. 😅 One extra thing that I did; since we're using lts-7.24 for the time being anyway, I used it to install ghc-mod as well. Thanks again. |
That's great news, @bidhan-a! 👍 Thanks for re-testing. I'll go ahead and merge that PR and close out this issue. |
Closed by #288. |
ghc-mod on 8.2.x has been broken for a while, but here recently looks like there is a workaround for getting it installed using
cabal-helper
. Some progress has been made too on adding official support.I could see this as pretty frustrating for new users of
haskell-vim-now
if theghc-mod
install blows up and the install fails. A few options:ghc-mod
. This could be a maintenance/support chore.ghc-mod
normally, but if it fails, don't stop the installer. Instead provide a link to instructions on troubleshooting the install of it.ghc-mod
as part ofhaskell-vim-now
's install. Instead just provide instructions.The text was updated successfully, but these errors were encountered: