Closed
Bug 95257
Opened 23 years ago
Closed 23 years ago
Crypto/NSS/PSM won't configure/build in 0.9.3 or recent CVS
Categories
(SeaMonkey :: Build Config, defect)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: h, Assigned: cls)
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010813 BuildID: 0000000000 When using --enable-crypto, configure warns: configure: warning: no configuration information is in security/nss and make fails in security/nss Reproducible: Always Steps to Reproduce: 1.$ cd /usr/src $ rm -rf mozilla $ tar xvfj ~/downloads/mozilla-source-0.9.3.tar.bz2 $ rm mozilla/client.mk $ export CVSROOT=:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot $ cvs login $ cvs co mozilla/client.mk $ gmake -f mozilla/client.mk checkout $ cd mozilla $ ./configure ... --enable-crypto 2. make Actual Results: 1. configure: warning: no configuration information is in security/nss 2. cd crmf; make export make[3]: Entering directory `/usr/src/mozilla/security/nss/lib/crmf' Creating ../../../../dist/public/security /bin/sh: ../../../coreconf/nsinstall/Linux2.4_x86_glibc_PTH_DBG.OBJ/nsinstall: No such file or directory make[3]: *** [../../../../dist/public/security] Error 127 make[3]: Leaving directory `/usr/src/mozilla/security/nss/lib/crmf' make[2]: *** [export] Error 2 make[2]: Leaving directory `/usr/src/mozilla/security/nss/lib' make[1]: *** [export] Error 2 make[1]: Leaving directory `/usr/src/mozilla/security/nss' make: *** [export] Error 2 Expected Results: Configured and built NSS It doesn't seem to make any difference whether I use the unmodified tarball, try to pull extra modules but from the 0.9.3 release (by not deleting client.mk first), or go for the latest CVS as above.
> When using --enable-crypto, configure warns:
> configure: warning: no configuration information is in security/nss
> and make fails in security/nss
You need to unset MOZ_NSS_AUTOCONF before running the toplevel configure. Can
you attach a full build log & config/autoconf.mk ?
Marking invalid per m.crypto post. news://news.mozilla.org:119/slrn9nj09u.6k8.tony@realh.co.uk
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•