From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-03-07
Date: Thu, 8 Mar 2018 09:20:35 +0100 [thread overview]
Message-ID: <20180308092035.5f07ea4b@windsurf> (raw)
In-Reply-To: <87lgf3knkk.fsf@dell.be.48ers.dk>
Hello,
On Thu, 08 Mar 2018 08:56:27 +0100, Peter Korsgaard wrote:
> > Classification of failures by reason
> > ------------------------------------
>
> > zyre-1d949e4bf79b694ea883c3... | 14
>
> Started happening when czmq got bumped, so probably an incompatibility
> with the new version.
>
> I see upstream released a v2.0.0 back in January 2017, so bumping the
> version might fix it. Any takers?
I'll take a look.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2018-03-08 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-03-07 Thomas Petazzoni
2018-03-08 7:56 ` Peter Korsgaard
2018-03-08 7:57 ` Olivier Schonken
2018-03-08 8:20 ` 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=20180308092035.5f07ea4b@windsurf \
--to=thomas.petazzoni@bootlin.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