Hmm, the make file already has 2GB per process set up. https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=lfs/dnsdist;h=9f2040f16583e033f624e24415953396a4d9e526;hb=HEAD#l40 So it will launch one compiler process per 2GB of memory. Obviously less than one isn’t possible. You can try filtering out “-pipe” from the CFLAGS and CXXFLAGS, so that the assembler will be stared after the compiler is done and not in parallel. That will also save a couple of megabytes, but probably not a massive lot. In general I can recommend to add more memory to your build system. 4GB seems to be a bit of a sweet spot. More than that normally does not make any difference. Best, -Michael > On 4 Apr 2020, at 16:03, ummeegge wrote: > > Hi Michael, > that´s my old build syste, with 2GB RAM > https://fireinfo.ipfire.org/profile/72d11e77621ec66ea75d39e3c9b10025e746e5af > > > Am Samstag, den 04.04.2020, 14:51 +0100 schrieb Michael Tremer: >> How much memory does your build system have? >> >>> On 4 Apr 2020, at 08:04, ummeegge wrote: >>> >>> Hi all, >>> the current build delivers an error with dnsdist: >>> >>> dnsdist >>> (1.4.0) >>> [ 17 ][ >>> FAIL ] >>> >>> -j [N], --jobs[=N] Allow N jobs at once; infinite jobs >>> with no arg. >>> -k, --keep-going Keep going when some targets can't >>> be made. >>> -l [N], --load-average[=N], --max-load[=N] >>> Don't start multiple jobs unless load is below N. >>> -L, --check-symlink-times Use the latest mtime between >>> symlinks and target. >>> -n, --just-print, --dry-run, --recon >>> . . . >>> Consider FILE to be infinitely new. >>> --warn-undefined-variables Warn when an undefined variable is >>> referenced. >>> >>> This program built for x86_64-pc-linux-gnu >>> Report bugs to >>> make: *** [dnsdist:84: /usr/src/log/dnsdist-1.4.0] Error 2 >>> >>> ERROR: Building >>> dnsdist >>> [ FAIL ] >>> >>> By commenting '$(MAKETUNING)' the build went through. Should it >>> prepare >>> a patch for this or is there may another solution ? >>> >>> Best, >>> >>> Erik >>> >> >> >