Hello Nadav/All, I see, well, I have not set any jobs which means it is equivalent to -j1 As for the building, I was not running any other software, just make and the ssh (connected over putty) As you deduced, I didn't setup a swap (otherwise the performance would be horrible here, still using old disks here)
Maybe we could change the approach and just print a warning that 2 GB of RAM and 3 GB of disk is recommended? Kind Regards, Geraldo Netto Sapere Aude => Non dvcor, dvco http://exdev.sf.net/ On 22 February 2018 at 05:38, Nadav Har'El <n...@scylladb.com> wrote: > > On Thu, Feb 22, 2018 at 6:02 AM, geraldo netto <geraldone...@gmail.com> > wrote: >> >> this will avoid people having such situation below: >> ... >> CXX core/commands.cc >> virtual memory exhausted: Cannot allocate memory > > > I'm not comfortable with saying just that "2 GB of memory is needed for the > compilation". What is this number based on? For example, it strongly depends > on how much compilation you do in parallel, e.g., if "make -j4" doesn't > work, because it compiles 4 source files in parllel, probably "make -j1" > would. What "-j" option did you try? Also the amount of memory you need also > depends on what else you have running on your machine - and whether you have > swap (I guess you had none). > > Nobody would set up a physical host today with just 1 GB of memory. A local > shop here which I recently went to sells its most basic setups with 4 GB. > And if you set up a VM with just 1 GB of memory and no swap, isn't it > obvious that if you get errors like "virtual memory exhausted" you need to > increase your memory? > > By the way, something which is more deterministic and perhaps more > surprising that memory usage is the build's disk usage. Users should have at > least 3 GB of free disk space, because of some surprising disk usage of the > git files (700 MB) and the "external" directory (1.2 GB). > >> >> make: *** [build/release.x64/core/commands.o] Error 1 >> Makefile:363: recipe for target 'build/release.x64/core/commands.o' failed >> make failed. Exiting from build script >> >> VM configuration: >> VMWare player >> 2 vCPUs >> 8 GB of disk >> 1 GB of RAM (changing to 2 GB solves the problem) >> Debian 9.3 >> --- >> README.md | 4 ++-- >> 1 file changed, 2 insertions(+), 2 deletions(-) >> >> diff --git a/README.md b/README.md >> index f68bee5..d08a10c 100644 >> --- a/README.md >> +++ b/README.md >> @@ -23,6 +23,8 @@ https://github.com/cloudius-systems/osv/wiki >> OSv can only be built on a 64-bit x86 Linux distribution. Please note >> that >> this means the "x86_64" or "amd64" version, not the 32-bit "i386" >> version. >> >> +Compilation requires at least 2GB of RAM. >> + >> If you wish, you can run the script 'scripts/setup.py' as root to install >> all dependencies. >> Otherwise, you may follow the manual instructions below. >> >> @@ -39,8 +41,6 @@ Debian stable(wheezy) requires to compile gcc, gdb and >> qemu. >> And also need to configure bridge manually. >> >> More details are available on wiki page: >> -[Building OSv on Debian stable][] >> - >> [Building OSv on Debian stable]: >> https://github.com/cloudius-systems/osv/wiki/Building-OSv-on-Debian-stable >> >> **Debian testing(jessie)** >> -- >> 2.7.4 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "OSv Development" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to osv-dev+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. > > -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to osv-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
