Closed Bug 104093 Opened 24 years ago Closed 23 years ago

retail xpfe linking to debug libraries - intl component

Categories

(SeaMonkey :: UI Design, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: jonsmirl, Assigned: paulkchen)

Details

I am building a non-debug version of xpfe and receive this link error when building on Windows. I receive it even after a clobber/install. I am building both debug/non-debug version on my system. Something is wrong in the xpfe build process, maybe a non-debug library is not getting copied when it should or something is wrong with complier flags. Debug build of XPFE has a similar problem. LINK : warning LNK4098: defaultlib "MSVCRTD" conflicts with use of other libs; u se /NODEFAULTLIB:library appcompintl_s.lib(nsCharsetMenu.obj) : error LNK2001: unresolved external symbol _NS_CheckThreadSafe appcompintl_s.lib(nsCharsetMenu.obj) : error LNK2001: unresolved external symbol _NS_CurrentThread appcompintl_s.lib(nsFontPackageHandler.obj) : error LNK2001: unresolved external symbol _NS_CurrentThread .\WIN32_O.OBJ\appcomps.dll : fatal error LNK1120: 2 unresolved externals NMAKE : fatal error U1077: 'link' : return code '0x460' Stop. NMAKE : fatal error U1077: 'C:\PROGRA~1\MICROS~1\VC98\BIN\NMAKE.EXE' : return co de '0x2' Stop. NMAKE : fatal error U1077: 'C:\PROGRA~1\MICROS~1\VC98\BIN\NMAKE.EXE' : return co de '0x2' Stop. NMAKE : fatal error U1077: 'C:\PROGRA~1\MICROS~1\VC98\BIN\NMAKE.EXE' : return co de '0x2' Stop. NMAKE : fatal error U1077: 'C:\PROGRA~1\MICROS~1\VC98\BIN\NMAKE.EXE' : return co de '0x2' Stop. NMAKE : fatal error U1077: 'C:\PROGRA~1\MICROS~1\VC98\BIN\NMAKE.EXE' : return co de '0x2' Stop.
pchen sez this works for him now. pls reopen if this is still an issue!
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
mass verification of WorksForMe bugs: to find all bugspam pertaining to this, set your search string to "IfItWorksForSlappyTheSquirrelThenItWFM". if you think this particular bug is *still* an open issue, please make sure of the following before reopening: a. that it's still a problem with ***recent trunk builds*** on the all appropriate platform[s] b. provide clear steps to reproduce (unless a good test case is already in the bug report), making sure it pertains to the original problem (avoid morphing as much as possible :)
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.