Closed Bug 724490 Opened 8 years ago Closed 8 years ago

Comment out the -jN lines in the .mozconfigs for each branch

Categories

(SeaMonkey :: Release Engineering, defect)

x86
Windows Server 2003
defect
Not set

Tracking

(seamonkey2.7 fixed, seamonkey2.8 fixed, seamonkey2.9 fixed)

RESOLVED FIXED
seamonkey2.10
Tracking Status
seamonkey2.7 --- fixed
seamonkey2.8 --- fixed
seamonkey2.9 --- fixed

People

(Reporter: ewong, Assigned: ewong)

Details

Attachments

(1 file)

With the move to iX machines, the Win32 builders' mozconfigs have a higher
-jN set.  Just comment out these lines or remove -jN if there are other
flags mentioned.
Assignee: nobody → ewong
Status: NEW → ASSIGNED
OS: Windows Vista → Windows Server 2003
Addendum:  Ignore comm-1.9.1 and comm-2.0. (Obsolete branches).
Attachment #594662 - Flags: review?(kairo)
Attachment #594662 - Flags: review?(bugspam.Callek)
Attachment #594662 - Flags: review?(kairo)
Attachment #594662 - Flags: review?(bugspam.Callek)
Attachment #594662 - Flags: review+
Pushed to buildbot-configs:
http://hg.mozilla.org/build/buildbot-configs/rev/c214a2c6dea1
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Actually, I'm not sure that going to -j1 implicitly is a better idea than to use at least two parallel processes. :-/
Fwiw, I had checked this not long ago, and iirc:
*Firefox uses -j1 (with gnu make) on Windows.
*https://developer.mozilla.org/en/Windows_Build_Prerequisites
 "Parallel builds (-jN) do not work with GNU make on Windows. You need to use pymake instead."
Flags: in-testsuite-
Target Milestone: --- → seamonkey2.10
Version: SeaMonkey 2.8 Branch → Trunk
You need to log in before you can comment on or make changes to this bug.