correct macOS Tahoe 26 build via apple_support #4500
Merged
Conversation
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
All of rules_go tests were failing on macOS Tahoe 26 due to `missing LC_UUID load command` in the clang binary built and in other tools. Many tools from Go to bazel itself have had to drop various workarounds for these kinds of linker problems in the run-up to macOS Tahoe (see bazelbuild/apple_support@44c43c715a and bazelbuild/bazel#27014) To fix this, we bump the version of build_bazel_apple_support (a.k.a. apple_support in Bazel Central Registry) to 1.24.3 in WORKSPACE. We also have to move the build_bazel_apple_support dependency above the llvm_toolchain call in order to make sure that version is actually used. It's possible we should also upgrade the llvm_toolchain to something more modern to handle some of our deps problems. The current llvm used by rules_go is 8.0.0 and is from 2019. The latest llvm version that toolchains_llvm supports in its latest release 1.5.0 is llvm 21.1.0. Fixes bazel-contrib#4499
jmhodges
force-pushed
the
correct-macos-tahoe-26-build
branch
from
1bd20b3 to
401be24
Compare
fmeum
approved these changes
Nov 4, 2025
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.
What type of PR is this?
Bug fix
What does this PR do? Why is it needed?
All of rules_go tests were failing on macOS Tahoe 26 due to
missing LC_UUID load commandin the clang binary built and in other tools. Manytools from Go to bazel itself have had to drop various workarounds for
these kinds of linker problems in the run-up to macOS Tahoe (see
bazelbuild/apple_support@44c43c715a and
bazelbuild/bazel#27014)
To fix this, we bump the version of build_bazel_apple_support (a.k.a.
apple_support in Bazel Central Registry) to 1.24.3 in WORKSPACE. We also
have to move the build_bazel_apple_support dependency above the
llvm_toolchain call in order to make sure that version is actually used.
It's possible we should also upgrade the llvm_toolchain to something
more modern to handle some of our deps problems. The current llvm used
by rules_go is 8.0.0 and is from 2019. The latest llvm version that
toolchains_llvm supports in its latest release 1.5.0 is llvm 21.1.0.
Which issues(s) does this PR fix?
Fixes #4499