From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3 v2] infra/pkg-golang: enforce number of parallel jobs
Date: Mon, 03 Dec 2018 23:12:22 +0100 [thread overview]
Message-ID: <877egq2rax.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <951dd893ccaa0d4a894bfcac76dc04e28d9acafb.1543137559.git.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Sun, 25 Nov 2018 10:19:48 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> By default, the go compiler will spawn as many jobs as there are CPUs
> available, thus possibily over-shooting the limits set by the user.
> Make it abide by the user's wish, and specify the number of jobs allowed
> to run.
> We can do so without fear of a package failing to build in parallel,
> because they were already all building in parallel, as that is the
> default for the go compiler.
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Committed to 2018.08.x, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-12-03 22:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-25 9:19 [Buildroot] [PATCH 0/3 v2] golang: fix build with oldish codesourcery amd64 toolchain (branch yem/go-west) Yann E. MORIN
2018-11-25 9:19 ` [Buildroot] [PATCH 1/3 v2] infra/pkg-golang: enforce number of parallel jobs Yann E. MORIN
2018-11-27 17:42 ` Arnout Vandecappelle
2018-11-27 17:55 ` Yann E. MORIN
2018-12-03 22:12 ` Peter Korsgaard [this message]
2018-11-25 9:19 ` [Buildroot] [PATCH 2/3 v2] toolchain: CodeSourcery AMD64 affected by PR20006 Yann E. MORIN
2018-12-03 22:13 ` Peter Korsgaard
2018-11-25 9:19 ` [Buildroot] [PATCH 3/3 v2] package: hide golang packages for toolchains with binutils bug 20006 Yann E. MORIN
2018-12-03 22:13 ` Peter Korsgaard
2018-11-29 20:24 ` [Buildroot] [PATCH 0/3 v2] golang: fix build with oldish codesourcery amd64 toolchain (branch yem/go-west) Peter Korsgaard
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=877egq2rax.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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