-
Notifications
You must be signed in to change notification settings - Fork 695
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
Cabal: Take into account compilerBuildWay when computing final library ways #10419
Conversation
cb137bf
to
8db1301
Compare
Backportable to 3.14 but not 3.12. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great find. Thanks for the fix.
49dbb91
to
9eeb7bd
Compare
Does this need to be expedited? |
Yes, this needs to be backported to the 3.14 branch too. |
@mergify backport 3.14 |
✅ Backports have been created
|
…y ways In the profiling dynamic patch I made a mistake when computing the needed ways for a build. When building an executable, the Haskell modules need to be built * For the final link way * For the build way of the compiler if TH is enabled Before this patch, the modules were being built for all the configured library ways, which built modules in more configurations than the previous version of Cabal. Fixes haskell#10418
Figured that. It's embarked now. |
@Mergifyio backport 3.12 |
✅ Backports have been created
|
Repeating here: this can't be backported to 3.12 because it's a modification to #9900, which changed the |
@wz1000: just to clarify, in our cabal maintainers jargon "expedited" means "merged without waiting the normal 2 days for all interested devs to find time to review and discuss". I believe this patch did not need to be expedited and there was probably a miscommunication of expedited vs. backported. |
I understood it to be "yes, and…". I already knew it was destined for backporting since it's needed for 9.12.1. |
Cabal: Take into account compilerBuildWay when computing final library ways (backport #10419)
In the profiling dynamic patch I made a mistake when computing the needed ways for a build.
When building an executable, the Haskell modules need to be built
Before this patch, the modules were being built for all the configured library ways, which built modules in more configurations than the previous version of Cabal.
Fixes #10418
Please read Github PR Conventions and then fill in one of these two templates.
Template Α: This PR modifies behaviour or interface
Include the following checklist in your PR:
Template B: This PR does not modify behaviour or interface
E.g. the PR only touches documentation or tests, does refactorings, etc.
Include the following checklist in your PR: