On 2018-11-06 13:51, Christopher Gregory via blfs-support wrote:
Hello,
I have just built WebKitGTK+-2.22.3 and it was the most unpleasant
experience I have ever had with building blfs. The build killed off
the process a total of 4 times due to running out of memory. I have a
6 core machine and 8 gig of ram with a swap partition of 6 gigs.
This is the first time that ninja has been used in the build process,
so I do not know if that is the problem or not. This is my first
build on an ssd drive, so I have no idea if swap even gets used as an
ssd drive is basicly a giant flash drive.
With this build I did not even have a gui running. This was done
solely from directly on console. Also no xwindows.
The build time was also considerably longer, at about 7 hours. On all
my other builds of webkit I have done them either in chroot, or via a
terminal in lxde.
I think for the next build I will be dropping ninja and directly using
cmake with make install.
Has anyone else had this experience with building webkit with ninja?,
or has webkit grown so obese that it now requires more than 8 gigs of
ram to compile?
Regards,
Christopher
Try using "export NINJAJOBS=1" and recompile WebKit.
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
