From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2017-08-14
Date: Thu, 17 Aug 2017 09:47:51 +0200 [thread overview]
Message-ID: <20170817094751.5df88b1f@windsurf> (raw)
In-Reply-To: <9a1b8d71-d39b-dc8b-fa95-dbeb6f1213b4@mind.be>
Hello,
On Thu, 17 Aug 2017 00:48:10 +0200, Arnout Vandecappelle wrote:
> > So if it was just the Sourcery toolchain being unable to build
> > ruby-2.4.1, I think we would have a lot more failures than that. So it
> > might be a toolchain issue, but that occurs under very specific
> > conditions.
>
> ruby has a bunch of optional dependencies, so yes indeed it only occurs for
> some exotic combination of these dependencies.
>
> So I checked the source of the Sourcery toolchain and it does NOT have the
> patch of bug 20006 applied, even though it was released in binutils 2.26.1, 4
> months before the Sourcery release...
>
> So, we could try to find out which exact combination of packages triggers this
> issue, but is that worth it for something that happens twice in five months...
True, but it's annoying to have those sporadic failures once in a
while :-/
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-08-17 7:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 6:31 [Buildroot] [autobuild.buildroot.net] Build results for 2017-08-14 Thomas Petazzoni
2017-08-15 12:20 ` [Buildroot] Analysis of build " Thomas Petazzoni
2017-08-15 12:58 ` Matthew Weber
2017-08-15 13:59 ` Thomas Petazzoni
2017-08-15 14:15 ` Matthew Weber
2017-08-16 20:22 ` Arnout Vandecappelle
2017-08-16 23:58 ` Matthew Weber
2017-08-17 2:00 ` Matthew Weber
2017-08-17 7:09 ` Thomas Petazzoni
2017-08-17 7:36 ` Arnout Vandecappelle
2017-08-17 12:01 ` Matthew Weber
2017-08-17 12:15 ` Arnout Vandecappelle
2017-08-16 20:35 ` Arnout Vandecappelle
2017-08-16 20:53 ` Thomas Petazzoni
2017-08-16 22:48 ` Arnout Vandecappelle
2017-08-17 7:47 ` Thomas Petazzoni [this message]
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=20170817094751.5df88b1f@windsurf \
--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