Skip to content

Binary coping with installed binaries #901

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

Closed
NightRa opened this issue Sep 2, 2015 · 1 comment
Closed

Binary coping with installed binaries #901

NightRa opened this issue Sep 2, 2015 · 1 comment

Comments

@NightRa
Copy link
Contributor

NightRa commented Sep 2, 2015

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:

hlint: Couldn't find file: HLint
Tried with:
  HLint
  HLint.hs
  D:\Users\NightRa\AppData\Roaming\stack\snapshots\i386-windows\lts-3.1\7.10.2\share\i386-windows-ghc-7.10.2\hlint-1.9.21\HLint
  D:\Users\NightRa\AppData\Roaming\stack\snapshots\i386-windows\lts-3.1\7.10.2\share\i386-windows-ghc-7.10.2\hlint-1.9.21\HLint.hs

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.

@snoyberg
Copy link
Contributor

snoyberg commented Sep 2, 2015

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.

@NightRa NightRa closed this as completed Sep 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants