Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] package/nut: don't build in parallel
Date: Thu, 28 Dec 2017 22:54:41 +0100	[thread overview]
Message-ID: <20171228225441.0c24a8a1@windsurf> (raw)
In-Reply-To: <20171228134318.982-1-yann.morin.1998@free.fr>

Hello,

On Thu, 28 Dec 2017 14:43:18 +0100, Yann E. MORIN wrote:
> The conditions are not trivial to reproduce, but it can happen that the
> headers are not fully regenerated by the time they are included.
> 
> This only happens when a python and/or perl interpreter are available,
> with a high number of jobs and a high load.
> 
> Fixes:
>     http://autobuild.buildroot.org/results/523/5231ff39a0839ec5e1962662004214d4b0773068/
>     http://autobuild.buildroot.org/results/5a7/5a75d44c028e77b58f0fd9ab794952f2b477dd84/
> 
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Peter Korsgaard <peter@korsgaard.com>
> 
> ---
> Changes v1 -> v2:
>   - drop non-upstreamable patch, but just do not build in parallel (Peter)
> ---
>  package/nut/nut.mk | 3 +++
>  1 file changed, 3 insertions(+)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2017-12-28 21:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-28 13:43 [Buildroot] [PATCHv2] package/nut: don't build in parallel Yann E. MORIN
2017-12-28 21:54 ` Thomas Petazzoni [this message]
2017-12-28 22:17 ` Peter Korsgaard
2017-12-30 22:39 ` 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=20171228225441.0c24a8a1@windsurf \
    --to=thomas.petazzoni@free-electrons.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