Closed Bug 2190 Opened 26 years ago Closed 26 years ago

[PP] NSPR building incorrectly on FreeBSD 3.0

Categories

(NSPR :: NSPR, defect, P1)

Other
Other
defect

Tracking

(Not tracked)

CLOSED FIXED

People

(Reporter: tague, Assigned: wtc)

Details

The current NSPR release (NSPRPUB_RELEASE_3_0) is building incorrectly on FreeBSD 3.0. On FreeBSD 3.0, there must be a libfoo.so to link against. FreeBSD will not use libfoo.so.1.0. The NSPR build scripts need to generate symbolic links for libnspr21.so libplc21.so and libpld21.so linking them back to their *.so.1.0 counterparts.
Severity: normal → critical
Summary: NSPR building incorrectly on FreeBSD 3.0 → [PP] NSPR building incorrectly on FreeBSD 3.0
Status: NEW → ASSIGNED
Tague, if you could figure out how to do this and send me a patch, I'd greatly appreciate it. Otherwise I'll take a look at it in my spare time.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Tague, sorry I didn't notice that you said "NSPRPUB_RELEASE_3_0". NSPRPUB_RELEASE_3_0 is a static CVS tag that does not move. Indeed, it does not build correctly on FreeBSD 3.0. This problem is already fixed on the tip by a patch contributed by Jeremy Lea. Jeremy's fix is to name the libraries libnspr21.so, libplc21.so, and libplds21.so. So there are no lib*.so.1.0 or symbolic links back to them. I am able to build and run NSPR test programs on your FreeBSD 3.0 machine angelus.mcom.com.
Thanks for getting these fixes in. When will there a stable release of nspr for Mozilla with these changes?
The next NSPR release (v3.1) is tentatively scheduled for the first week of March. Code freeze will begin very soon, around Feb. 1. We will announce our release schedule in the mailing lists. Mozilla client will start to pull the tip of NSPR during this period of time (about six weeks). Closed the bug.
Status: RESOLVED → CLOSED
Inserting Milestone info.
NSPR now has its own Bugzilla product. Moving this bug to the NSPR product.
Target Milestone: M2 → 3.1
Version: other → 3.0
You need to log in before you can comment on or make changes to this bug.