[fix] Do not add symbol table in ar utility#2149
Open
danpashin wants to merge 1 commit intojordansissel:mainfrom
Open
[fix] Do not add symbol table in ar utility#2149danpashin wants to merge 1 commit intojordansissel:mainfrom
danpashin wants to merge 1 commit intojordansissel:mainfrom
Conversation
Xcode 26.4 and later enabled symbol table generation by default, this causes ar to ignore all non-macho files leaving only SYMDEF entry and results in corrupted archive.
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
1 participant
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.
Description
Xcode 26.4 and later enabled symbol table generation by default. This behavior causes ar to ignore all non-macho files leaving only SYMDEF entry and results in corrupted archive.
Compatibility
-S flag is already included in all ar impls: bsd (FreeBSD 13.5), llvm-ar (FreeBSD 15.0), gnu (ArchLinux, Ubuntu 16.04), Apple (MacOS 10.10) so this change is fully backward-compatible will all these tools and should not cause any undesirable behavior.
Closes #2148