Thanks, Ole, misery loves company:-) The only question I'd ask about your build change is whether build-root/Makefile should be modified to allow command line args, or whether it should stay as is and you write the configuration options into a locally modified copy of build-data/platforms/$(PLATFORM).mk. Maybe a question for Dave. (I see an example of vpp_configure_args_vpp in build-data/platforms.vpp.mk.) Actually, I personally am leaning towards using the file -- I think it plays better with the ebuild mechanism that senses if you changed the file -- that tells ebuild that configuration has to be redone -- I am pretty sure.
Burt On Wed, Nov 1, 2017 at 6:33 PM, Ole Troan <otr...@employees.org> wrote: > Burt et al, > > > I hadn't built new code in a few weeks. I have a machine with 8 > hyperthreads, and I have only 8GB memory minus what is used for hugepages. > I ran out of virtual memory when doing a build, in the new C++ code. Just a > heads up for anyone without huge memory per processor thread. My work > around is going into build-root/Makefile and halving the number of > MAKE_PARALLEL_JOBS. There is a number 2 that can be changed to 1 in case > anybody is using a modest build machine. > > I ran into the same issue with my 2G VPP in a box E3845 system. > > I pushed patch https://gerrit.fd.io/r/#/c/9186/ > As a way of passing autoconf flags from the make command line. > E.g.: > make CONFIGURE_ARGS="--disable-pppoe-plugin --disable-nat-plugin > --disable-lb-plugin --disable-japi --disable-vapi --disable-vom > --disable-stn-plugin" build > > I've -2'ed for now, awaiting someone more clue'd up about the build system > than me. > > Best regards, > Ole > >
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
