Changeset e51466a


Ignore:
Timestamp:
06/28/2022 04:01:41 PM (6 weeks ago)
Author:
Ken Moffat <ken@…>
Branches:
trunk
Children:
b0540bce
Parents:
e603046
Message:

Update for firefox-102.0esr (security fix).

Files:
3 edited

Legend:

Unmodified
Added
Removed
  • introduction/welcome/changelog.xml

    re603046 re51466a  
    4646      <itemizedlist>
    4747        <listitem>
     48          <para>[ken] - Update to firefox-102.0esr (security fix) and use
     49          clang for it. Fixes <ulink url="&blfs-ticket-root;16708">#16708</ulink>
     50          If updating from firefox-91 series, please check that ticket (or the
     51          wiki) for dependency updates and build changes, and for information
     52          if your firefox profile is shared across multiple systems with the same
     53          /home. This addresses part of
     54          <ulink url="&blfs-ticket-root;16697">#16697</ulink>.</para>
     55        </listitem>
     56        <listitem>
    4857          <para>[ken] - Update to JS91.11.0 (security fix) and recommend
    4958          clang to build it to save time. Fixes
  • packages.ent

    re603046 re51466a  
    960960
    961961<!-- for firefox-legacy-version use JS78-version: f-l archived at version 78.15.0 -->
    962 <!ENTITY firefox-version              "91.10.0">
     962<!ENTITY firefox-version              "102.0">
    963963<!ENTITY flashplayer-version          "27.0.0.187">
    964964<!ENTITY qupzilla-version             "2.2.6">
  • xsoft/graphweb/firefox.xml

    re603046 re51466a  
    77  <!ENTITY firefox-download-http "&mozilla-http;/firefox/releases/&firefox-version;esr/source/firefox-&firefox-version;esr.source.tar.xz">
    88  <!ENTITY firefox-download-ftp  " ">
    9   <!ENTITY firefox-md5sum        "c22765dc34c94035ebd83b998c90de33">
    10   <!ENTITY firefox-size          "363 MB">
     9  <!ENTITY firefox-md5sum        "72d8bf3644c4db2cced72fa3f712a4a1">
     10  <!ENTITY firefox-size          "464 MB">
    1111  <!-- NB with stylo, much of the build uses rust, and therefore cargo files.
    1212    But the extra cached cargo files, if any, seem to be minimal -->
    13   <!ENTITY firefox-buildsize     "6.6 GB (193 MB installed) without tests">
     13  <!ENTITY firefox-buildsize     "7.1 GB (199 MB installed) without tests">
    1414  <!-- editors: with ff63 and rust-1.29, ./mach build -j4 is probably the
    1515   most practical way to get a timing on a machine with more cores, if taking
    1616   cores offline is not practical. If in doubt, round up -->
    17   <!ENTITY firefox-time          "25 SBU (on a typical 4-core machine) without tests">
     17  <!ENTITY firefox-time          "24 SBU (on a typical 4-core machine) without tests">
    1818]>
    1919
     
    7575    </itemizedlist>
    7676
    77     <bridgehead renderas="sect3">Additional Downloads</bridgehead>
     77<!--<bridgehead renderas="sect3">Additional Downloads</bridgehead>
    7878    <itemizedlist spacing="compact">
    7979      <listitem>
     
    8989        </para>
    9090      </listitem>
    91     </itemizedlist>
     91    </itemizedlist>-->
    9292
    9393    <note>
     
    292292ac_add_options --with-system-zlib
    293293
     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.
     297ac_add_options --without-wasm-sandboxed-libraries
     298
    294299# The following option unsets Telemetry Reporting. With the Addons Fiasco,
    295300# Mozilla was found to be collecting user's data, including saved passwords and
     
    308313    </para>
    309314
    310     <para>
     315<!--<para>
    311316      First apply a patch which works around unexplained failures on some machines
    312317      (a message that a python check on libgkrust.a identified 1 networking
     
    320325    </para>
    321326
    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>-->
    323328
    324329    <para>
     
    330335<screen><userinput>sed -i '/ROOT_CLIP_CHAIN/d' gfx/webrender_bindings/webrender_ffi.h</userinput></screen>
    331336
    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
    334341    <para>
    335342      If building on a 32 bit machine, the following sed works around
     
    395402    </para>
    396403
    397 <screen><userinput>export CC=gcc CXX=g++ &amp;&amp;
    398 export MACH_USE_SYSTEM_PYTHON=1            &amp;&amp;
    399 export MOZBUILD_STATE_PATH=${PWD}/mozbuild &amp;&amp;
    400 ./mach configure                           &amp;&amp;
     404<screen><userinput>export MACH_BUILD_PYTHON_NATIVE_PACKAGE_SOURCE=system &amp;&amp;
     405export MOZBUILD_STATE_PATH=${PWD}/mozbuild            &amp;&amp;
     406./mach configure                                      &amp;&amp;
    401407./mach build</userinput></screen>
    402408
     
    416422    </para>
    417423
    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>
    419425
    420426    <para>
     
    422428    </para>
    423429
    424 <screen><userinput>unset CC CXX MACH_USE_SYSTEM_PYTHON MOZBUILD_STATE_PATH</userinput></screen>
     430<screen><userinput>unset MACH_BUILD_PYTHON_NATIVE_PACKAGE_SOURCE MOZBUILD_STATE_PATH</userinput></screen>
    425431
    426432  </sect2>
     
    431437<!--<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    432438      href="../../xincludes/SIOCGSTAMP.xml"/>-->
    433 
    434     <para>
    435       <command>export CC=gcc CXX=g++ ...</command>: Upstream now prefer
    436       <application>clang</application> so that they can use one compiler
    437       everywhere. On the X86 architectures <application>clang</application>
    438       now appears to support most of the same security-hardening options as
    439       <application>GCC</application>.
    440       <!-- supported in llvm-11
    441       but the newer
    442       <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 but
    445       takes typically 2 SBU less time on a 4-core machine using the mozconfig
    446       above.
    447     </para>
    448439
    449440    <para>
     
    465456
    466457    <para>
    467       <command>MACH_USE_SYSTEM_PYTHON=1</command>: Use the system python
    468       to create a virtual environment for <command>mach</command> without
    469       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.
    470461    </para>
    471462
     
    488479    </para>
    489480
    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>
    506490
    507491  </sect2>
Note: See TracChangeset for help on using the changeset viewer.