pkgs/build-support/trivial-builders: remove runCommandCCLocal

We shouldn’t force the user to have a C compiler in scope, just
because the derivation is forced to build locally. That can’t be
counted as “lightweight” anymore.

Co-Authored-By: Silvan Mosberger<contact@infinisil.com>

1 files changed, 2 insertions, 2 deletions

diff --git a/doc/builders/trivial-builders.xml b/doc/builders/trivial-builders.xml
index d31c74e520f3..94948c57b91f 100644
--- a/doc/builders/trivial-builders.xml
+++ b/doc/builders/trivial-builders.xml
@@ -52,11 +52,11 @@
   </varlistentry>
   <varlistentry xml:id="trivial-builder-runCommandLocal">
    <term>
-    <literal>runCommandLocal</literal>, <literal>runCommandCCLocal</literal>
+    <literal>runCommandLocal</literal>
    </term>
    <listitem>
     <para>
-     Variants of <literal>runCommand</literal> and <literal>runCommandCC</literal> that force the derivation to be built locally, it is not substituted. This is intended for very cheap commands (&lt;1s execution time). It saves on the network roundrip and can speed up a build.
+     Variant of <literal>runCommand</literal> that forces the derivation to be built locally, it is not substituted. This is intended for very cheap commands (&lt;1s execution time). It saves on the network roundrip and can speed up a build.
     </para>
     <note><para>
       This sets <link xlink:href="https://nixos.org/nix/manual/#adv-attr-allowSubstitutes"><literal>allowSubstitutes</literal> to <literal>false</literal></link>, so only use <literal>runCommandLocal</literal> if you are certain the user will always have a builder for the <literal>system</literal> of the derivation. This should be true for most trivial use cases (e.g. just copying some files to a different location or adding symlinks), because there the <literal>system</literal> is usually the same as <literal>builtins.currentSystem</literal>.