Take 2. And I'll censor myself to only build issues. <recap> We had been talking about this for awhile w/o any real tracking mechanism. The branch has been created based upon the NSS 3.2.1 release (NSS_3_2_1_RTM) and has he post 3.2.1 changes from the NSS_CLIENT_TAG applied as well. Bryner has verified that the code on the tag & the branch are the same. We tried but I don't think we're going to make this for 0.9. I'm still working out the kinks of getting this to build on win32 and I don't think the mac will need any changes besides the cvs tag. To use the client branch, add the following options to your ~/.mozconfig: MOZ_NSS_AUTOCONF=1 mk_add_options MOZ_NSS_AUTOCONF=1 ac_add_options --enable-crypto Then pull the tree as normal and build as normal. </recap> We are definitely not going to make this for 0.9.
The client branch now builds on win32. To use it, just replace NSS_CLIENT_TAG with NSS_CLIENT_BRANCH in client.mak and set BUILD_PSM2=1 as usual.
Just an FYI to people who are waiting for this landing, we are partially waiting on a timeline for a counterproposal that will allow us to use the existing NSS build system but allow us to avoid the problems outlined in bug 60912. So it's a distinct possibility that this work will be thrown away. You have been warned. So, the officially sanctioned way to build PSM/NSS for mozilla is still to not have any of the above changes in .mozconfig and do this after your normal build: make BUILD_MODULES=psm2
Ok, I took this branch, and applied it to my mozilla 0.9 tree I logged into the solaris machine with gcc and nspr installed in /opt I then ran my normal configure with MOZ_NSS_AUTOCONF=1 and --enable-crypto I then ran make I watched the whole thing build with no problems whatsoever This is so much simpler and cleaner than the old way, where I had to rewrite half of the stuff in coreconf to change compiler flags for GCC and overwrite variables for the location of NSPR includes and libs. Landing this will make a lot of people very happy, especially me, since I won't have to apply the rather large patch.
Not going to happen.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.