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'm on master 7153be8.
If I install a program via stack, for example, stack install hlint, hlint works well and everything.
But if I then delete the stack directory with all the snapshots, running hlint results in the following:
I think this has to do with the binary sharing that was introduced recently.
(Maybe the installed binary of hlint included references to other cached binaries?)
Installing via stack should create standalone binaries, independant of the state stack is in.
The text was updated successfully, but these errors were encountered:
Nope, this is nothing new, and has always worked this way. See #848 and previous linked discussions, the only way around this with Cabal is double-building.
I'm on master 7153be8.
If I install a program via stack, for example,
stack install hlint
, hlint works well and everything.But if I then delete the stack directory with all the snapshots, running
hlint
results in the following:I think this has to do with the binary sharing that was introduced recently.
(Maybe the installed binary of hlint included references to other cached binaries?)
Installing via stack should create standalone binaries, independant of the state stack is in.
The text was updated successfully, but these errors were encountered: