Closed Bug 102922 Opened 23 years ago Closed 22 years ago

get rid of -B symbolic linker option

Categories

(JSS Graveyard :: Library, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jamie-bugzilla, Assigned: jamie-bugzilla)

Details

Currently, libjss3.so is linked with the "-B symbolic" linker option. It is set
in mozilla/security/jss/config/config.mk.

This linker option does the following, according to the Solaris man page:

     -B symbolic
           In dynamic mode only. When building a  shared  object,
           binds  references  to  global symbols to their defini-
           tions, if  available,  within  the  object.  Normally,
           references to global symbols within shared objects are
           not bound  until  runtime,  even  if  definitions  are
           available,  so  that definitions of the same symbol in
           an executable or other shared object can override  the
           object's  own  definition.  ld will issue warnings for
           undefined symbols unless -z defs overrides.

This just doesn't seem to be an issue, since I don't anticipate any other
library trying to override the symbols in libjss3.so. The only symbols exported
by libjss are JNI methods (Java_org_mozilla_jss_*).

NSS does not use this option either.
This bug causes OSF1 builds to break, as documented in
http://bugzilla.mozilla.org/show_bug.cgi?id=101609
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → 3.2
Target Milestone: 3.2 → 3.2.1
Fixed on JSS_3_2_BRANCH.

/cvsroot/mozilla/security/jss/config/config.mk,v  <--  config.mk
new revision: 1.6.2.1; previous revision: 1.6
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Rename JSS 3.2.1 to JSS 3.3.
Target Milestone: 3.2.1 → 3.3
You need to log in before you can comment on or make changes to this bug.