Gerald, To me this looks like a terribly crippled environment to build ceph, and I won’t bother building in such environment. IMO, It’s not worth for anybody to optimize the build process to make it work on such a crippled environment. And to answer your question, If you can not add more memory then provide more swap space to increase the virtual memory. You can also remove the “-j" parameter to “make" in the spec file to avoid creating lot of processes for parallel build. Nitin > On Jul 28, 2016, at 6:50 PM, Gerard Braad <me@xxxxxxxxx> wrote: > > Hi All, > > > At the moment I am setting up CI pipelines for Ceph and ran into a > small issue; I have some memory constrained runners (2G). So, when > performing a build using do-cmake all is fine... the build might last > long, but after an hour or two I am greeted with a 'Build succeeded' > message, I gather the artifacts and all is well. > > But when I do a rpmbuild, I have to rely on doing a make-dist, and > then issue a rpmbuild targeting this tarball. However, in the same > runners, this build will fail with "virtual memory exhausted". Is > there anything I can do that does not immediately involve adding more > memory? > > If more information is needed, please let me know... > > regards, > > > Gerard > > -- > > Gerard Braad | http://gbraad.nl > [ Doing Open Source Matters ] > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |