From: Trent Piepho <tpiepho@impinj.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] azmq: bump to version 1.0.2
Date: Wed, 28 Feb 2018 18:23:28 +0000 [thread overview]
Message-ID: <1519842208.25567.225.camel@impinj.com> (raw)
In-Reply-To: <87vaehlj1v.fsf@dell.be.48ers.dk>
On Wed, 2018-02-28 at 07:33 +0100, Peter Korsgaard wrote:
> > > > > > "Trent" == Trent Piepho <tpiepho@impinj.com> writes:
>
> >> >>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> >> Does this fix any big / security issues so it needs to go to master or
> >> s this for next?
>
> > The previous version of azmq will not build with the boost version in 2018.02-rc2.
>
> > It does work with buildroot 2017.11.2.
>
> > Not sure exactly where the breakage point was between those releases.
>
> Ahh, so azmq-1.0 doesn't build in 2018.02-rc3? Odd, I don't see it in
> the autobuilder
azmq is a header only library and buildroot disables the library's unit
tests, so there is nothing to fail when buildroot "builds" the library.
But if you use it, it doesn't work with some asio changes that went
into boost.
It would be interesting if buildroot could build and run a package's
unit tests. I wonder if autobuilders would be able to find many bugs
that way?
next prev parent reply other threads:[~2018-02-28 18:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 20:51 [Buildroot] [PATCH 1/1] azmq: bump to version 1.0.2 Fabrice Fontaine
2018-02-27 21:03 ` Peter Korsgaard
2018-02-27 21:15 ` Fabrice Fontaine
2018-02-27 21:28 ` Peter Korsgaard
2018-02-28 6:11 ` Trent Piepho
2018-02-28 6:33 ` Peter Korsgaard
2018-02-28 12:51 ` Fabrice Fontaine
2018-02-28 18:23 ` Trent Piepho [this message]
2018-03-01 20:54 ` Arnout Vandecappelle
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=1519842208.25567.225.camel@impinj.com \
--to=tpiepho@impinj.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