You are currently viewing a snapshot of www.mozilla.org taken on April 21, 2008. Most of this content is highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If there are any pages on this archive site that you think should be added back to www.mozilla.org, please file a bug.



Troubleshooting NSS and JSS Builds

Newsgroup: mozilla.dev.tech.crypto
Technical contacts: Sonja Mirtitsch
Manager: Wan-Teh Chang

This page summarizes information on troubleshooting the NSS and JSS build and test systems, including known problems and configuration suggestions.

If you have suggestions for this page, please post them to mozilla.dev.tech.crypto.


Building NSS

  • Having /usr/ucb/bin in the path before /usr/ccs/bin breaks the build on 64-bit Solaris.
  • The Solaris compiler needs to be workshop-5.0 or greater.
  • The 64-bit builds don't support gcc.
  • If the build fails early on the gmake in coreconf try updating your cvs tree with -P:

    cd mozilla
    cvs update -P


Testing NSS

  • The SSL stress test opens 2,048 TCP connections in quick succession. Kernel data structures may remain allocated for these connections for up to two minutes. Some systems may not be configured to allow this many simultaneous connections by default; if the stress tests fail, try increasing the number of simultaneous sockets supported.


Building JSS

  • Windows Only: The shell invoked by gmake, shmsdos.exe, is likely to crash when invoking some Java tools on Windows. The current workaround is to use some other shell in place of shmsdos, such as sh.exe, which should be distributed with the Cygnus toolkit you installed to build NSS. The change is unfortunately rather drastic: to trick gmake, you rename the shell program.
    cd c:/Programs/cygnus/bin(or wherever your GNU tools are installed)
    cp shmsdos.exe shmsdos.bak(backup shmsdos)
    cp sh.exe shmsdos.exe(substitute alternative shell)
    Making this change will probably break other builds you are  making on the same machine. You may need to switch the shell back and forthdepending on which product you are building. We will try to provide a moreconvenient solution in the future. If you have the MKS toolkit installed,  the sh.exe that comes with this toolkit can be used as well.