-
Notifications
You must be signed in to change notification settings - Fork 208
Can't build on windows with a space in any of the used paths (stack,ghc,etc locations) #1356
Comments
Do we know which command failed specifically? E.g. does |
@fendor any
It probably doesn't matter but I'm using the integrated powershell terminal in vscode.
It needs a unix toolchain but I believe it is included with the Haskell platform. Here is the file: network-3.0.1.1-a7c0a2f72c1e0fc4564857678c584897c6b48964.log |
Sounds a bit like an issue upstream... |
Except it does not. |
I tried a minimal example on windows with a space in the path, it seems to work alright. So, this issue might indeed be caused by the install script. |
Windows 10 Pro x64 version 1903 (updated yesterday). |
Fyi, I did not clone the repository into my user folder, I cloned it into |
It was probably downloading ghc and building the install script. |
re: cabal error |
@ArthurHNL i would relocate all paths used by
local-bin-path: X:\bin
local-programs-path: X:\bin\stack Of course you can replace |
@ArthurHNL have you had the opportunity to try those changes in stak config? Imo that stack configuration is good in general to develop with stack in windows. |
@jneira I just tried the new configuration and it appears to be working :) |
Great! I think we could close this, having a good workaround and being at the end a upstream issue. |
Is it an upstream issue though? Did we confirm that? Could not find a stack issue. |
Mmm i've not reproduced it but given that changing stack config fixes it i think it would be so. |
Before trying to reproduce is, what is your stack version @ArthurHNL? EDIT: closed by accident |
Ok, i've reproduced it simply setting a path with spaces in
When you run a stack command instead a script it emits a warning:
The warning is a little bit weird in the suggestions but i think that makes clear that they are aware of the issue. The improvement could be show the message when running a script (like hie Filling an issue upstream... |
@jneira should I add a check into the |
mmm, it would be great at least while stack itself doesn't warn anything. |
@power-fungus i've just opened a pr upstream to make stack show the warning. We will have to wait to the next release but maybe we dont need add the message to hie. |
@jneira Awesome. The warning does make more sense coming from |
Since the upstream issue is closed, what do we aim to do here? Add to readme, or just close this issue? |
Not sure if we should wait to a stack release with the warning that hie could use |
I had the same issue because Stack was installed under C:\Program Files\ .. . Moving Stack to C:\bin\stack was not enough however. Had to also uninstall and reinstall the whole Haskell Platform to C:\Haskell\8.6.5 which was previously installed under C:\Program Files\Haskell Platform\8.6.5 . Before reinstalling the Haskell Platform the GHC 8.6.5 and stack based install failed with: |
On Windows, when trying to build (after cloning) using the following command:
Gives the following output:
I'm not really experienced with stack but it appears to be an issue with spaces in the path (my actual user folder is
C:\Users\Arthur Heidt
), the path appears to be cut off at the first space.The text was updated successfully, but these errors were encountered: