output-complete-obj: link runtime C libraries when building shared libraries #1664
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.
Thus PR is an offspring of #1351 : currently, when building a shared library with
-output-obj
or-output-complete-obj
:the only difference between
-output-obj
andoutput-complete-obj
is that-output-complete-obj
does not link the C libraries used by the runtime by default. The fact that thecomplete
variant links less objects than the simple variant is not intuitive at all — as illustrated by the discussion in #1351 .Moreover, @whitequark confirmed that this behavior was not really intended and was inherited from the static linking mode.
Consequently, this small PR proposes to align the behavior of
-output-complete-obj
to the behavior ofoutput-obj
and link these runtime C libraries in the shared library mode.