Closed Bug 298494 Opened 19 years ago Closed 14 years ago
_NAME's static-override doesn't get correct XPCOM _TRANSLATE _NSGM _ENTRY _POINT setting
When building sunbird statically on OS/2 we get an error during the process of building the xpi that _NSGetModule is unresolved in mozStorageModule.o. The xpi should be building non-static but is building statically, thus gModuleInfo_nsStorageModule is being built instead of NSGetModule. The #define in xpcom determines whether NS_IMPL_GETMODULENAME isNSGetModule or gModuleInfo_ XPI_NAME should trump static when XPI_NAME is set. XPI_NAME and IS_COMPONENT, if both set, make us build dynamic regardless of an --enable-static We set FORCE_STATIC_LIB= and FORCE_SHARED_LIB=1 but XPCOM_TRANSLATE_NSGM_ENTRY_POINT gets hit first. http://lxr.mozilla.org/mozilla/source/config/config.mk#333 http://lxr.mozilla.org/mozilla/source/config/config.mk#365
Component: Base → Build Config
Product: Calendar → Core
Target Milestone: --- → mozilla1.8beta3
Version: unspecified → Trunk
Shaver, didn't you fix this?
Sunbird no longer has this problem as they no longer build the xpi when building sunbird. I still get the error in static Seamonkey builds.
Assignee: shaver → nobody
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.