-
Notifications
You must be signed in to change notification settings - Fork 711
Installing from separate folder with Custom build type fails #1058
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
Comments
I ran into this trying to install the clckwrks packages. It failed with obscure errors like this:
And then the build log mentioned in the output is an empty file. I can confirm that it installs fine if I |
@dcoutts You've been working on being able to |
Works for me:
@snoyberg Could you give me the complete log, including the versions of GHC and cabal please? |
Thanks for looking into this @tibbe. Here's the full log:
|
@snoyberg Very odd. I'm at a loss about what to do. Here's how configure is called in my case:
Could you try to install with |
I'm working towards a Cabal/cabal-install bug fix release this weekend and this is the last issue on the list of issues to fix, so if someone has some insight about what's going on here that would be great. |
Here's my output.
I noticed that in yours, the setup executable is compiled against Cabal-1.14.0, whereas in mine it's using Cabal-1.16.0.1. I tried unregistering Cabal-1.16.0.1 and starting over, but to no avail:
Then I tried to use the old
I'm doing some research myself, I'll put it in a separate comment. |
Fixed in 48082b9. |
@snoyberg Correct. |
@tibbe Could you have a look at http://hackage.haskell.org/trac/ghc/ticket/7327? It seems that Ian is having difficulty reproducing the difference in behavior, and since I've never actually run this code on Mac I can't help. |
@snoyberg Replied on the GHC Trac. Ian's example segfaults on my machine! |
This is a new issue with version 1.16 of
cabal-install
. Steps to reproduce:cabal unpack lifted-base-0.1.2
cabal install ./lifted-base-0.1.2
The problem is that when the
setup
executable is called, e.g.:it is not able to find the
cabal
file, as it is now in the current subfolder. A theoretical fix would be to change working directory before calling that script.The text was updated successfully, but these errors were encountered: