Closed Bug 419481 Opened 12 years ago Closed 12 years ago

moz2 builds are broken

Categories

(Release Engineering :: General, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: bhearsum)

Details

mozilla-central-linux is having checkout conflicts with nsprpub/configure
mozilla-central-win32 fails with this error:
make[4]: Leaving directory `/e/builds/moz2-slave/mozilla-central-win32/build/obj-firefox/js/src/fdlibm'
make[4]: Entering directory `/e/builds/moz2-slave/mozilla-central-win32/build/obj-firefox/js/src'
link -NOLOGO -DLL -OUT:js3250.dll -PDB:js3250.pdb -SUBSYSTEM:WINDOWS  jsapi.obj jsarena.obj jsarray.obj jsatom.obj jsbool.obj jscntxt.obj jsdate.obj jsdbgapi.obj jsdhash.obj jsdtoa.obj jsemit.obj jsexn.obj jsfun.obj jsgc.obj jshash.obj jsinterp.obj jsiter.obj jslock.obj jslog2.obj jslong.obj jsmath.obj jsnum.obj jsobj.obj jsopcode.obj jsparse.obj jsprf.obj jsregexp.obj jsscan.obj jsscope.obj jsscript.obj jsstr.obj jsutil.obj jsxdrapi.obj jsxml.obj prmjtime.obj    js3240.res -NXCOMPAT -SAFESEH    -OPT:NOICF  ../../dist/lib/nspr4.lib ../../dist/lib/plc4.lib ../../dist/lib/plds4.lib  kernel32.lib user32.lib gdi32.lib winmm.lib wsock32.lib advapi32.lib   
jsapi.obj : MSIL .netmodule or module compiled with /GL found; restarting link with /LTCG; add /LTCG to the link command line to improve linker performance
   Creating library js3250.lib and object js3250.exp
jslock.obj : error LNK2001: unresolved external symbol "long __cdecl _Interlock
I'm out sick today, I'll have a look at this (hopefully) tomorrow.
Priority: -- → P3
I see that NSPR was updated on February 21st (and merged into mozilla-central on the 22nd). I bet this is why there is checkout conflicts. I manually clobber nsprpub/configure and it seems to be going OK now. I don't think there's any need to clobber it every time, or anything like that.

On to win32...
I'm trying a build manually but I wonder if this is legitimate failure. Does anyone build mozilla-central on a regular basis?
It shouldn't *hurt* to clobber configure every time, because we regenerate it during the build now anyway... perhaps we shouldn't do that by default, but we do for the moment.
Sorry, I was talking about building mozilla-central on *win32* in comment#3.

w.r.t configure, it was nsprpub/configure that had conflicts, likely because of the recent nspr upgrade.
Doing a manual build of mozilla-central on win32 gives me the same error...not sure where to go from here.
win32 appears to be broken on mozilla-central. It's a code error, you may ignore it until we fix the code.
OK, thanks for confirming that.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.