[release/8.0-staging] Use clang --version to get Apple toolset version #100199
Conversation
This file contains 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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas |
This was referenced Mar 24, 2024
VSadov
approved these changes
Mar 24, 2024
jeffschwMSFT
approved these changes
Mar 25, 2024
agocke
approved these changes
Mar 25, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport of #100190 to release/8.0-staging
/cc @jkotas
Customer Impact
The
xcodebuildtool used to identify the Apple native toolset version is only available with full Xcode installation. It is not available in command line only installation of the Apple toolset used by some customers.The fix is to use
clangto identify the Apple native toolset version instead.Regression
Regression introduced by earlier .NET 8 servicing fix (#97856) that added workaround for an issue with latest Apple native toolset.
Testing
The fix was independently validated #100190 (review)
Risk
Low