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
I just tried doing stack upgrade --git from stack 0.1.3.1. It gave the following error:
GHC version mismatched, found 7.10.1 (x86_64), but expected version 7.10.2 (x86_64) (based on
resolver setting in /var/folders/gx/7lt1gq996118d06q7g9ft7dd080grz/T/stack-upgrade1676/stack/stack.yaml).
Try running stack setup
It should probably run stack setup if you don't have the correct GHC installed.
On a side note, why doesn't stack build/install/test/etc automatically download the correct GHC for you anymore? One of the really cool things about stack was you literally run one command to get going and stack handles everything for you. The existence of stack setup seems to complicate this and leads to situations like above.
The text was updated successfully, but these errors were encountered:
Stack has recently become more precise about requiring an (nearly) exact GHC version match with the LTS snapshot (see #736), and since stack uses LTS 3.0 and LTS 3.0 requires GHC 7.10.2, you need GHC 7.10.2 to build stack.
It's been quite a while since stack installed GHC without stack setup. We changed the behaviour early on because the current behaviour seems to be preferred by most users. You can use the install-ghc option to change it if you prefer.
That said, I could see automatically installing the required GHC for the case of stack upgrade making sense. A pull request would be welcome.
I just tried doing
stack upgrade --git
from stack 0.1.3.1. It gave the following error:It should probably run
stack setup
if you don't have the correct GHC installed.On a side note, why doesn't stack build/install/test/etc automatically download the correct GHC for you anymore? One of the really cool things about stack was you literally run one command to get going and stack handles everything for you. The existence of
stack setup
seems to complicate this and leads to situations like above.The text was updated successfully, but these errors were encountered: