-
Notifications
You must be signed in to change notification settings - Fork 208
cabal-helper build fails #372
Comments
What operating system are you on? |
I got a similar error these last few days.
I resolved this by using lts-9.14.
|
@Nostradamos can you try building now and confirm that the issue is fixed? |
I also had issues with installing using
I got around this by running |
It isn't normally required. But our circleci.yml uses a different approach due to caching needs. Maybe @alanz could test a clean build with instructions from Readme and see if the problem can be reproduced. Also, @juho-p, what does |
|
What I have found is that stack does not always deal gracefully with git-style dependencies and sub-projects. So if my build goes funny like that, I will first do $ find . -iname ".stack-work" | xargs rm -fr From the main project directory |
I've also run |
You need to do the recursive one. Each subproject has a .stack-work too |
Indeed. |
|
Hi,
|
It is a bad sign that cabal-helper wants to run cabal. Generally, I find that cabal-helper and ghc-mod are messy and fragile, but that's another topic. You might have success doing
To install the |
The question is how we fix that once and for all. Is there anything we can do to improve dependency management in |
I'm pretty sure that one of the things cabal-helper is supposed to do is to make sure that an appropriate version of cabal is available. Ping @DanielG |
@mgsloan it is perfectly alright for cabal-helper do want to run I guess we could just depend on some http library and download package tarballs directly instead of depending on |
Is it possible to ensure that See haskell/cabal#220 Also I wonder if just adding At the very least we could document that |
The dependency on the |
|
I've tried using |
@alanz The upstream problem is closed now. Is hie updated to use the fixed cabal-helper? |
There is now a new release of cabal-helper (0.8.0.0) but which has a bug, fixed in current master. I am doing some final testing of the ghc-mod side of it at the moment, then will be able to push something. |
Cloned latest commit (6f46f1a)
but
stack install
fails on this error:The text was updated successfully, but these errors were encountered: