-
Notifications
You must be signed in to change notification settings - Fork 245
all library components that use backpack should be compiled with -j1 #245
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
Of course, users can override this pretty easily on a per-package basis, but it would be nice if they didn't have to; especially since this would affect pre-built caches of hackage due to avoidable build failures. |
I completely missed this issue. Let's try to fix it with #244 together. |
Thank you! |
I wrote https://gitlab.haskell.org/ghc/ghc/merge_requests/1823 which allows |
@Ericson2314 I'll have to try that out! That's great! |
Knock on wood, but I think https://gitlab.haskell.org/ghc/ghc/merge_requests/1823 will finally be merged soon. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
GHC cannot perform typechecking on "backpackified" code in parallel. All components affected must be built with -j1. Cabal seems smart enough to infer this and does the right thing (inserts -j1), but both haskell.nix and nixpkgs pass the same number to -j (i think $NIX_BUILD_CORES?), which causes a build-time failure (GHC sees -jN where N > 1 and aborts with an error message).
The text was updated successfully, but these errors were encountered: