From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 142 build error with dnsdist
Date: Sat, 04 Apr 2020 14:51:39 +0100 [thread overview]
Message-ID: <60002E9E-84AA-4E32-B157-5702C0C4B7AA@ipfire.org> (raw)
In-Reply-To: <0d779f547bdfd8183f62d36029622975d2085c7a.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]
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
>
next prev parent reply other threads:[~2020-04-04 13:51 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 [this message]
2020-04-04 15:03 ` ummeegge
2020-04-11 11:01 ` Michael Tremer
2020-04-11 12:03 ` ummeegge
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=60002E9E-84AA-4E32-B157-5702C0C4B7AA@ipfire.org \
--to=michael.tremer@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