public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 142 build error with dnsdist
Date: Sat, 11 Apr 2020 14:03:49 +0200	[thread overview]
Message-ID: <83df67daa4134e430d88b5a847a78a10398bcc26.camel@ipfire.org> (raw)
In-Reply-To: <2C7B78D3-C486-4479-A5B8-3EAEDADF923A@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 3075 bytes --]

Am Samstag, den 11.04.2020, 12:01 +0100 schrieb Michael Tremer:
> 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.
OK, will give it may a try.

> 
> 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.
Yeah, will need a new machine for this since my good old JNC9C eats 3GB
max :-| . But may some day the Weihnachtsmann comes via wormhole a
little earlier and funds some new hardware ;-) .

> 
> Best,
> -Michael

Thanks. Best,

Erik

> 
> > On 4 Apr 2020, at 16:03, ummeegge <ummeegge(a)ipfire.org> 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 <ummeegge(a)ipfire.org> 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 <bug-make(a)gnu.org>
> > > >   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
> > > > 
> > > 
> > > 
> 
> 


      reply	other threads:[~2020-04-11 12:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-04  7:04 ummeegge
2020-04-04 13:51 ` Michael Tremer
2020-04-04 15:03   ` ummeegge
2020-04-11 11:01     ` Michael Tremer
2020-04-11 12:03       ` ummeegge [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83df67daa4134e430d88b5a847a78a10398bcc26.camel@ipfire.org \
    --to=ummeegge@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox