Closed Bug 106771 Opened 24 years ago Closed 24 years ago

Need to support building on hpux 11.11

Categories

(SeaMonkey :: Build Config, defect)

HP
HP-UX
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jdunn, Assigned: jdunn)

Details

Attachments

(2 files, 1 obsolete file)

Currently the build system is setup for building on 11.00 hpux, however we want to add 11.11. There are several files that hardcode B.11.00 as the OS_RELEASE and we need to expand to include B.11.11
Attached patch nspr changesSplinter Review
wtc if you can review these that would be great. We don't expect you to pick up support but we would like to be able to build on 11.11 platform.
Status: NEW → ASSIGNED
QA Contact: granrose → jdunn
Comment on attachment 55121 [details] [diff] [review] nspr changes The NSPR changes are fine. HP-UX.mk is now a historical file so it doesn't need to be modified. cls, is there a way to test for B.11.* in the configure script?
Attachment #55121 - Flags: review+
Comment on attachment 55122 [details] new security coreconf file - same as HP-UXB.11.00.mk There are references to 11.00 in this file that should be changed to 11.11. The copyright year probably should say 2001.
Attachment #55122 - Flags: needs-work+
wtc, yes, we can. We would need to remove the hardcoded OS_RELEASE tests and convert them to using a case switch with ${target_os} which doesn't have the A.,B. prefixes.
Actually, you may be able to just replace the egrep '^(B.11.00|B.11.11)' with egrep '^B.11' to simulate the B.11.* . Using B.11 should work for the $(filter) rules as well.
Using B.11 is probably NOT a good idea. Without going into TOO much detail... if a 11.70 came along that was radically different we would have to re-write. Right now 11.11 & 11.00 are basically the same (I still can't figure out the differences)
Well, if it was that different, we'd have to update the config anyway, right? If we used B.11, then we wouldn't have to update anything for future releases that weren't radically different.
Comment on attachment 55135 [details] 11.11.mk file for security coreconf (updated) I will change the copyright notice to say just 2001. Other than that, this is fine. r=wtc.
Attachment #55135 - Flags: review+
Attachment #55122 - Attachment is obsolete: true
I checked in the NSPR changes on both the NSPRPUB_PRE_4_2_CLIENT_BRANCH and the tip. I added security/coreconf/HP-UXB.11.11.mk to both the tip and NSS_3_3_BRANCH and tag the revision on NSS_3_3_BRANCH as NSS_CLIENT_TAG. Marked the bug fixed.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: