From 5b01512e94e82bf111df3968784c9508e576a4da Mon Sep 17 00:00:00 2001 From: Derek Mauro Date: Thu, 8 Sep 2022 13:26:39 -0700 Subject: Add a case to detect when the Bazel compiler string is explicitly set to "gcc", instead of just detecting Bazel's default "compiler" string. When Bazel auto-configures GCC, it sets the compiler string to "compiler", probably for backwards compatibility. Some users manually set the string to "gcc". This should address the backwards compatibility issues described in https://github.com/bazelbuild/bazel/issues/12707 and hopefully fix https://github.com/abseil/abseil-cpp/issues/1263 PiperOrigin-RevId: 473069817 Change-Id: I8a24721f63f9d61447b22b3b05b06a9dde7d34d8 --- absl/BUILD.bazel | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'absl/BUILD.bazel') diff --git a/absl/BUILD.bazel b/absl/BUILD.bazel index 7cccbbba..29963ccc 100644 --- a/absl/BUILD.bazel +++ b/absl/BUILD.bazel @@ -27,6 +27,14 @@ config_setting( visibility = [":__subpackages__"], ) +config_setting( + name = "gcc_compiler", + flag_values = { + "@bazel_tools//tools/cpp:compiler": "gcc", + }, + visibility = [":__subpackages__"], +) + config_setting( name = "msvc_compiler", flag_values = { -- cgit v1.2.3