Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [arc-buildroot] [autobuild.buildroot.net] arc build results for 2015-07-30
Date: Fri, 31 Jul 2015 15:14:32 +0000	[thread overview]
Message-ID: <1438355672.4848.42.camel@synopsys.com> (raw)
In-Reply-To: <20150731063016.698F510159B@stock.ovh.net>

Hi Thomas,

On Fri, 2015-07-31 at 08:30 +0200, Thomas Petazzoni wrote:
> Those results are limited to the arc architecture.
> 
> Build statistics for 2015-07-30
> ===============================
> 
>         success : 7  
>        failures : 6  
>        timeouts : 0  
>           TOTAL : 13 
> 
> Classification of failures by reason
> ====================================
> 
>              libselinux-2.1.13 | 5 
>                 gnuradio-3.7.5 | 1 
> 
> Detail of failures
> ===================
> 
>          arc |                 gnuradio-3.7.5 | NOK | 
> http://autobuild.buildroot.net/results/4dfb0ddcdfb61908e1601506373e990abf5647b7/

Interesting, gnuradio includes Boost and boom it fails in the same way as Boost:
------------------------->8-----------------------
boost::asio::detail::eventfd_select_interrupter::open_descriptors()':
/home/buildroot/build/instance-1/output/host/usr/arc-buildroot-linux
-uclibc/sysroot/usr/include/boost/asio/detail/impl/eventfd_select_interrupter.ipp:50:50: error: '__NR_eventfd' was not
declared in this scope
------------------------->8-----------------------

So once Boost is fixed gnuradio will be cured as well.

-Alexey

           reply	other threads:[~2015-07-31 15:14 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20150731063016.698F510159B@stock.ovh.net>]

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=1438355672.4848.42.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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