Changeset 5c7f2497
- Timestamp:
- 02/19/2019 06:16:11 AM (6 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 12.2, 8.4, 9.0, 9.1, gimp3, 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/for-12.3, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/spidermonkey128, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 0891321
- Parents:
- 6dd3533
- Files:
-
- 3 edited
- 1 moved
Legend:
- Unmodified
- Added
- Removed
-
general/prog/prog.xml
r6dd3533 r5c7f2497 47 47 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="mercurial.xml"/> 48 48 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="nasm.xml"/> 49 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="ninja.xml"/>49 <!-- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="ninja.xml"/> --> 50 50 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="npapi-sdk.xml"/> 51 51 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="perl-modules.xml"/> -
networking/netutils/nmap.xml
r6dd3533 r5c7f2497 34 34 TCP/IP fingerprinting.</para> 35 35 36 &lfs8 3_checked;36 &lfs84_checked; 37 37 38 38 <bridgehead renderas="sect3">Package Information</bridgehead> -
x/lib/qtwebengine.xml
r6dd3533 r5c7f2497 245 245 <option>NINJAJOBS=4 make</option>: If you patched system ninja in LFS to 246 246 recognize the NINJAJOBS environment variable, this command will run system 247 ninja with the specified number of jobs (i.e. 4). Among the reasons why 248 you might want to do this are: building on a subset of CPUs, either to 249 measure the build time for that number of processors or to run other 250 CPU-intensive tasks on other cores, or to improve the build speed on a 251 less-well endowed 4-core machine. On a machine with a powerful CPU and 252 plenty of RAM, running N+2 jobs (the ninja default for 4+ cores) for the 253 large working sets of the C++ compiles in this package is typically only 254 marginally faster than running N jobs at a time. But for a machine with 255 less memory it can be much slower. 256 </para> 247 ninja with the specified number of jobs (i.e. 4). 248 There are several reasons why you might want to do this:</para> 249 250 <itemizedlist> 251 <listitem> 252 <para> Building on a subset of CPUs allows measuring the build time 253 for that number of processors or to run other CPU-intensive tasks on 254 other cores.</para> 255 </listitem> 256 <listitem> 257 <para>Improving the build speed on a less-well endowed 4-core 258 machine. On a machine with a powerful CPU and plenty of RAM, running 259 N+2 jobs (the ninja default for 4+ cores) for the large working sets 260 of the C++ compiles in this package is typically only marginally 261 faster than running N jobs at a time. But for a machine with less 262 memory it can be much slower.</para> 263 </listitem> 264 <listitem> 265 <para>Reducing the number of cores being used on long running, CPU 266 intensive packages may alleviate heat problems.</para> 267 </listitem> 268 </itemizedlist> 257 269 258 270 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.