Changeset bf5fb94 for xsoft/graphweb

Timestamp:

10/26/2020 09:44:17 PM (3 years ago)

Author:

Ken Moffat <ken@…>

Branches:

10.1, 11.0, 11.1, 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, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

6fe9b0bd

Parents:

a2e21ee

Message:

Update to llvm-11.0.0 and rustc-1.47.0.

Patch firefox and thunderbird for this version of rust.
Remeasure all packages which use rust -
I think I used an out of date mozconfig when I updated thunderbird.
In general, builds are slower and slightly larger, but installs are marginally smaller.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@23843 af4574ff-66df-0310-9fd7-8a98e5e911e0

Location:

xsoft/graphweb

Files:

• firefox.xml (modified) (4 diffs)
• seamonkey.xml (modified) (2 diffs)

xsoft/graphweb/firefox.xml

@@ -11 +11 @@
   <!-- NB with stylo, much of the build uses rust, and therefore cargo files.
     But the extra cached cargo files, if any, seem to be minimal -->
-  <!ENTITY firefox-buildsize     "4.7 GB (184 MB installed) without tests">
+  <!ENTITY firefox-buildsize     "5.0 GB (181 MB installed) without tests">
   <!-- editors: with ff63 and rust-1.29, ./mach build -j4 is probably the
    most practical way to get a timing on a machine with more cores, if taking
    cores offline is not practical. If in doubt, round up -->
-  <!ENTITY firefox-time          "29 SBU (on a 4-core machine) without tests">
+  <!ENTITY firefox-time          "30 SBU (on a 4-core machine) without tests">
 ]>
 
@@ -76 +76 @@
     </itemizedlist>
 
+    <bridgehead renderas="sect3">Additional Downloads</bridgehead>
+    <itemizedlist spacing="compact">
+      <listitem>
+        <para>
+          Required patch:
+          <ulink url="&patch-root;/firefox-&firefox-version;esr-rustc1470-1.patch"/>
+        </para>
+      </listitem>
+    </itemizedlist>
+
     <note>
       <para>
@@ -346 +356 @@
 esac</userinput></screen>
     -->
+    <para>
+      Apply a patch to allow this to be compiled with <xref linkend="rust"/>:
+    </para>
+
+<screen><userinput remap="pre">patch -p1 -i ../firefox-&firefox-version;esr-rustc1470-1.patch</userinput></screen>
 
     <para>
@@ -394 +409 @@
       everywhere. On the X86 architectures <application>clang</application>
       now appears to support most of the same security-hardening options as
-      <application>GCC</application> but the newer
-      <literal>-fstack-clash-protection</literal> is still not supported.
+      <application>GCC</application>.
+      <!-- supported in llvm-11
+      but the newer
+      <literal>-fstack-clash-protection</literal> is still not supported.-->
       With the current versions and the default flags,
       <application>GCC</application> creates a marginally bigger build but

xsoft/graphweb/seamonkey.xml

@@ -9 +9 @@
   <!ENTITY seamonkey-md5sum        "bbf02af3586f1d488e77517f8cd9f439">
   <!ENTITY seamonkey-size          "281 MB">
-  <!ENTITY seamonkey-buildsize     "6.6 GB (145 MB installed)">
-  <!ENTITY seamonkey-time          "16 SBU (on a 4-core machine)">
+  <!ENTITY seamonkey-buildsize     "6.8 GB (145 MB installed)">
+  <!ENTITY seamonkey-time          "18 SBU (on a 4-core machine)">
 ]>
 
@@ -107 +107 @@
       <xref linkend="autoconf213"/>,
       both <xref linkend="gtk2"/> and <xref linkend="gtk3"/>,
+      <xref linkend="python2"/>,
       <xref linkend="rust"/>,
       <xref linkend="unzip"/>,