You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Choose to also install cabal, stack and hls
error appears in the MinGW x 64 windows
Welcome to Haskell!
This script can download and install the following binaries:
* ghcup - The Haskell toolchain installer
* ghc - The Glasgow Haskell Compiler
* cabal - The Cabal build tool for managing Haskell software
* stack - A cross-platform program for developing Haskell projects (similar to cabal)
* hls - (optional) A language server for developers to integrate with their editor/IDE
ghcup installs only into the following directory,
which can be removed anytime:
C:\ghcup
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 43.2M 100 43.2M 0 0 21.8M 0 0:00:01 0:00:01 --:--:-- 21.8M
[ Info ] verifying digest of: gs.exe
[ Info ] Upgrading GHCup...
[ Info ] downloading: https://downloads.haskell.org/~ghcup/0.1.19.0/x86_64-mingw64-ghcup-0.1.19.0.e
xe as file C:/ghcup\tmp\ghcup-b7c40b6512f093ad\ghcup.exe
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 86.1M 100 86.1M 0 0 16.9M 0 0:00:05 0:00:05 --:--:-- 17.3M
[ Info ] verifying digest of: ghcup.exe
[ Warn ] ghcup.exe is not in PATH! You have to add it in order to use ghcup.
[ Info ] Successfully upgraded GHCup to version 0.1.19.0
"_eghcup --cache install ghc recommended" failed!
cat: 'https'$'\357\200\272''/www.haskell.org/ghcup/sh/bootstrap-haskell': No such file or directory
Might be related to #745 ? Although I already downloaded ghc manually and added the path which didn't fix that issue.
The text was updated successfully, but these errors were encountered:
Choose to also install cabal, stack and hls
error appears in the MinGW x 64 windows
Might be related to #745 ? Although I already downloaded ghc manually and added the path which didn't fix that issue.
The text was updated successfully, but these errors were encountered: