Closed
Bug 167375
Opened 23 years ago
Closed 23 years ago
configuration changes needed for building on BSD/OS 5.0
Categories
(SeaMonkey :: Build Config, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.2beta
People
(Reporter: lidl, Assigned: netscape)
Details
Attachments
(1 file)
|
2.76 KB,
patch
|
netscape
:
review+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (X11; U; BSD/OS i386; en-US; rv:1.1) Gecko/20020827
Build Identifier: Mozilla/5.0 (X11; U; BSD/OS i386; en-US; rv:1.1) Gecko/20020827
Out of the box (ok, the tip of the CVS tree as of a couple of days ago)
the build/configuration system doesn't recoginize BSD/OS 5.0. Since 5.0
has more or less the same userland code as BSD/OS 4.3, it wasn't too
hard to wedge in recoginition for the system into Mozilla.
Reproducible: Always
Steps to Reproduce:
1. Checkout the source tree onto a BSD/OS 5.0 machine
2. Attempt a build.
3. Notice it fails.
Actual Results:
It doesn't build.
Expected Results:
It should build.
Since there isn't a place to attach a diff in this particular bugzilla
form, I'll attach the diffs needed to make it build in just a minute.
As promised, here are the patches to make Mozilla compile on BSD/OS 5.0.
| Assignee | ||
Updated•23 years ago
|
Priority: -- → P2
Target Milestone: --- → mozilla1.2beta
| Assignee | ||
Comment 2•23 years ago
|
||
Comment on attachment 98322 [details] [diff] [review]
patches for BSD/OS 5.0 building
Looks good to me. r=cls
Attachment #98322 -
Flags: review+
Comment 3•23 years ago
|
||
Comment on attachment 98322 [details] [diff] [review]
patches for BSD/OS 5.0 building
r=wtc. I've checked in the NSPR part of the
patch into the tip and NSPRPUB_PRE_4_2_CLIENT_BRANCH
of NSPR. I omitted the change to the obsolete
file mozilla/nsprpub/config/BSD_OS.mk.
| Assignee | ||
Comment 4•23 years ago
|
||
The configure.in change has been checked in.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•