Changeset 00032e41


Ignore:
Timestamp:
08/31/2021 12:03:02 AM (15 months ago)
Author:
Bruce Dubbs <bdubbs@…>
Branches:
11.0, 11.1, 11.2, lazarus, plabs/python-mods, qt5new, trunk, upgradedb, xry111/intltool, xry111/soup3, xry111/test-20220226
Children:
6fdd3ce
Parents:
4148484c
Message:

Tag qtwebengine and add a warning.
This is the largest BLFS package. It can overload system memory
if all cores are used. Add a warning about this.

Note: Build failed at about the 90% point on a system with 24 cores
and 32 GB of RAM + 2 GB of swap due to out-of-memory. The
solution is to limit cores with NINJAJOBS ir add RAM or swap space.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • x/lib/qtwebengine.xml

    r4148484c r00032e41  
    151151         end of note for editors -->
    152152
    153     &lfs101_checked;
    154 
    155     <note>
     153    &lfs110a_checked;
     154
     155    <warning>
    156156      <para>
    157157        By default, ninja will use all online CPUs +2 (if at least 4 exist),
    158158        even if they are not available to the current task because the build
    159         terminal has been restricted with 'taskset'.  To work around this, see
    160         the Command Explanations below.
    161       </para>
    162 
     159        terminal has been restricted with 'taskset'.  In BLFS, this package
     160        takes more time to build than than any other.  In one example,
     161        the build of this package crashed at about the 90 percent point
     162        due to an out of memory problem on a system with 24 cores and 32 GB
     163        of memory.
     164      </para>
     165
     166      <para>
     167        To work around this, see the Command Explanations below.
     168      </para>
     169    </warning>
     170
     171    <note>
    163172      <para>
    164173        Unusually, the shipped GN build system (used to create the Ninja files)
     
    489498            Reducing the number of cores being used on long running, CPU
    490499            intensive packages may alleviate heat problems.
     500          </para>
     501        </listitem>
     502        <listitem>
     503          <para>
     504            Reducing the number of cores will prevent potential out-of-memory
     505            problems on systems that do not have enough memory (or swap)
     506            when all cores are active.  A suggested approach is to limit
     507            the number of cores to about one core for each 1.5 GB of
     508            combined RAM and swap space.
    491509          </para>
    492510        </listitem>
Note: See TracChangeset for help on using the changeset viewer.