-
Notifications
You must be signed in to change notification settings - Fork 18
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
cabal-store-check: error in windows setting the compiler with -w ghc-${version}
#19
Comments
Thanks for the report. Unfortunately I'm not actively supporting these tools (as they work well enough for me). Especially, I won't investigate why something doesn't work. Windows is quite a mystery for me. For that reason I'm not actively advertising their existence either. |
Can not reproduce on win 10:
Only happens when this cabal-helper bug occurs? |
@fendor it works for |
Thanks, misread the issue! Can reproduce! |
I think this is either a problem with file extensions in let p = proc "ghc-8.6.5" ["--info"]
readCreateProcess p "" But this succeeds: let p = proc "ghc-8.6.5.exe" ["--info"]
readCreateProcess p "" Also, the following calls succeeds:
@jneira Maybe this is expected behaviour on windows? IIRC, the extension is important to windows. |
well |
We can easily introduce a work-around for it. I just think the behaviour is weird for |
As stated in #20 (comment), it seems the solution should be upstream (in the directory package). |
-w ghc-${version}
After a little more thinking, I'd like to have shell like search available in the library. I.e. On unix-like systems simulate:
and on windows whatever PowerShell does in: Get-Command ghc-8.6.5 (It might find Obviously not listing anything for aliases and functions (which both AFAIK handle). The use-case is to simulate how the shell finds the commands, as that what you kind of expect when you say I think that's reasonable feature to have in |
Hi, first of all thanks for these useful tools.
Trying to fix the cabal-helper build for ghc-8.4.4 (my default one is ghc-8.6.5) i've go this error:
I guess it should be relatd with windows
The full path works:
The text was updated successfully, but these errors were encountered: