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
on OSX 10.10.4, it fails building ide-backend-server-0.10.0:
-- While building package ide-backend-server-0.10.0 using:
/usr/local/bin/runhaskell -package=Cabal-1.22.2.0 -clear-package-db -global-package-db -package-db=/Users/asaelh/.stack/snapshots/x86_64-osx/nightly-2015-07-29/7.10.1/pkgdb/ /Users/asaelh/Tools/HTools/ide-backend/ide-backend-server/Setup.hs --builddir=.stack-work/dist/x86_64-osx/Cabal-1.22.2.0/ build
Process exited with code: ExitFailure 1
Logs have been written to: "/Users/asaelh/Tools/HTools/stack-ide/.stack-work/logs/ide-backend-server-0.10.0.log"
building rts...
Running cabal with ["build","--builddir=dist/buildinfo-3838620864207376993"]
Building ide-backend-rts-0.1.3.1...
Preprocessing library ide-backend-rts-0.1.3.1...
The build-tool has reset ENV. --env=std required.
The log file says:
building rts...
Running cabal with ["build","--builddir=dist/buildinfo-3838620864207376993"]
Building ide-backend-rts-0.1.3.1...
Preprocessing library ide-backend-rts-0.1.3.1...
The build-tool has reset ENV. --env=std required.
I'm still figuring out stack, but I was able to build ide-backend-rts using cabal. Running stack install in ide-backend gave this similar error:
Configuring ide-backend-rts-0.1.3.1...
building rts...
Running cabal with ["build","--builddir=dist/buildinfo-3838620864207376993"]
Building ide-backend-rts-0.1.3.1...
Preprocessing library ide-backend-rts-0.1.3.1...
The build-tool has reset ENV. --env=std required.
The text was updated successfully, but these errors were encountered:
While running the command from stack-ide:
on OSX 10.10.4, it fails building ide-backend-server-0.10.0:
The log file says:
I'm still figuring out stack, but I was able to build ide-backend-rts using cabal. Running stack install in ide-backend gave this similar error:
The text was updated successfully, but these errors were encountered: