Index: xsoft/graphweb/seamonkey.xml
===================================================================
--- xsoft/graphweb/seamonkey.xml	(revision e4a6895145acc647824a6945e865960458dd20c9)
+++ xsoft/graphweb/seamonkey.xml	(revision 33de79b943f07340007d19fffb96510862c815ee)
@@ -7,8 +7,8 @@
   <!ENTITY seamonkey-download-http "&mozilla-http;/seamonkey/releases/&seamonkey-version;/source/seamonkey-&seamonkey-version;.source.tar.xz">
   <!ENTITY seamonkey-download-ftp " ">
-  <!ENTITY seamonkey-md5sum        "3cba72ec6a37f7c68fac48876a3a5f8f">
-  <!ENTITY seamonkey-size          "271 MB">
+  <!ENTITY seamonkey-md5sum        "f36c532bbd9c6903036aa02e9a40246b">
+  <!ENTITY seamonkey-size          "272 MB">
   <!ENTITY seamonkey-buildsize     "6.1 GB (159 MB installed)">
-  <!ENTITY seamonkey-time          "20 SBU (on a 4-core machine)">
+  <!ENTITY seamonkey-time          "21 SBU (with parallelism=4)">
 ]>
 
@@ -137,20 +137,5 @@
       </para>
     </note>
-<!--
-    <note>
-      <para>
-        You must have installed <application>Openssl</application> before
-        <application>Python 2</application> or the build system will quickly
-        fail with output including "ImportError: cannot import name
-        HTTPSHandler". If you are in any doubt about this (e.g. upgrading from
-        an older version of Seamonkey), check if
-        <filename>/usr/lib/python&python2-majorver;/lib-dynload/_ssl.so</filename>
-        exists.  If it does not, reinstall <xref linkend="python2"/> (after
-        installing <xref linkend="openssl"/>.  The latest version of any
-        <emphasis>currently maintained</emphasis> version of Openssl should be
-        satisfactory if already installed.
-      </para>
-    </note>
--->
+
     <bridgehead renderas="sect4">Optional</bridgehead>
     <para role="optional">
@@ -191,8 +176,6 @@
 
 <screen><?dbfo keep-together="auto"?><userinput>cat &gt; mozconfig &lt;&lt; "EOF"
-<literal># If you have a multicore machine, all cores will be used by default.
-# If desired, you can reduce the number of cores used, e.g. to 1, by
-# uncommenting the next line and setting a valid number of CPU cores.
-#mk_add_options MOZ_MAKE_FLAGS="-j1"
+<literal># If you have a multicore machine, all cores will be used
+# unless you pass -jN to ./mach build
 
 # If you have installed DBus-Glib comment out this line:
@@ -224,6 +207,4 @@
 ac_add_options --with-system-libevent
 ac_add_options --with-system-nspr
-# nss-3.65 broke the build of seamonkey, use the shipped version
-# Fixed with 2.53.8
 ac_add_options --with-system-nss
 ac_add_options --with-system-webp
@@ -255,9 +236,5 @@
 ac_add_options --enable-official-branding
 
-# From firefox-40 (and the corresponding version of seamonkey),
-# using system cairo caused seamonkey to crash
-# frequently when it was doing background rendering in a tab.
-# This appears to again work in seamonkey-2.49.2
-ac_add_options --enable-system-cairo
+# The option to use system cairo was removed in 2.53.9.
 ac_add_options --enable-system-ffi
 ac_add_options --enable-system-pixman
@@ -302,6 +279,10 @@
     </para>
 
-<screen><userinput>CC=gcc CXX=g++ ./mach build</userinput></screen>
-
+<screen><userinput>export CC=gcc CXX=g++ &amp;&amp;
+./mach configure                           &amp;&amp;
+./mach build</userinput></screen>
+
+
+    <!-- comment this since llvm must have been installed for rust
     <note>
       <para>
@@ -309,5 +290,5 @@
         <xref linkend="llvm"/> is installed and you do not want to use clang.
       </para>
-    </note>
+    </note>-->
 
     <para>
@@ -332,7 +313,26 @@
 
     <para>
-      <command>./mach build</command>: <application>Seamonkey</application>
-      now uses this <application>python</application> script to run the
-      build and install.
+      <command>export CC=gcc CXX=g++ ...</command>: Upstream now prefer
+      <application>clang</application> so that they can use one compiler
+      everywhere. On the X86 architectures <application>clang</application>
+      takes a little longer than gcc to compile mozilla applications.
+    </para>
+
+    <para>
+      <command>./mach configure</command>: This validates the supplied
+      dependencies and the <filename>mozconfig</filename>.
+    </para>
+
+    <para>
+      <option>./mach build --verbose</option>: Use this alternative if you
+      need details of which files are being compiled, together with any C or
+      C++ flags being used. But do not add '--verbose' to the install command,
+      it is not accepted there.
+    </para>
+
+    <para>
+      <option>./mach build -jN</option>: The build should, by default, use
+      all the online CPU cores. If using all the cores causes the build to swap
+      because you have insufficient memory, using fewer cores can be faster.
     </para>
 
