[8.5.0] Remove xcode_locator's no_uuid and codesigning workarounds#27089
Merged
meteorcloudy merged 1 commit intobazelbuild:release-8.5.0from Sep 26, 2025
Merged
[8.5.0] Remove xcode_locator's no_uuid and codesigning workarounds#27089meteorcloudy merged 1 commit intobazelbuild:release-8.5.0from
meteorcloudy merged 1 commit intobazelbuild:release-8.5.0from
Conversation
These workarounds were added (in 76b3c24, bazelbuild#14168) to enable hermetic macOS toolchain setup, but are no longer necessary as far as I can tell (see also: bazelbuild/apple_support@44c43c715a, bazelbuild/apple_support#373). It should be noted that macOS Tahoe seems to have enforced that LC_UUID must be present in executables. Executables without it are rejected by dyld with `dyld: missing LC_UUID load command`, effectively stops Bazel from working. It is therefore necessary to drop these workarounds here and in Apple support (done in bazelbuild/apple_support@44c43c715a) in order for Bazel to function on macOS Tahoe. CC @keith Closes bazelbuild#27014. PiperOrigin-RevId: 811436317 Change-Id: I9d819fdbc2b76ad4ee5abb1fc0c4eb1ee1b442fb
meteorcloudy
approved these changes
Sep 26, 2025
Merged
via the queue into
bazelbuild:release-8.5.0
with commit Sep 26, 2025
e4eada5
47 checks passed
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
3 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.
These workarounds were added (in 76b3c24, #14168) to enable hermetic macOS toolchain setup, but are no longer necessary as far as I can tell (see also: bazelbuild/apple_support@44c43c715a, bazelbuild/apple_support#373).
It should be noted that macOS Tahoe seems to have enforced that LC_UUID must be present in executables. Executables without it are rejected by dyld with
dyld: missing LC_UUID load command, effectively stops Bazel from working. It is therefore necessary to drop these workarounds here and in Apple support (done in bazelbuild/apple_support@44c43c715a) in order for Bazel to function on macOS Tahoe.CC @keith
Closes #27014.
PiperOrigin-RevId: 811436317
Change-Id: I9d819fdbc2b76ad4ee5abb1fc0c4eb1ee1b442fb
Commit 433e0e7