Closed Bug 75018 Opened 24 years ago Closed 23 years ago

Enable PSM 2.0 for Linux

Categories

(Core Graveyard :: Security: UI, defect)

1.0 Branch
x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
psm2.0

People

(Reporter: ddrinan0264, Assigned: javi)

Details

Enable PSM 2.0 in the mozilla and commercial builds.
To test Linux builds of PSM 2.0 1) cvs co mozilla/client.mk 2) cd mozilla 3) gmake -f client.mk checkout 4) gmake -f client.mk checkout NSS_CO_TAG=PSM2_NSS_CLIENT_TAG_20010410 BUILD_MODULES=psm2 5) configure 6) gmake 7) configure --enable-modules=psm2 8) gmake BUILD_MODULES=psm2
I ran into problems with the above, perhaps it is outdated? The following forks for me: 1) cvs co mozilla/client.mk 2) cd mozilla 3) export MOZ_NSS_AUTOCONF=1 4) gmake -f client.mk checkout 5a) mkdir -p _build; cd _build; ../configure --enable-crypto or 5b) configure --enable-crypto 6) gmake
robbe, did your build die trying to build in mozilla/security/psm? If so, i think i have a fix, in a bug assigned to me, that i can't recall the number for (removing "security" from the psm2 module definition in mozilla/build/unix/modules.mk is the fix that worked for me)
I can build with javi's recipe now (with minor changes to build in a subdir, and disable debugging). Still, I'd prefer doing it in a way that does not involve jumping through all the hoops (checkout, configure, make) twice.
The OS should probably be Linux for this bug. Anyway, I have a question for robbe. I am currently building PSM2.0 on Solaris using javi's recipe. Have to make some minor changes as well, but I am curious on your comment about disabling debugging. Can you tell me why you are disabling that? Are you seeing problem with debug enabled? Thanks.
No problems with debugging, except: .../deb/mozilla$ du -sh _build* 125M _build 931M _build_debug But, back on topic: will PSM2 get the default before 0.9.1? There's no target milestone set. I guess that the 0.9 binaries /will/ contain PSM2.
We're shooting for default building RealSoonNow, and almost certainly by 1.0.
OS: Windows NT → Linux
Target -> PSM 2.0
Keywords: nsCatFood
here's the recipe i used: 0. make sure i had already built mozilla *without* psm2. 1. gmake -f client.mk checkout NSS_CO_TAG=PSM2_NSS_CLIENT_TAG_20010410 2. gmake -f client.mk checkout BUILD_MODULES=psm2 3. i configured --enable-modules=psm2, eg, in ~/.mozmyconfig.sh added the following: ac_add_options --enable-modules=psm2 4. gmake -f client.mk build_all gotchas/questions: * re: step (0): why is it that i need to have mozilla already built before i can build psm2? the reason i ask is that i kept getting build failures [in xpcom? i think --sorry, it was late when i last tried] when i did either of the following: a. clobber_all, then pull_and_build_all [still had --enable-modules=psm2], or, b. removed my tree [rm -rf mozilla/], checked out: gmake -f client.mk checkout [default pull] gmake -f client.mk checkout NSS_CO_TAG=PSM2_NSS_CLIENT_TAG_20010410 gmake -f client.mk checkout BUILD_MODULES=psm2 then finally did a build_all [again, still had --enable-modules=psm2] * at step (1), it seems that a pull_all is being done? why? i guess i ask since i'm not very familiar with how cvs/the build system knows when to specifically pull what at times. :) * after step (4) i am --so far-- able to do another pull_all and build_all [yeah, i can do that as one step, but it's a weird habit of mine, heh]. however, i cannot help but wonder: at what point would i manage to pull something that would break a subsequent build because of the psm2 i have in my tree? would it have to be something lowlevel [xpcom/connect, dom, js, netwerk, or layout...]? and if so, what would be an easier workaround than starting from scratch with a clean tree?
You no longer have to build mozilla first and you seem to be using tags we created to ease the transition from PSM1 to PSM2. See new updated instructions for building at http://mozilla.org/projects/security/pki/psm/buildpsm.html
Target Milestone --- -> 2.0.
Target Milestone: --- → 2.0
Assigning to javi.
Assignee: ddrinan → javi
PSM2 is now bundled with nightly builds. Marking this fixed.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Javier: Reading the instruction on the webpage, does it mean that pulling out mozilla will automatically pull out psm as well? No need to explicitly pull anymore? Thanks, Margaret
Margaret, Yes that is the case.
thx, javi. i changed --enable-modules=psm2 to --enable-crypto, and this works fine. tested with a clean tree and a few subsequent depend builds.
Status: RESOLVED → VERIFIED
Verified.
Product: PSM → Core
Version: psm2.0 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.