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
$ stack build
....
Process exited with code: ExitFailure 127
Logs have been written to: /home/netsu/.zsh/antigen-hs/.stack-work/logs/text-1.2.1.3.log
/home/netsu/.stack/setup-exe-cache/setup-Simple-Cabal-1.22.4.0-x86_64-linux-ghc-7.10.2: error while loading shared libraries: libgmp.so.10: cannot open shared object file: No such file or directory
This really comes from the fact that Stack fails to compile setup-Simple-Cabal-1.22.4.0-x86_64-linux-ghc-7.10.2 correctly with Nix:
I just encountered this on a client project. There, the error message was worse there for some reason, it did not even mention libgmp.so.10.
/home/username/.stack/setup-exe-cache/x86_64-linux/Cabal-simple_mPHDZzAJ_2.0.1.0_ghc-8.2.2: streamingProcess: runInteractiveProcess: exec: does not exist (No such file or directory)
@domenkozar I'm not sure if this is a stack issue, it is making a very straightforward invocation of ghc to build this. What should it do differently?
It took me a while to figure out why I was getting "does not exist" even when running the binary with bash. I think it would be nice to do the following:
When simple Setup or custom Setup get built, first sanity check them with --version.
If the sanity check fails, perhaps run ldd (if that exists), and check for "=> not found". If that is found in the output, then perhaps give the user some tips on resolving it.
It's a common error in Stack+Nix:
This really comes from the fact that Stack fails to compile
setup-Simple-Cabal-1.22.4.0-x86_64-linux-ghc-7.10.2
correctly with Nix:The text was updated successfully, but these errors were encountered: