Don't strip DT_SONAME from the shared libobjc - #423
Merged
Conversation
davidchisnall
approved these changes
Sep 8, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The NO_SONAME property was introduced in 76a8831 (2014) as
set_property(TARGET PROPERTY NO_SONAME true)— with the target name missing, so it never applied to any target and libobjc has shipped with a DT_SONAME on every ELF platform ever since.#422 corrected the syntax while moving the shared library into
if (BUILD_SHARED_LIBOBJC), which activated the property for the first time. The resulting libobjc.so has noDT_SONAME, so any consumer linked against it by absolute path records that absolute build-time path in itsDT_NEEDEDand fails to load once installed elsewhere.NO_SONAMEalso contradicts theSOVERSIONset two lines above, so remove the line rather than the version.