-
Notifications
You must be signed in to change notification settings - Fork 843
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
Parallel builds don't work: Cabal (library) bug on configure? #84
Comments
Initial hack done, deferring to later milestone. |
This now appears to be occurring on Linux as well |
I suspect that this is a bug in the Cabal library. However, b511d70 introduces a resilient workaround. I'm going to move this to a later milestone for now, but may end up closing it completely. |
The workaround is working reliably, and is documented as a hack in the codebase. Closing the issue, we can always research further in the future if desired. |
So something to do with configuring indeed has a global dependency. Good to know... |
I bet if we crawled through the cabal-install code base long enough we'd find that they'd implemented the same hack somewhere. |
It seems that, after eight years, something may have happened somewhere to cure the original problem that the workaround fixed. See #6361. |
When I have parallel builds on, the
runhaskell Setup.hs build
steps will sporadically fail about "need to configure", but if I set the number of Shake flags to 1, it works. We may want to conditionally set threads to 1 on Windows for an initial release, and then debug what's happening.The text was updated successfully, but these errors were encountered: