Changes between Version 6 and Version 7 of nss

Timestamp:

12/16/2018 08:50:37 PM (6 years ago)

Author:

ken@…

Comment:

--

nss

@@ -1 +1 @@
 = NSS =
 
-== x86_64 ==
- On x86_64 the build will default to 32-bit.  In multilib, this may be exactly what you want.  In pure64, it will fail to build.  You can get around this with
+== The testsuite in modern versions of nss ==
+
+The current testsuite is designed to catch regressions in new additions,
+so every new addiiton should come with one or more tests (I noticed from
+the diff between 3.40 and 3.40.1 that there ''were'' tests, although the
+book said there was not a testsuite).
+
+Unfortunately, it needs to be run with nspr and nss directories side by
+side in the top-level directory (which is how combined nspr+nss tarballs
+present things), and built unoptimized (BUILD_OPT=0).
+
+For further details, see [https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_Sources_Building_Testing]
+
+I managed to get that process working on 4.19+3.40 but not with 3.40.1.
 {{{
-make USE_64=1 nss_build_all
+make -C nss nss_build_all USE64=1
 }}}
+That took almost 25 minutes, I don't think the particular CPU makes a lot of difference.
+For that run, 6 tests failed (look for ' FAILED' in the output), all reporting that a
+peer's certificate has expired.
 
-== ppc64 ==
+Unless you intend to hack on nss/nspr, running the tests on a released version is not recommended.
+
+== Old notes, retained in case still useful ==
+
+=== ppc64 ===
  On ppc64, building 32-bit barfs on -z defs when CC is overridden to "gcc -m32".  Use the patch at [http://www.linuxfromscratch.org/patches/downloads/nss/nss-3.11-zdefs-1.patch] and read the instructions in it.
 
-== Test Suite: CRL tests ==
+=== Test Suite: CRL tests ===
 cert.sh uses the local time when creating revocation lists. This can cause
 a number of tests (130 out of 800) to fail.