Closed tomsmalley closed 7 years ago
Thanks for the report!
My guess is that something broke due to the changes to add implicit custom snapshots (more package sharing). Since GHC and GHCJS work very similarly, I suspected that it was just invoking ghc-pkg instead of using ghcjs-pkg, or using GHC_PACKAGE_PATH instead of GHCJS_PACKAGE_PATH.
Indeed, searching GHC_PACKAGE_PATH revealed a spot that the implicit snapshots change added a use of it without checking which compiler you're using. I've pushed a fix to that to master. Can you please check if this resolves the issue?
Pinging @tomsmalley , does updating to the master version of stack resolve this?
Looks to be working, thanks!
I'm getting very temperamental builds with the master branch, this wasn't happening in stack 1.4.0 (hence reporting here). The first build seems to work perfectly, but as soon as there is any change in the stack.yaml/snapshot file (e.g. removing an empty line) I'm getting errors like:
This happens both with custom snapshots and the normal resolvers.
stack clean --full
doesn't help, I've only found completely cleaning~/.stack
(hence having to reboot ghcjs, taking around 2 hours) allows a build to work.stack.yaml
:snapshot.yaml
:Note: The build I am using is actually from 20dc5ef04df20171e8f7b21303bed4e00873223f (relative path snapshots) but this also happens on 455c79fb7ba2c8880f284091f164decdd93e825b when using absolute snapshot path (or no custom snapshot).