Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2015-11-18
Date: Fri, 20 Nov 2015 21:01:28 +0000	[thread overview]
Message-ID: <1448053288.2964.12.camel@synopsys.com> (raw)
In-Reply-To: <20151120001552.51c1b21b@free-electrons.com>

Hi Thomas,

On Fri, 2015-11-20 at 00:15 +0100, Thomas Petazzoni wrote:
> Hello,
> 
> J?r?me, Johan, Bernd, Yann, Martin, Gustavo, R?mi, Samuel, Alexey,
> Waldemar, Clayton, please read below, there are some interesting issues
> for you :-) Thanks !

[snip]

> > arc |                  mesa3d-11.0.4 | NOK | 
> > http://autobuild.buildroot.net/results/6baca535cf492f23112e39e4ced677a969e15d64/
>
>   CXXLD    gallium_dri.la
> collect2: error: ld terminated with signal 11 [Segmentation fault]
>
> Alexey, this looks like an ARC toolchain bug.

Indeed that we were able to reproduce and reported that issue as
9000976236 "Segmentation fault during mesa3d build" to our toolchain guys.
Hopefully will be fixed soon.

[snip]

> > arc |              util-linux-2.27.1 | NOK | 
> > http://autobuild.buildroot.net/results/75960db671807091fe9155aee9e46a6245e32590/
> 
> checking for prlimit... no
> configure: error: flock selected, but required timer_create function not available
> 
> Not sure. Alexey ?

Well I was trying to reproduce that locally but to no avail.
Indeed I tried to strip everything but "util-linux" from defconfig to save time so
might be that's the reason of my failed attempt.

Still google tells me there's a similar issue with MIPSEL, see
http://autobuild.buildroot.org/results/112/112e8b85783f5aaba42a937a6eb064317615a21b/build-end.log

So I would assume that's not just ARC. Still I'm going to start building full defconfig
from failed build and we'll see if I'll be able to trigger that same issue.

-Alexey

  parent reply	other threads:[~2015-11-20 21:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-11-18 Thomas Petazzoni
2015-11-19 23:15 ` [Buildroot] Analysis of build " Thomas Petazzoni
2015-11-20  0:17   ` Ryan Barnett
2015-11-20 15:29   ` Gustavo Zacarias
2015-11-20 15:45     ` Thomas Petazzoni
2015-11-22  7:53     ` Waldemar Brodkorb
2015-11-20 21:01   ` Alexey Brodkin [this message]
2015-11-24 12:10     ` Alexey Brodkin
2015-11-20 22:26   ` Arnout Vandecappelle
2015-11-21  8:23     ` Thomas Petazzoni
2015-11-21 21:14       ` Arnout Vandecappelle
2015-11-21 14:45   ` Martin Bark
2015-11-21 22:17     ` Arnout Vandecappelle
2015-11-22 18:31       ` Martin Bark
2015-11-23  6:22   ` Rodrigo Rebello

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=1448053288.2964.12.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