Changeset 5ce1bdb for introduction/important

Timestamp:

06/30/2020 05:45:38 PM (4 years ago)

Author:

Ken Moffat <ken@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

eb7de89

Parents:

693f28e1

Message:

Rust: explain how to (mostly) restrict how many processors it wants to use.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@23349 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• introduction/important/building-notes.xml (modified) (1 diff)

introduction/important/building-notes.xml

@@ -666 +666 @@
       </para>
 
+      <para>
+        The rust developers seem to assume that everyone will compile on a
+        machine dedicated to producing builds, so by default all CPUs are used.
+        This can often be worked around, either by exporting
+        CARGO_BUILD_JOBS=&lt;N&gt; or passing --jobs &lt;N&gt; to cargo. For
+        compiling rustc itself, specifying --jobs &lt;N&gt; on invocations of
+        x.py (together with the <envar>CARGO_BUILD_JOBS</envar> environment
+        variable, which looks like a "belt and braces" approach but seems to be
+        necessary) mostly works. The exception is running the tests when building
+        rustc, some of them will nevertheless use all online CPUs, at least as of
+        rustc-1.42.0.
+      </para>
+
   </sect2>