-
Notifications
You must be signed in to change notification settings - Fork 841
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
GHCJS build worked only once and then stack simply stopped doing anything in consecutive builds #3665
Comments
Unfortunately, I ran into an issue with using Cabal-2.0 along with this build - haskell/cabal#4137 (comment) - and don't currently feel like putting much more time into reproducing it. One thing to try varying is your node version. Sometimes that can be a source of non reproducibility of ghcjs builds. It would be nice to have stack manage this - #1632 - but that's not currently implemented. It's hard to figure out what all the different behaviors are on different node versions. node 6.10.0 is what I have and that seems to work pretty well. Even trickier is that sometimes node version actually affects compilation results, and so you don't actually see the problems get fixed unless the stuff is rebuilt. |
I've tried many node versions, but it did not fix my issue. I'm starting to think my |
Sorry that didn't work out, I hope you figure it out soon! I know that getting this stuff working can be frustrating. It was even harder before stack setup. Note that ghcjs puts some of its packages in |
@mgsloan I've found the culprit 😄 . I used a single Cabal file, with two executables (frontend and backend). The file was like this:
I had this setup from a tutorial I was following, but it simply didn't work this way. I split it up into two Cabal files (one for frontend and one for backend) and it started working. I knew I was doing something wrong 😅 . |
General summary/comments
I'm using a backend/frontend structure using GHCJS and GHC. There are 2 directories
backend
andfrontend
with each their ownstack.yaml
. I managed to compile the frontend only once, and any consecutive commands tostack
simply stopped giving any output.Steps to reproduce
I am not sure what produces this issue. The install command worked once, but after that it simply stopped working. But here is my cabal and stack file:
And then I run
Expected
I expect there to be a build and a copy of the jsexe to my
.stack-work
bin directoryActual
What actually happens is nothing... When I run it in verbose mode:
Stack version
Method of installation
I installed stack using brew, and its the latest version right now.
The text was updated successfully, but these errors were encountered: