Yeah, I know, get with the rest of the world and build 2.0

I'm working on HPUX and we need to work the fix for a bug into our PSM, 
but we are having troubles getting it to build. We are stuck out on the 
branch and don't have the code there ( it wasn't branched with the rest 
of mozilla ) and the instructions we have pull mozilla/security/psm and 
mozilla/security/coreconf from the trunk. And our resident PSM guru is 
on vacation ( of course ).

My question is this: Is there a date we can pull that will work? Our 
current PSM build is from last October, when did PSM 1.3 become work on 
1.4/2.0? Here is what we pull to build:

 > cvs co -r Netscape_6_0_OEM_BRANCH mozilla/client.mk  // branch based 
off of Netscape_20000922_BRANCH at RTM for 6.0
 > cd mozilla
 > gmake -f client.mk pull_all
 > gmake -f client.mk build_all

 > rm -rf mozilla/security/psm
 > cvs co mozilla/security/psm
 > cvs co mozilla/security/coreconf
 > cvs co -r NSS_30_BRANCH mozilla/security/nss
 > cvs co -r NSPRPUB_CLIENT_BRANCH mozilla/nsprpub

# then from the NS tree
 > cvs co -r NSS_30_BRANCH ns/security/lib/crypto

Then we apply some diffs for HPUX, rebuild libnslayer.a, put it in a jar 
and then build. What I'm looking for is a tag for pulling the psm and 
coreconf directories that will work with the nss and nsprpub code pulls. 
Also, it'd be nice if our diffs would patch nicely since they are based 
on code from October of last year.

Any other tips to make this process easier are greatly appreciated too. :-)

thanks,
john


Reply via email to