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] [autobuild.buildroot.net] Build results for 2017-02-16
Date: Tue, 21 Feb 2017 09:27:54 +0100	[thread overview]
Message-ID: <20170221092754.3dd7bc65@free-electrons.com> (raw)
In-Reply-To: <b94b135b-35c2-ad80-9a99-f14ebfea1e06@mind.be>

Hello,

On Tue, 21 Feb 2017 09:05:01 +0100, Arnout Vandecappelle wrote:

>  Perhaps for the timeout, it would make sense to do a setrlimit(RLIMIT_CPU) in
> addition to the monitor. That way you avoid that a single compile stays stuck
> for 7 hours. Though admittedly at the moment it happens sufficiently rarely to
> not be too much of a waste.

So doing "ulimit -t 60" will for example prevent a single process from
getting more than 60 seconds of CPU time ?

But I agree, it doesn't happen that often, so probably not worth the
effort.

> >>>         sh4a |                  opencv-2.4.13 | NOK | http://autobuild.buildroot.net/results/2944568f9623f1377e987a1dadde5ea8cc428c5f    
> >>
> >>     error: 'SIZE_MAX' was not declared in this scope
> >>
> >> Missing header? Samuel?  
> > 
> > This is the same issue as the one fixed for libraw in
> > d246cf5fd01bb0d20a0e64194ffed514ea8dd0aa. It's annoying that the issue
> > is in the jasper package, but we have to fix it in all packages using
> > jasper. Not sure what can be done about it though.  
> 
>  Actually, only the packages that use C++. AFAICS that's just kodi, libraw,
> opencv and opencv3.

Correct. But still, that's a bit annoying to have to change all the
consumers of a package.

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

  reply	other threads:[~2017-02-21  8:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17  7:28 [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-16 Thomas Petazzoni
2017-02-17 21:12 ` Yann E. MORIN
2017-02-17 22:01   ` Yann E. MORIN
2017-02-17 22:02   ` Waldemar Brodkorb
2017-02-18  8:49   ` Peter Korsgaard
2017-02-20 12:41   ` Thomas Petazzoni
2017-02-20 14:59     ` Waldemar Brodkorb
2017-02-20 15:10       ` Thomas Petazzoni
2017-02-20 18:14     ` Bernd Kuhls
2017-02-20 22:40     ` Peter Korsgaard
2017-02-20 22:46       ` Thomas Petazzoni
2017-02-20 22:59         ` Peter Korsgaard
2017-02-21  8:05     ` Arnout Vandecappelle
2017-02-21  8:27       ` Thomas Petazzoni [this message]
2017-02-21  8:46         ` Arnout Vandecappelle
2017-02-21  8:55           ` Thomas Petazzoni
2017-02-24 14:37   ` Julien Boibessot
2017-02-24 14:48     ` Thomas Petazzoni
2017-02-25  1:47       ` Waldemar Brodkorb

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=20170221092754.3dd7bc65@free-electrons.com \
    --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