Closed Bug 83225 Opened 23 years ago Closed 23 years ago

One should be able to build NSS outside the source tree.

Categories

(NSS :: Build, defect, P1)

3.2.1
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: wtc, Assigned: wtc)

References

Details

Attachments

(2 files)

One should be able to build NSS outside the source tree.
This has two advantages.  One, the source tree can be
made read-only.  Two, this enables us to integrate the
NSS build with Mozilla client's objdir build better.
Blocks: 82324
I attached my proposed patch containing Bob's BUILD_TREE
and cross-compilation support for NSS_3_2_BRANCH.  Please
review it.  Thank you.
Status: NEW → ASSIGNED
I've verified my patch on Windows, Linux, and Solaris SPARC.

I just created NSS_3_2_BUILD_TREE_BRANCH, which contains my
proposed patch.

Michael and Javier, could you test it on OS/2?
Colin, could you test it on OpenVMS?

To test it, edit mozilla/client.mk and change NSS_CLIENT_TAG
to NSS_3_2_BUILD_TREE_BRANCH.  Then say
    gmake -f client.mk checkout

Then, apply the patch for bug 82324
(http://bugzilla.mozilla.org/showattachment.cgi?attach_id=36981).

Then configure and make.

It should work out of the box on OpenVMS but may need some
tweaking on OS/2.

Thank you for your help.
Priority: -- → P1
Target Milestone: --- → 3.2.2
Javier Pedemonte noted in bug 82324:
    This and 83225 build and work fine for os/2
    with no changes.

I guess drivers@mozilla.org don't look at
NSS bugs.  I'll send them email.
Blocks: 83989
a=blizzard on behalf of drivers for the trunk
I checked in proposed patch v2 (id=36979) on the NSS_3_2_BRANCH
and moved the NSS_CLIENT_TAG to include it.

I still need to implement bryner's suggestion: put the object
files in objdir/security/nss as opposed to objdir/nss.  I will
do that next.

The NSS_3_2_BUILD_TREE_BRANCH is now dead.  Don't use it.
Marked the bug fixed.  I'm going to address the objdir/security/nss
issue as a separate bug.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
This fix is not in 3.2.2.  This bug is about transplanting
a 3.3 feature (which is supposed to be a separate bug) to
the 3.2 branch.  I'm setting the target milestone to 3.2.3
(even though we are not planning to release any new 3.2.x)
for lack of a better target milestone.
Component: Libraries → Build
Target Milestone: 3.2.2 → 3.2.3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: