-
Notifications
You must be signed in to change notification settings - Fork 92
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
Stack install failing on windows with unknown symbol
ucnv_getMaxCharSize_58'`
#56
Comments
I think the bug is because it is looking for the path in the wrong drive: D instead of C: |
I got the same issue and I just follow the same method of #41 to solve the problem in: |
I also hit this (unknown symbol `ucnv_getMaxCharSize_58'). Hopefully the Haskell on Windows experience improves over time. |
I heard you can use Windows Linux Subsystem + Nix / cabal2nix / stack2nix
to solve almost all of these problems.
…On Wed, Aug 30, 2017, 08:31 Oscar Vargas Torres ***@***.***> wrote:
I also hit this (unknown symbol `ucnv_getMaxCharSize_58'). Hopefully the
Haskell on Windows experience improves over time.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABrV9OuF_jMz626q-yrGvYSwxv9vFgMTks5sdQ-_gaJpZM4O8a8z>
.
|
WSL is not ready for haskell at the moment. Every time I try I hit a different bug. Last time I tried microsoft/WSL#1671 (comment), but didn't work for me. Therefore, the only thing that has worked for me has been to use a Linux guest in VirtualBox. At the moment I'm using Fedora 26, and it works prety good. However, Windows is a very important platform... I wish it wouldn't be that hard for Haskell development |
I know someone who is a very good Haskell programmer and he said he had no issues with using WSL with Nix. Not saying that this means anything though: it is just another data point. |
@razvan-panda Do you mind sharing a solution if you find any? Maybe your friend could give us some guidance :) |
I have my own things I need to work on but if I run into it I'll provide
the solution so others can benefit. I usually do that. I pinged my friend
about the ticket.
…On Wed, Aug 30, 2017 at 3:27 PM Oscar Vargas Torres < ***@***.***> wrote:
@razvan-panda <https://github.com/razvan-panda> Do you mind sharing a
solution if you find any? Maybe your friend could give us some guidance :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABrV9D9YSltYSOwn9_SK5BHodgqARC_Hks5sdXFfgaJpZM4O8a8z>
.
|
@alanz I'm happy to inform you that I have just successfully installed Haskell Language Server on Windows 10 pro (64 bits) version 1709. Please, keep going with this project! I'm pretty happy to have a modern development environment for Haskell on Windows with VS Code. |
Hitting the same issue. |
Are there any windows users who can help with this? |
The solution in this issue works for me (#41) but it required rebuilding text-icu and it also requires that the symlinked DLLs are somewhere in the PATH when the
|
I've created a pull request on the text-icu package the fixes this for me. With this change it's enough to install the icu library via pacman. This isn't a haskell-lsp issue but this issue is the first result for Perhaps someone can do something about getting this merged and maybe a new version pushed to Hackage? It's been 3 years and I feel that text-icu is a pretty integral package. |
I can not reproduce the error with:
So it seems the issue was fixed upstream. @LukaHorvat, feel free to reopen if you continue experiencing the issue. |
Environment:
When running
stack install
I first got the following error:To fix it I run:
stack exec -- pacman -Sy mingw64/mingw-w64-x86_64-icu
After that the build stopped on another error which seemed to have to do with stack building multiple things at same time.
On running again it passed by that error and it printed the following error:
Any suggestions on how to fix it?
StackOverflow reference: https://stackoverflow.com/q/45775326/750216
The text was updated successfully, but these errors were encountered: