[Bazel CI] CcMesonMakeRule Fails with Linker Error, Build Fails

[sgowroji]

CI: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/4026#01910c40-d7fb-4158-b4cb-8bf56fa9423d

Platform: MacOS

Logs:

ERROR: �[0m/private/var/tmp/_bazel_buildkite/4dbdaa322633a6e7887d5b601b0cf2f5/external/libffi/BUILD.bazel:10:6: Foreign Cc - Meson: Building libffi failed: (Exit 1): bash failed: error executing CcMesonMakeRule command (from target @@libffi//:libffi) 
ERROR: Unable to detect linker for compiler `/private/var/tmp/_bazel_buildkite/4dbdaa322633a6e7887d5b601b0cf2f5/execroot/rules_foreign_cc_examples/external/local_config_apple_cc/wrapped_clang -Wl,--version -lc++ -Wl,-oso_prefix,__BAZEL_EXECUTION_ROOT__/ -headerpad_max_install_names -no-canonical-prefixes -target x86_64-apple-macosx14.2 -fobjc-link-runtime -Xlinker -no_deduplicate -framework Foundation -Wl,-no_warn_duplicate_libraries`
error: linker command failed with exit code 1 (use -v to see invocation)
ERROR: �[0m/private/var/tmp/_bazel_buildkite/4dbdaa322633a6e7887d5b601b0cf2f5/external/rules_foreign_cc_examples_third_party/glib/BUILD:10:11 Executing genrule @@rules_foreign_cc_examples_third_party//glib:glib_build_test_0__deps failed: (Exit 1): bash failed: error executing CcMesonMakeRule command (from target @@libffi//:libffi) 
ERROR: �[0mBuild did NOT complete successfully
Error: The command exited with status 1�[0m
error: exit status 1

Culprit:

Steps:

git clone https://github.com/bazelbuild/rules_foreign_cc
git reset 9d5727d5e51bf1be8423dff7996bdb4d847b47e6  --hard
export USE_BAZEL_VERSION=a7264d99e2d14463cb683a4091d5ad0e08431205
bazel build -- //... //:third_party_examples_macos_tests -//cmake_android/... -@rules_foreign_cc_examples_third_party//curl:curl_test -@rules_foreign_cc_examples_third_party//openssl:openssl_test 

CC Greenteam @fweikert

[jsharpe]

This is due to the upgrade of the macOS workers - this was reported here: bazelbuild/continuous-integration#1981 (comment)
Its unclear what the correct fix is here, I don't have time to investigate the proper fix to this at this time.

[jsharpe]

@sgowroji this should hopefully now be fixed

[sgowroji]

Thanks for working on this!