Changeset e51466a for xsoft/graphweb/firefox.xml
- Timestamp:
- 06/28/2022 04:01:41 PM (22 months ago)
- Branches:
- 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, xry111/llvm18, xry111/soup3, xry111/xf86-video-removal
- Children:
- b0540bce
- Parents:
- e603046
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
xsoft/graphweb/firefox.xml
re603046 re51466a 7 7 <!ENTITY firefox-download-http "&mozilla-http;/firefox/releases/&firefox-version;esr/source/firefox-&firefox-version;esr.source.tar.xz"> 8 8 <!ENTITY firefox-download-ftp " "> 9 <!ENTITY firefox-md5sum " c22765dc34c94035ebd83b998c90de33">10 <!ENTITY firefox-size " 363MB">9 <!ENTITY firefox-md5sum "72d8bf3644c4db2cced72fa3f712a4a1"> 10 <!ENTITY firefox-size "464 MB"> 11 11 <!-- NB with stylo, much of the build uses rust, and therefore cargo files. 12 12 But the extra cached cargo files, if any, seem to be minimal --> 13 <!ENTITY firefox-buildsize " 6.6 GB (193MB installed) without tests">13 <!ENTITY firefox-buildsize "7.1 GB (199 MB installed) without tests"> 14 14 <!-- editors: with ff63 and rust-1.29, ./mach build -j4 is probably the 15 15 most practical way to get a timing on a machine with more cores, if taking 16 16 cores offline is not practical. If in doubt, round up --> 17 <!ENTITY firefox-time "2 5SBU (on a typical 4-core machine) without tests">17 <!ENTITY firefox-time "24 SBU (on a typical 4-core machine) without tests"> 18 18 ]> 19 19 … … 75 75 </itemizedlist> 76 76 77 77 <!--<bridgehead renderas="sect3">Additional Downloads</bridgehead> 78 78 <itemizedlist spacing="compact"> 79 79 <listitem> … … 89 89 </para> 90 90 </listitem> 91 </itemizedlist> 91 </itemizedlist>--> 92 92 93 93 <note> … … 292 292 ac_add_options --with-system-zlib 293 293 294 # Using sandboxed wasm libraries has been moved to all builds instead 295 # of only mozilla automation builds. It requires extra llvm packages 296 # and was reported to seriously slow the build. Disable it. 297 ac_add_options --without-wasm-sandboxed-libraries 298 294 299 # The following option unsets Telemetry Reporting. With the Addons Fiasco, 295 300 # Mozilla was found to be collecting user's data, including saved passwords and … … 308 313 </para> 309 314 310 315 <!--<para> 311 316 First apply a patch which works around unexplained failures on some machines 312 317 (a message that a python check on libgkrust.a identified 1 networking … … 320 325 </para> 321 326 322 <screen><userinput>patch -Np1 -i ../firefox-&firefox-version;esr-gcc12_fix-1.patch</userinput></screen> 327 <screen><userinput>patch -Np1 -i ../firefox-&firefox-version;esr-gcc12_fix-1.patch</userinput></screen>--> 323 328 324 329 <para> … … 330 335 <screen><userinput>sed -i '/ROOT_CLIP_CHAIN/d' gfx/webrender_bindings/webrender_ffi.h</userinput></screen> 331 336 332 <!-- applying this for 11.1: upstream haven't make their mind yet 333 https://bugzilla.mozilla.org/show_bug.cgi?id=1729459 --> 337 <!-- applying this for 11.1: upstream haven't made their mind yet 338 https://bugzilla.mozilla.org/show_bug.cgi?id=1729459 339 Still applies in 102.0, 32-bit build NOT tested for that. --> 340 334 341 <para> 335 342 If building on a 32 bit machine, the following sed works around … … 395 402 </para> 396 403 397 <screen><userinput>export CC=gcc CXX=g++ && 398 export MACH_USE_SYSTEM_PYTHON=1 && 399 export MOZBUILD_STATE_PATH=${PWD}/mozbuild && 400 ./mach configure && 404 <screen><userinput>export MACH_BUILD_PYTHON_NATIVE_PACKAGE_SOURCE=system && 405 export MOZBUILD_STATE_PATH=${PWD}/mozbuild && 406 ./mach configure && 401 407 ./mach build</userinput></screen> 402 408 … … 416 422 </para> 417 423 418 <screen role="root"><userinput>MACH_ USE_SYSTEM_PYTHON=1./mach install</userinput></screen>424 <screen role="root"><userinput>MACH_BUILD_PYTHON_NATIVE_PACKAGE_SOURCE=system ./mach install</userinput></screen> 419 425 420 426 <para> … … 422 428 </para> 423 429 424 <screen><userinput>unset CC CXX MACH_USE_SYSTEM_PYTHONMOZBUILD_STATE_PATH</userinput></screen>430 <screen><userinput>unset MACH_BUILD_PYTHON_NATIVE_PACKAGE_SOURCE MOZBUILD_STATE_PATH</userinput></screen> 425 431 426 432 </sect2> … … 431 437 <!--<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" 432 438 href="../../xincludes/SIOCGSTAMP.xml"/>--> 433 434 <para>435 <command>export CC=gcc CXX=g++ ...</command>: Upstream now prefer436 <application>clang</application> so that they can use one compiler437 everywhere. On the X86 architectures <application>clang</application>438 now appears to support most of the same security-hardening options as439 <application>GCC</application>.440 <!-- supported in llvm-11441 but the newer442 <literal>-fstack-clash-protection</literal> is still not supported.-->443 With the current versions and the default flags,444 <application>GCC</application> creates a marginally bigger build but445 takes typically 2 SBU less time on a 4-core machine using the mozconfig446 above.447 </para>448 439 449 440 <para> … … 465 456 466 457 <para> 467 <command>MACH_ USE_SYSTEM_PYTHON=1</command>: Use the system python468 to create a virtual environment for <command>mach</command> without469 downloading any python wheels.458 <command>MACH_BUILD_PYTHON_NATIVE_PACKAGE_SOURCE=system</command>: Use the 459 system python to create a virtual environment for <command>mach</command> 460 without downloading any python wheels. 470 461 </para> 471 462 … … 488 479 </para> 489 480 490 <!-- 491 <para> 492 <command>mkdir -pv /usr/lib/mozilla/plugins</command>: This ensures 493 that <filename class="directory">/usr/lib/mozilla/plugins/</filename> 494 exists. 495 </para> 496 497 <para> 498 <command>ln -sv ... /usr/lib/firefox/browser</command>: 499 This command creates a symbolic link to <filename 500 class="directory">/usr/lib/mozilla/plugins</filename>. It's not really 501 needed, as <application>Firefox</application> checks <filename 502 class="directory">/usr/lib/mozilla/plugins</filename> by default, but the 503 symbolic link is made to keep all the plugins installed in one folder. 504 </para> 505 --> 481 <para> 482 <parameter><envar>CC=gcc CXX=g++</envar></parameter>: BLFS used to 483 prefer to use gcc and g++ instead of upstream's defaults of the 484 <application>clang</application> programs. With the release of 485 gcc-12 the build takes longer with gcc and g++, primarily because 486 of extra warnings, and is bigger. Set these environment variables 487 <emphasis>before you run the configure script</emphasis> 488 if you wish to continue to use gcc, g++. 489 </para> 506 490 507 491 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.