I do not see anything in the Bitbake manual for controlling how much memory Bitbake should consider itself entitled to consume in the development platform within which it runs. Running it on //Windows 7 64//i7-2620M//Virtualbox//Ubuntu 14 32-bit//, I told Virtualbox to allow Ubuntu to use 1.5 GBytes, but Windows Task Manager indicates the whole Virtualbox/Ubuntu thread is using only 160 MBytes -- and is generating approximately 1,000 page faults per second. Perhaps as a result, this Gumstix Overo build has completed only 760 out of 3792 total tasks in 21 hours -- at this rate it will complete in 5-6 days. How does the user terminate Bitbake at its current stage, increase the memory it is using, and then restart in order to speed up this process ?
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto