Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2019-05-08
Date: Mon, 13 May 2019 13:31:46 +0200	[thread overview]
Message-ID: <20190513133146.7a011b13@windsurf.home> (raw)
In-Reply-To: <8fd5700b-d81b-71da-7edb-c32248a32a4f@free.fr>

Hello,

On Mon, 13 May 2019 13:20:54 +0200
Julien Boibessot <julien.boibessot@free.fr> wrote:

> I have already brought this problem up a few times before but no one has
> a clue.
> My build system is consuming 100% CPU in conftest process when building
> libsodium.
> 
> In this state I have to manually kill all conftest processes otherwise
> the build is blocked for days... :-)

Which configure test is it running when it's blocked ? What does
"strace" says about this conftest process that is stuck ?

Can  you reproduce manually ? Does it happen every time libsodium is
built on your machine, or only once in a while ?

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-05-13 11:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09  6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2019-05-08 Thomas Petazzoni
2019-05-09 21:03 ` Thomas Petazzoni
2019-05-09 21:19   ` Giulio Benetti
2019-05-11 21:00     ` Giulio Benetti
2019-05-14 20:36       ` Yann E. MORIN
2019-05-14 21:47         ` Giulio Benetti
2019-05-09 21:41   ` LP C
2019-05-10  8:59   ` Vadym Kochan
2019-05-13 11:20   ` Julien Boibessot
2019-05-13 11:31     ` Thomas Petazzoni [this message]
2019-05-13 15:59       ` Julien Boibessot
2019-05-25 15:31         ` Arnout Vandecappelle
2019-05-26 14:08           ` LP C
2019-05-26 18:36             ` Thomas Petazzoni
2019-05-23  7:07   ` Nylon Chen

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=20190513133146.7a011b13@windsurf.home \
    --to=thomas.petazzoni@bootlin.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