Closed
Bug 126932
Opened 23 years ago
Closed 21 years ago
NSPR tests don't run on OS/2
Categories
(NSPR :: NSPR, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
4.4
People
(Reporter: julien.pierre, Assigned: wtc)
References
Details
Attachments
(2 files, 3 obsolete files)
716 bytes,
patch
|
Details | Diff | Splinter Review | |
1.05 KB,
patch
|
Details | Diff | Splinter Review |
Right now they don't even build on OS/2.
Reporter | ||
Updated•23 years ago
|
Comment 1•22 years ago
|
||
This is all that is needed - use $(LD) instead of $(LINK)
Reporter | ||
Comment 2•22 years ago
|
||
Now that the tests are building, we need to run runtests.ksh . The standard mozilla OS/2 tools don't appear to include ksh. Mike, do you know which one we should use ? Also, I think runtests.ksh will need some modifications for OS/2 in order to pick the correct tests to run.
Comment 3•21 years ago
|
||
runtests.sh should be used - it needs to be modified. You also need printf and basename from gnusutils.
Comment 4•21 years ago
|
||
Might as well put two fixes in - attach test is totally broke for os/2
Attachment #118645 -
Attachment is obsolete: true
Comment 5•21 years ago
|
||
No idea why this is working for other platforms. tmocon.c says that #includes are needed for getcwd
Assignee | ||
Comment 6•21 years ago
|
||
Michael, please update your patches against the current NSPR client branch.
Status: NEW → ASSIGNED
Target Milestone: 4.2 → ---
Comment 7•21 years ago
|
||
Sorry, I didn't realize some of this went in. This puts one more OS/2 in the .sh file and fixes an include problem in thrpool_server.c Once these changes are in, this bug is done.
Attachment #118648 -
Attachment is obsolete: true
Attachment #118649 -
Attachment is obsolete: true
Assignee | ||
Comment 8•21 years ago
|
||
Patch checked into the NSPR TIP and client branch.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Whiteboard: [4.3.1]
Target Milestone: --- → 4.3
Assignee | ||
Updated•21 years ago
|
Whiteboard: [4.3.1]
Target Milestone: 4.3 → 4.4
You need to log in
before you can comment on or make changes to this bug.
Description
•