On 28/11/2013 10:57, Neil wrote:
I often build in a VM. I allocate 2 CPUs and 2GB of RAM to it, which seems to be enough even to link xul.dll with debug symbols, although it takes a few minutes. (Linking it without symbols takes just seconds.) Given the amount of memory needed to link I haven't considered the case of running out of RAM during compiling, although I did manage to run out of virtual disk space for temporary files when I accidentally built with -j instead of -j3.
I assume this was a Firefox for Windows build, correct? This week I found an issue that causes FxOS's gecko to be built with -j16 irrespective of the number of jobs you specify on the command-line or in the .config file. That's likely the cause for some of these issues; fortunately it's FxOS-specific. I'm fixing this problem as part of bug 888698.
Gabriele _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
