We would like to add a build, configuration and test troubleshooting section
to the NSS website, the attached draft is still incomplete.
Please add known problems and suggestions to the list below.
Troubleshooting NSS/JSS Build and TestThese are tips on troubleshooting the NSS and JSS build and test system, known problems and configuration suggestions.
If you have more to add to this page, please post to netscape.public.mozilla.crypto.
Building NSS
- having /usr/ucb/bin in the path before /usr/ccs/bin breaks the build on solaris 64 bit
- Solaris compiler needs to be workshop-5.0 or greater
- gcc is not supported on the 64 bit builds
- 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 totwo minutes.
Some systems may not be configured to allow this many simultaneousconnections
by default; if the stress tests fail, try increasing the numberof 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
|
|
