[build] Fix macOS-cross build #5951
Conversation
This broke with the Bazel 9 update. Drive-by: Clean up coverage configuration – we don't use remote execution so no need to set strategy, put -mllvm option on the same line as following option – this is easier to read since -mllvm can't be used as a standalone option. Also, avoid using settings intended for CI in local coverage builds.
|
I confirmed locally that this fixes builds that use |
|
Why do we even support intel macs anymore? |
Except for hiccups like this, the opportunity cost is low – it's trivial to cross-compile with the existing support in Xcode and Bazel. There also seem to be people fond of older OS versions/devices which likely includes Intel devices, recently someone asked about having support for macOS 11 (released 2020, EOL since 2023, we dropped support in 2024). I think we should support Intel Mac for as long as there is OS support for it – the current macOS 26 will be the last release with Intel support, so it might be another 2.5 years unless something makes it more difficult to maintain support. |
3 participants
This broke with the Bazel 9 update.
Drive-by: Clean up coverage configuration – we don't use remote execution so no need to set strategy, put -mllvm option on the same line as following option – this is easier to read since -mllvm can't be used as a standalone option. Also, avoid using settings intended for CI in local coverage builds.