Closed
Bug 302317
Opened 19 years ago
Closed 19 years ago
link error in xpcom_core.dll - unresolved symbol NS_NewStaticComponentLoader
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: markus.doehr, Assigned: dougt)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322) Build Identifier: /cygdrive/c/mozillasrc/phoenix/mozilla/build/cygwin-wrapper link -NOLOGO -DLL - OUT:xpcom_core.dll -P DB:xpcom_core.pdb -SUBSYSTEM:WINDOWS nsCOMPtr.obj nsComponentManagerUtils.obj nsDebug.obj nsIInterf aceRequestorUtils.obj nsMemory.obj nsTraceRefcnt.obj nsWeakReference.obj nsGREGlue.obj nsGenericFact ory.obj nsXPComInit.obj nsStringAPI.obj dlldeps.obj ../../dist/lib/xpcomds_s.lib ../../dist/lib/xpco mio_s.lib ../../dist/lib/xpcomcomponents_s.lib ../../dist/lib/xpcomthreads_s.lib ../../dist/lib/xpco mproxy_s.lib ../../dist/lib/xpcombase_s.lib ../../dist/lib/xptcall.lib ../../dis t/lib/xptinfo.lib .. /../dist/lib/xpt.lib ../../dist/lib/xptcmd.lib ../../dist/lib/string_s.lib ./m odule.res ../../ dist/lib/xpcomds_s.lib ../../dist/lib/xpcomio_s.lib ../../dist/lib/xpcomcomponen ts_s.lib ../../dist/ lib/xpcomthreads_s.lib ../../dist/lib/xpcomproxy_s.lib ../../dist/lib/xpcombase_ s.lib ../../dist/lib /xptcall.lib ../../dist/lib/xptinfo.lib ../../dist/lib/xpt.lib ../../dist/lib/xp tcmd.lib ../../dist/ lib/string_s.lib ../../dist/lib/nspr4.lib ../../dist/lib/plc4.lib ../../dist/ lib/plds4.lib shell 32.lib ole32.lib uuid.lib version.lib kernel32.lib user32.lib gdi32.lib winmm.lib wsock32.lib advapi 32.lib Creating library xpcom_core.lib and object xpcom_core.exp xpcomcomponents_s.lib(nsComponentManager.obj) : error LNK2019: unresolved external symbol "unsigned int __cdecl NS_NewStaticComponentLoader(class nsIComponentLoader * *)" (? NS_NewStaticComponentLoader @@YAIPAPAVnsIComponentLoader@@@Z) referenced in function "public: unsigned int __thiscall nsComponen tManagerImpl::Init(void)" (?Init@nsComponentManagerImpl@@QAEIXZ) xpcom_core.dll : fatal error LNK1120: 1 unresolved externals make[4]: *** [xpcom_core.dll] Error 96 make[4]: Leaving directory `/cygdrive/c/mozillasrc/phoenix/mozilla/xpcom/build' make[3]: *** [libs] Error 2 make[3]: Leaving directory `/cygdrive/c/mozillasrc/phoenix/mozilla/xpcom' make[2]: *** [tier_2] Error 2 make[2]: Leaving directory `/cygdrive/c/mozillasrc/phoenix/mozilla' make[1]: *** [default] Error 2 make[1]: Leaving directory `/cygdrive/c/mozillasrc/phoenix/mozilla' make: *** [build] Error 2 my mozconfig: . $topsrcdir/browser/config/mozconfig mk_add_options MOZ_CVS_FLAGS=-q #mk_add_options MOZ_CO_LOCALES=de-DE #mk_add_options LOCALES_CVSROOT=:ext:cltbld@cvs.mozilla.org:/l10n GLIB_PREFIX=/cygdrive/c/mozillasrc/toolsstatic LIBIDL_PREFIX=/cygdrive/c/mozillasrc/toolsstatic ac_add_options --enable-crypto #ac_add_options --enable-activex-scripting ac_add_options --disable-debug ac_add_options --enable-optimize ac_add_options --disable-tests ac_add_options --enable-static ac_add_options --disable-shared #ac_add_options --enable-official-branding ac_add_options --enable-application=browser I'm using VS .NET 2003 C:\mozillasrc\phoenix>cl Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 13.10.3077 for 80x86 Copyright (C) Microsoft Corporation 1984-2002. All rights reserved. This happens everytime - with 1_0_6_RELEASE, 1a2_RELEASE and with HEAD. I set up a fresh PC with fresh environment. Am I missing something obvious? Reproducible: Always
Assignee: mscott → nobody
Product: Thunderbird → Core
QA Contact: chase → build-config
Version: unspecified → Trunk
Assignee: nobody → dougt
Component: Build Config → XPCOM
QA Contact: build-config → xpcom
Comment 1•19 years ago
|
||
You must not be checking out the sources correctly on HEAD, because there is no NS_NewStaticComponentLoader function on the trunk any more: http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&file=nsStaticComponentLoader.cpp&branch=&root=/cvsroot&subdir=mozilla/xpcom/components&command=DIFF_FRAMESET&rev1=3.22&rev2=3.23
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 2•19 years ago
|
||
sorry for reopening but... what about the other three trees? Neither of them is working FIREFOX_1_1a2_RELEASE FIREFOX_1_0_6_RELEASE FIREFOX_1_0_5_RELEASE Same error there...
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Comment 3•19 years ago
|
||
Markus, I don't know, but I know that many many people have been building those source trees without a problem, and we won't make changes to them anyway.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•