VMSuni.opt must go into $OBJDIR

RESOLVED FIXED in 3.3.1

Status

NSS
Build
P2
normal
RESOLVED FIXED
17 years ago
17 years ago

People

(Reporter: Colin Blake, Assigned: Ian McGreer)

Tracking

3.3.1
DEC
OpenVMS

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

17 years ago
Something has changed in the build of NSS recently (between 0.9.1 and 0.9.2)
so that now the current working directory is the source tree instead of the 
object tree. This seems strange to me since for everything else the object
directory is the current working directory, but Wan-Teh tells me that this is
a deliberate change.

As a result of this, the VMSuni.opt files that get created during the OpenVMS
build are now in the source tree instead of the object tree. This needs fixing.
(Reporter)

Updated

17 years ago
OS: Windows 98 → OpenVMS
(Reporter)

Updated

17 years ago
Status: NEW → ASSIGNED
(Reporter)

Comment 1

17 years ago
Created attachment 40488 [details] [diff] [review]
Patch to fix problem (from 0.9.2 branch)
(Reporter)

Comment 2

17 years ago
Over to NSS group for checkin.
Assignee: colin → wtc
Status: ASSIGNED → NEW
Component: Libraries → Build
QA Contact: sonmi → wtc

Comment 3

17 years ago
Assigned the bug to Ian.

Ian, this bug needs to be checked in on NSS_3_2_BRANCH,
NSS_3_3_BRANCH, and the trunk.  Then, move the NSS_CLIENT_TAG
to the revision on NSS_3_2_BRANCH.

You might want to ask Bob to review this patch.
Assignee: wtc → mcgreer
Priority: -- → P2
Target Milestone: --- → 3.2.2

Comment 4

17 years ago
Looks good as far as I can tell. I'll trust colin that it works for Open VMS.
For everyone else it should have no effect.
(Assignee)

Comment 5

17 years ago
done all of the above.

Mozilla pulls NSS from MOZILLA_0_9_2_BRANCH for the 0.9.2 branch.  Colin, do you
need the checkin there, also?  I think that would require PDT approval and all that.
(Reporter)

Comment 6

17 years ago
I'm not bothered about 0.9.2. As long as future pulls will get the change,
I'm happy.

Colin.
(Reporter)

Comment 7

17 years ago
Confirming that everything is checked in just fine. My 0.9.3 Mozilla build
went without a hitch. Closing.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED

Comment 8

17 years ago
This fix is not in 3.2.2 and 3.3 but is in 3.3.1 and
the 3.2 branch.  Since we are not planning to make any
new 3.2.x releases, I am setting the target milestone
to 3.3.1.
Target Milestone: 3.2.2 → 3.3.1
You need to log in before you can comment on or make changes to this bug.