Closed
Bug 88102
Opened 24 years ago
Closed 24 years ago
Define _PR_HAVE_SOCKADDR_LEN only when _SOCKADDR_LEN is defined
Categories
(NSPR :: NSPR, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
4.2
People
(Reporter: colin, Assigned: wtc)
Details
Attachments
(1 file)
|
508 bytes,
patch
|
Details | Diff | Splinter Review |
Building would be a lot easier for me if _PR_HAVE_SOCKADDR_LEN only got defined
when _HAVE_SOCKADDR_LEN was defined. I'll attach a patch (from my 0.9.2 tree) next.
|
Reporter | |
Updated•24 years ago
|
Summary: Define _PR_HAVE_SOCKADDR_LEN only when _HAVE_SOCKADDR_LEN is defined → Define _PR_HAVE_SOCKADDR_LEN only when _SOCKADDR_LEN is defined
|
|
Reporter | |
Comment 1•24 years ago
|
||
|
Assignee | |
Comment 2•24 years ago
|
||
How are you going to define _SOCKADDR_LEN?
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → 4.2
|
|
Reporter | |
Comment 3•24 years ago
|
||
Its defined here:
http://lxr.mozilla.org/seamonkey/source/nsprpub/configure.in#1224
so a normal build is BSD V4.4 style sockets.
But when I need to rebuild for BSD V4.3, a quick remove of -D_SOCKADDR_LEN=1
from OBJDIR/nsprpub/config/autoconf.mk, and I'm all set!
|
|
Reporter | |
Comment 4•24 years ago
|
||
Can this get checked in some time soon?
|
|
Assignee | |
Comment 5•24 years ago
|
||
Yes, sir!
Patch checked in on the tip of NSPR. Moved the NSPRPUB_CLIENT_TAG
to include the new rev.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•