Do you have NSPR in your tree at the point this happens?
At this point you're still building NSS. NSS isn't autoconf'ed so
that's why you're seeing the Linux...OBJ path in the include var.
-I../../../../dist/Linux2.4_x86_glibc_PTH_OPT.OBJ/include is a remnant
of the NSS build system which is just a symlink to
../../../../dist/include iff you've used the Makefile in
mozilla/security/manager/ to build PSM2.0 + NSS. That's where the NSPR
headers should be. This leads me to believe that NSPR hasn't been built
in this same tree. I don't remember if the psm2 module builds all of
its dependencies (cls did that work, so you'd have to ask him), but I
recommend doing a full browser build first then running the psm2 build
procedure. This is how I build on Linux and I haven't had a problem.
Also, remember to use PSM20_M_1_5_TAG for now to get a candidate of the
NSS we're considering for PSM 2.0
--
Javier Delgadillo Sun / Netscape Alliance
(408) 276-3977 Software Engineer
mailto:[EMAIL PROTECTED] http://people.netscape.com/javi
