Ignore:
Timestamp:
06/30/2020 05:45:38 PM (16 months ago)
Author:
Ken Moffat <ken@…>
Branches:
10.0, 10.1, 11.0, ken/refactor-virt, lazarus, qt5new, trunk, xry111/git-date, xry111/git-date-for-trunk, xry111/git-date-test
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:
1 edited

Legend:

Unmodified
Added
Removed
  • introduction/important/building-notes.xml

    r693f28e1 r5ce1bdb  
    666666      </para>
    667667
     668      <para>
     669        The rust developers seem to assume that everyone will compile on a
     670        machine dedicated to producing builds, so by default all CPUs are used.
     671        This can often be worked around, either by exporting
     672        CARGO_BUILD_JOBS=&lt;N&gt; or passing --jobs &lt;N&gt; to cargo. For
     673        compiling rustc itself, specifying --jobs &lt;N&gt; on invocations of
     674        x.py (together with the <envar>CARGO_BUILD_JOBS</envar> environment
     675        variable, which looks like a "belt and braces" approach but seems to be
     676        necessary) mostly works. The exception is running the tests when building
     677        rustc, some of them will nevertheless use all online CPUs, at least as of
     678        rustc-1.42.0.
     679      </para>
     680
    668681  </sect2>
    669682
Note: See TracChangeset for help on using the changeset viewer.