
<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 28 Mar 2018, at 14:19, Aurélien Larcher <<a href="mailto:aurelien.larcher@gmail.com" class="">aurelien.larcher@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div class="gmail_extra"><br class="Apple-interchange-newline"><br class=""><div class="gmail_quote">On Wed, Mar 28, 2018 at 1:05 PM, Marianne Spiller<span class="Apple-converted-space"> </span><span dir="ltr" class=""><<a href="mailto:marianne@spiller.me" target="_blank" class="">marianne@spiller.me</a>></span><span class="Apple-converted-space"> </span>wrote:<br class=""><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;">Hi,<br class=""><br class="">I'd like to re-compile my icinga2 package with the new oi-userland gcc6<br class="">behaviour; secret masterplan was to finally prepare the pull request.<br class="">With the gcc-4.9 version of oi-userland I got a working package.<br class=""><br class="">But using gcc-6 the package does not longer compile successfully; it<br class="">stops with the following error message:<br class="">[ 63%] Built target icinga-app<br class=""><br class="">cc1plus: out of memory allocating 2727788 bytes after a total of 85975040 bytes<br class="">make[3]: *** [lib/icinga/CMakeFiles/icinga.<wbr class="">dir/build.make:320:lib/icinga/<wbr class="">CMakeFiles/icinga.dir/icinga_<wbr class="">unity.cpp.o] Error 1<br class="">make[3]: Leaving directory '/scratch/oi-userland/<wbr class="">components/sysutils/icinga2/<wbr class="">build/amd64'<br class="">make[2]: *** [CMakeFiles/Makefile2:1656: lib/icinga/CMakeFiles/icinga.<wbr class="">dir/all] Error 2<br class="">make[2]: Leaving directory '/scratch/oi-userland/<wbr class="">components/sysutils/icinga2/<wbr class="">build/amd64'<br class="">make[1]: *** [Makefile:163: all] Error 2 make[1]: Leaving directory '/scratch/oi-userland/<wbr class="">components/sysutils/icinga2/<wbr class="">build/amd64' gmake: *** [/scratch/oi-userland/make-<wbr class="">rules/<a href="http://cmake.mk:167/" rel="noreferrer" target="_blank" class="">cmake.mk:167</a>: /scratch/oi-userland/<wbr class="">components/sysutils/icinga2/<wbr class="">build/amd64/.built] Error 2<br class=""><br class="">So what to do next? The host has 24GB RAM, 16 of them are available. No<br class="">strange ulimit settings as far as I can see - in fact it is a freshly<br class="">installed Hipster, no big changes made. </blockquote><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><br class="">Any help or idea would be great :)<br class=""></blockquote><div class=""><br class=""></div><div class="">How many build jobs (-j) did you specifiy with COMPONENT_BUILD_ARGS?<br class=""><br class=""></div><div class="">You output suggests that you are building with more than one.<br class="">I have just built version 2.8.2 successfully with -j1 on a machine with 48GB RAM (14 avaiable) but I could see that the compilation of icinga_<wbr class="">unity.cpp alone takes up to 1GB RAM.<span class="Apple-converted-space"> </span><br class=""></div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><br class=""></blockquote></div></div></div></div></blockquote><br class=""></div><div>Having nice amount of ram is good, but do not underestimate the value of the swap space. Make sure you have plenty for case the allocations are done with reservation and when you have /tmp filled.</div><div><br class=""></div><div>rgds,</div><div>toomas</div><br class=""></body></html>