Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-03-20
Date: Tue, 22 Mar 2016 07:50:12 +0100	[thread overview]
Message-ID: <4i67scxc49.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20160321073023.C428D1023A9@stock.ovh.net

Am Mon, 21 Mar 2016 08:30:23 +0100 schrieb Thomas Petazzoni:

> Build statistics for 2016-03-20
> ===============================
> 
>         success : 203
>        failures : 167
>        timeouts : 1  
>           TOTAL : 371
> 
> Classification of failures by reason
> ====================================
> 
>               gnuradio-3.7.9.1 | 35

Hi,

the reason for the build failures is the cmake bump to 3.5.0, reverting 
it solves the problem. A quick analysis showed that for boost being 
detected as a valid installation BR2_PACKAGE_BOOST_ATOMIC is needed. This 
fix alone does not fix the compile problem however, it seems 
BR2_PACKAGE_PYTHON is needed as well and maybe more.
I was unable to perform an error-free configure stage with cmake 3.5.0 so 
my conclusions about the cause are incomplete. What is sure however is 
that with cmake 3.4.3 gnuradio compiles without problems.

Regards, Bernd

  parent reply	other threads:[~2016-03-22  6:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-03-20 Thomas Petazzoni
2016-03-21 19:17 ` Jörg Krause
2016-03-22  6:50 ` Bernd Kuhls [this message]
2016-03-22  7:26   ` gwenhael.goavec

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=4i67scxc49.ln2@ID-313208.user.individual.net \
    --to=bernd.kuhls@t-online.de \
    --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