-
Notifications
You must be signed in to change notification settings - Fork 710
bug: building dependencies with cabal "new-build" and profiling #3485
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
/cc @dcoutts |
Confirm that I can reproduce. |
Known facts:
Current hypothesis: Cabal 1.22 didn't know how to install profiling objects; Cabal 1.24 does know how, so we need to force a newer custom setup in this case. |
OK, hypothesis verified. Workaround: add |
OK this is a dupe of #3790 which diagnoses the problem more directly. |
Closing in favour of #3790, which has been now fixed. |
Edit @ezyang. Simplified the test case; you only need to depend on
bifunctors
or one of the Kmett packages. Seems to be related to custom setup.Compiling my project with profiling does not work. A test cabal file is pasted below. Running the following:
stops building dependencies half way through, and when I look at the log file
~/.cabal/logs/bifunctors-5.3.log
I see at the bottom:When I run the command again, it tries again to build the failed dependencies, and fails in the same way. Running plain
cabal new-build
works fine.Here is a complete test case. Run this as root on a fresh Ubuntu 14.04 install:
test.cabal
The text was updated successfully, but these errors were encountered: