From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-02-21
Date: Fri, 23 Feb 2018 09:28:46 +0100 [thread overview]
Message-ID: <CAPi7W80GcVM8JeM0Svzxb=AG=b2tJ59=QYArRWY6HkR9OjArGQ@mail.gmail.com> (raw)
In-Reply-To: <CANQCQpZ4LfgTJakUKquxknPxepYKmoXoGGAztFwMEuBiw1nY7Q@mail.gmail.com>
Dear Matthew,
2018-02-22 23:41 GMT+01:00 Matthew Weber <matthew.weber@rockwellcollins.com>
:
> Thomas/Fabrice,
>
> On Thu, Feb 22, 2018 at 1:00 AM, Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
> > Hello,
> >
> > Build statistics for 2018-02-21
> > ===============================
> >
> > branch | OK | NOK | TIM | TOT |
> > master | 172 | 28 | 0 | 200 |
> > 2017.11.x | 23 | 0 | 0 | 23 |
> > next | 32 | 28 | 0 | 60 |
> >
> > Results for branch 'master'
> > ===========================
> >
> > Classification of failures by reason
> > ------------------------------------
> >
> > boost-1.66.0 | 6
>
> > bfin | boost-1.66.0 | NOK |
> http://autobuild.buildroot.net/results/ffa5f21d7e7c38ea7adebc84f1cc8e
> e4cff74f1b |
> > microblazeel | boost-1.66.0 | NOK |
> http://autobuild.buildroot.net/results/2879576eaa870eecd31af1ff9261df
> 1b86966542 |
> > arm | boost-1.66.0 | NOK |
> http://autobuild.buildroot.net/results/a89df3195b44f125ba1797cf866f4a
> 266909ec05 |
> > powerpc | boost-1.66.0 | NOK |
> http://autobuild.buildroot.net/results/c947986e4f460c1733c81585302f58
> baca84f01a |
> > arm | boost-1.66.0 | NOK |
> http://autobuild.buildroot.net/results/679a12c04e9954947dd51df2017af5
> 61c362f8ec |
> > or1k | boost-1.66.0 | NOK |
> http://autobuild.buildroot.net/results/4e901a97ad1c21f21e508eab826837
> 4220f2eba3 |
>
> Similar to (https://patchwork.ozlabs.org/patch/871696/). Feels like a
> similar patch is needed for Boost? I don't have the history on the
> discussion for the domoticz pkg.
>
You're right, this is the same issue. we should add a
BR2_TOOLCHAIN_HAS_THREADS_NPTL
dependency to BR2_PACKAGE_BOOST_THREAD.
This dependency should be added to all packages using boost_thread
including domoticz. I can make this patch or let you do it if you want.
>
> Matt
>
Best Regards,
Fabrice
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180223/a45dee63/attachment.html>
next prev parent reply other threads:[~2018-02-23 8:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-02-21 Thomas Petazzoni
2018-02-22 22:41 ` Matthew Weber
2018-02-23 8:28 ` Fabrice Fontaine [this message]
2018-02-23 12:02 ` Fabrice Fontaine
2018-02-23 14:05 ` Matthew Weber
2018-02-23 17:39 ` Fabrice Fontaine
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='CAPi7W80GcVM8JeM0Svzxb=AG=b2tJ59=QYArRWY6HkR9OjArGQ@mail.gmail.com' \
--to=fontaine.fabrice@gmail.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 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.