From fd72f9e62a6fd71d750d3e2f09d404e1839441ba Mon Sep 17 00:00:00 2001
From: Googler <ilist@google.com>
Date: Fri, 4 Oct 2024 05:22:54 -0700
Subject: [PATCH] Fix rules_cc copybara

PiperOrigin-RevId: 682280542
Change-Id: Ie5f9dbc05f4d87dbe14b2392a21a23ef0c3ea9a4
---
 cc/toolchains/actions.bzl        | 2 +-
 cc/toolchains/impl/variables.bzl | 4 ++--
 cc/toolchains/tool.bzl           | 2 +-
 cc/toolchains/tool_map.bzl       | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/cc/toolchains/actions.bzl b/cc/toolchains/actions.bzl
index 78c1fc6..3193b7d 100644
--- a/cc/toolchains/actions.bzl
+++ b/cc/toolchains/actions.bzl
@@ -40,7 +40,7 @@ cc_action_type = rule(
 `cc_action_type` rules are used to associate arguments and tools together to
 perform a specific action. Bazel prescribes a set of known action types that are used to drive
 typical C/C++/ObjC actions like compiling, linking, and archiving. The set of well-known action
-types can be found in [//cc/toolchains/actions:BUILD](https://github.com/bazelbuild/rules_cc/tree/main/cc/toolchains/actions/BUILD).
+types can be found in [//third_party/bazel_rules/rules_cc/cc/toolchains/actions:BUILD](https://github.com/bazelbuild/rules_cc/tree/main/cc/toolchains/actions/BUILD).
 
 It's possible to create project-specific action types for use in toolchains. Be careful when
 doing this, because every toolchain that encounters the action will need to be configured to
diff --git a/cc/toolchains/impl/variables.bzl b/cc/toolchains/impl/variables.bzl
index aac945e..35cc84a 100644
--- a/cc/toolchains/impl/variables.bzl
+++ b/cc/toolchains/impl/variables.bzl
@@ -75,7 +75,7 @@ def cc_variable(name, type, **kwargs):
     it's not possible to declare custom variables.
 
     For a full list of available variables, see
-    [//cc/toolchains/varaibles:BUILD](https://github.com/bazelbuild/rules_cc/tree/main/cc/toolchains/variables/BUILD).
+    [//third_party/bazel_rules/rules_cc/cc/toolchains/varaibles:BUILD](https://github.com/bazelbuild/rules_cc/tree/main/cc/toolchains/variables/BUILD).
 
     Example:
     ```
@@ -91,7 +91,7 @@ def cc_variable(name, type, **kwargs):
     Args:
         name: (str) The name of the outer variable, and the rule.
         type: The type of the variable, constructed using `types` factory in
-            [//cc/toolchains/impl:variables.bzl](https://github.com/bazelbuild/rules_cc/tree/main/cc/toolchains/impl/variables.bzl).
+            [//third_party/bazel_rules/rules_cc/cc/toolchains/impl:variables.bzl](https://github.com/bazelbuild/rules_cc/tree/main/cc/toolchains/impl/variables.bzl).
         **kwargs: [common attributes](https://bazel.build/reference/be/common-definitions#common-attributes) that should be applied to this rule.
     """
     _cc_variable(name = name, type = json.encode(type), **kwargs)
diff --git a/cc/toolchains/tool.bzl b/cc/toolchains/tool.bzl
index a3536cf..9bef3b1 100644
--- a/cc/toolchains/tool.bzl
+++ b/cc/toolchains/tool.bzl
@@ -102,7 +102,7 @@ This can help work around errors like:
             providers = [ToolCapabilityInfo],
             doc = """Declares that a tool is capable of doing something.
 
-For example, `//cc/toolchains/capabilities:supports_pic`.
+For example, `//third_party/bazel_rules/rules_cc/cc/toolchains/capabilities:supports_pic`.
 """,
         ),
     },
diff --git a/cc/toolchains/tool_map.bzl b/cc/toolchains/tool_map.bzl
index b4f7e35..53866a8 100644
--- a/cc/toolchains/tool_map.bzl
+++ b/cc/toolchains/tool_map.bzl
@@ -75,7 +75,7 @@ def cc_tool_map(name, tools, **kwargs):
     `CXX=/path/to/clang++` environment variables that most build systems use to determine which
     tools to use for a given action. To simplify usage, some actions have been grouped together (for
     example,
-    [//cc/toolchains/actions:cpp_compile_actions](https://github.com/bazelbuild/rules_cc/tree/main/cc/toolchains/actions/BUILD)) to
+    [//third_party/bazel_rules/rules_cc/cc/toolchains/actions:cpp_compile_actions](https://github.com/bazelbuild/rules_cc/tree/main/cc/toolchains/actions/BUILD)) to
     logically express "all the C++ compile actions".
 
     In Bazel, there is a little more granularity to the mapping, so the mapping doesn't follow the