Randell Jesup wrote:
> Javier Delgadillo <[EMAIL PROTECTED]> writes:
>
> >If you follow the instructions at the URL listed below, NSS will get built for
> >you.
> >
> >http://www.mozilla.org/projects/security/pki/psm/buildpsm.html
>
> From that page:
> :Because of complicated dependencies, you need a fully built Mozilla tree in
> :order to compile PSM. These instructions also assume you have a completed
> :NSS build tree.
>
> >> Is it necessary to build NSS in order to build PSM? Sorry if it is an stupid
> >> question. I am trying to build it on win2000.
>
> Ok, I have a bunch of questions about building PSM, NSS, etc.
>
> Right now it seems like it's a bunch of levers and buttons, all labelled
> cryptically, and the order you press them in matters. If by chance you
> get a working build, it's not likely you can repeat the experiments that
> got it working. (At least under Unix).
>
> "gmake -f client.mk BUILD_MODULES=psm"
>
> As you said, this assumes you have built NSS. There's no link
> telling you how to build NSS on the page above. If you do go to the NSS
> build page, it tells you about nss3.2. Do we need to use 3.2? I dunno.
This is not true. That statement assumes you have the sources only. We'll have
to update the documentation. Sorry for that.
The above gmake statement will go off and build NSPR, DBM, NSS, then PSM. All you
have to do is pull the source. You do not need to manually build NSS if all you
want is to build PSM in your browser tree.
The only reason to build NSS stand-alone is if you want to build a custom app that
uses NSS as the crypto engine.
>
>
> The above command builds (under freeBSD) a
> .../mozilla/dist/FreeBSD4.1_DBG.OBJ directory. However, all the regular
> "gmake -f client.mk build", etc commands build things in .../mozilla/dist.
> I was forced to add a symlink from .../mozilla/FreeBSD4.1_DBG.OBJ to
> .../mozilla/dist by hand (and restore it on each clobber).
>
This leads me to believe the moz_import rule in the mozilla/security/nss directory
was never executed in your tree. That rule gets executed as part of the
PSM build.
>
> Eventually (quickly), if you track the trunk, your psm/nss stuff
> atrophies (or gets nuked by a clobber build), and you have to start over
> again figuring out what magic needs to be done to build it.
>
> What's the chance of a _working_ --enable-psm and/or --enable-nss
> (or --enable-ssl, etc) for mozilla's configure?
>
> Please excuse my shortness on this; I've spent literally days (in
> total over a number of occasions) fighting the PSM/NSS build system.
>
> --
> Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94)
> [EMAIL PROTECTED]
--
Javier Delgadillo Sun / Netscape Alliance
(408) 276-3977 Software Engineer
mailto:[EMAIL PROTECTED] http://people.netscape.com/javi
