[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
I built it with no problems whatsoever on a Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz with 4GB, hardly a supercomputer... Seamonkey works also fine on the same laptop, though. It took longer for Thunderbird and LibreOffice, but they also work fine.
Now if there was somebody to tell me if they have ever been able to compile lang/mono, I'll be happy - I've been having the same failures for the last six months, on all my -current build machines.
It's a sad day, but apparently I now must admit that my computer is no longer powerful enough to build the latest Firefox.
I'm running a computer with an Intel Core 2 P8600, with 2G of physical memory, and plenty of disk space. The system is NetBSD 8.99.3, (Current), and I'm using GCC 5.4 as the compiler.
When compiling Firefox, the system chugs away until it start to compile components. It gets to the "servo/components/style" part, and that's when things get ugly. As it starts crunching, the memory allocation moves up to about 80%. Then the swap file starts growing. The swap partition is about 2.2G in size. Slowly, but surely, this starts growing until it gets to 100%, and then I get a resource error #32. Wow!
I guess I'll switch over to Seamonkey, and see it that works.
Main Index |
Thread Index |