docs: Explain how to build only .dyn_o. #10984
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We struggled for a while at ZuriHac 2025 to figure out
why Cabal kept adding `-static -dynamic-too` to GHC flags,
even when the GHC is built dynamic-by-default
(`ghc --info` outputs `("GHC Dynamic","YES")`).
The docs so far,
``--enable-shared`` is enabled automatically if GHC is dynamically linked or
you request to build dynamic executables.
did not explain it sufficiently.
It is beacause of this code:
wantedLibWays is_indef =
<> [StaticWay | withVanillaLib lbi || withStaticLib lbi]
This commit clarifies the docs.
|
Screenshot of the docs generated:
and for the commands:
|
philderbeast
approved these changes
Jun 11, 2025
geekosaur
approved these changes
Jun 11, 2025
|
Indeed, the default is to build vanilla libraries, and if you have a dynamically linked compiler that implies dynamic libraries as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We struggled for a while at ZuriHac 2025 to figure out why Cabal kept adding
-static -dynamic-tooto GHC flags, even when the GHC is built dynamic-by-default(
ghc --infooutputs("GHC Dynamic","YES")).The docs so far,
did not explain it sufficiently.
It is beacause of this code:
This commit clarifies the docs.
Please read Github PR Conventions and then fill in one of these two templates.
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: