Closed
Bug 298494
Opened 19 years ago
Closed 15 years ago
XPI_NAME's static-override doesn't get correct XPCOM_TRANSLATE_NSGM_ENTRY_POINT setting
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
mozilla1.8beta3
People
(Reporter: abwillis1, Unassigned)
References
Details
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
Updated•19 years ago
|
Component: Base → Build Config
Product: Calendar → Core
Target Milestone: --- → mozilla1.8beta3
Version: unspecified → Trunk
Comment 1•19 years ago
|
||
Shaver, didn't you fix this?
Reporter | ||
Comment 2•19 years ago
|
||
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.
Updated•15 years ago
|
QA Contact: base → build-config
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
Updated•7 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•