All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [arc-buildroot] [autobuild.buildroot.net] arc build results for 2015-07-14
Date: Fri, 17 Jul 2015 16:13:21 +0200	[thread overview]
Message-ID: <1437142401.1824.6.camel@embedded.rocks> (raw)
In-Reply-To: <1436982736.3682.16.camel@synopsys.com>

Dear Alexey, Thomas,

On Mi, 2015-07-15 at 17:52 +0000, Alexey Brodkin wrote:
> Hi Thomas,
> 
> On Wed, 2015-07-15 at 08:30 +0200, Thomas Petazzoni wrote:
> > Those results are limited to the arc architecture.
> > 
> > Build statistics for 2015-07-14
> > ===============================
> > 
> >         success : 6  
> >        failures : 23 
> >        timeouts : 0  
> >           TOTAL : 29 
> > 
> > Classification of failures by reason
> > ====================================
> > 
> >                   zeromq-4.0.5 | 9 
> >              util-linux-2.26.2 | 5 
> >                   boost-1.58.0 | 3 
> >                alsa-lib-1.0.29 | 3 
> >              btrfs-progs-4.1.1 | 1 
> >              libselinux-2.1.13 | 1 
> >                    tinc-1.0.24 | 1 
> > 
> > Detail of failures
> > ===================
> > 
> >          arc |                   boost-1.58.0 | NOK | 
> > http://autobuild.buildroot.net/results/596c2eb1378946b8c0fea6b3ebcf
> > 80ee7e14995a/
> >          arc |                   boost-1.58.0 | NOK | 
> > http://autobuild.buildroot.net/results/0585f6c926042d7c859150dbf7b3
> > 3928c4687273/
> >          arc |                   boost-1.58.0 | NOK | 
> > http://autobuild.buildroot.net/results/16fd658176b4e4927f7c7dbe5598
> > b7a38b819af9/
> 
> Looks like an issue with boost that for some reason
> uses syscall (non-existent on some arches including ARC)
> directly instead of libc's eventfd().
> ----------------->8-------------------
> "syscall(__NR_eventfd, 0);"
> ----------------->8-------------------

__NR_eventfd needs __ARCH_WANT_SYSCALL_NO_FLAGS to be defined in
asm/unistd.h. I am not a toolchain expert so I do not know how to
handle this.

Best regards
J?rg Krause

  reply	other threads:[~2015-07-17 14:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150715063016.118A21016B5@stock.ovh.net>
2015-07-15 17:52 ` [Buildroot] [arc-buildroot] [autobuild.buildroot.net] arc build results for 2015-07-14 Alexey Brodkin
2015-07-17 14:13   ` Jörg Krause [this message]
2015-07-17 15:31     ` Alexey Brodkin

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=1437142401.1824.6.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.