From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2018-12-02
Date: Mon, 3 Dec 2018 14:56:12 +0100 [thread overview]
Message-ID: <20181203145612.150037bc@windsurf.home> (raw)
In-Reply-To: <CAMRc=MdwOpMmwhjvHMOfb_wBgwQAq4_TAdUUDRSi4eYReYTcZg@mail.gmail.com>
Hello,
On Mon, 3 Dec 2018 14:51:05 +0100, Bartosz Golaszewski wrote:
> > > this failure (and others in pulseview) are due to libsigrokdecode.h
> > > being included when libsigrokdecode is not built. It's a bug in
> > > pulseview. I already have a patch and will submit it later today both
> > > for buildroot as well as upstream.
> >
> > Well, the error that Philipp points to is in libtorrent-rasterbar,
> > which has nothing to do with libsigrokdecode, and quite probably
> > doesn't use it. Are you sure the issue is related ?
>
> What I meant was that I found the issue and it has nothing to do with
> libtorrent. I should have expressed myself clearer.
How can a bug in pulseview/libsigrokdecode after libttorrent-rasterbar ?
See the build failures we are talking about, they affect the
libtorrent-rasterbar package:
http://autobuild.buildroot.net/?reason=libtorrent-rasterbar%
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-03 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181203070035.5D6B220D2E@mail.bootlin.com>
[not found] ` <CA+Vb7ho5wgKxatazqbL4sdmtiEXiwSH8zw+LdYGr5vySBa0QBw@mail.gmail.com>
2018-12-03 12:45 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2018-12-02 Thomas Petazzoni
2018-12-03 13:37 ` Bartosz Golaszewski
2018-12-03 13:44 ` Thomas Petazzoni
2018-12-03 13:51 ` Bartosz Golaszewski
2018-12-03 13:56 ` Thomas Petazzoni [this message]
2018-12-03 14:25 ` Bartosz Golaszewski
2018-12-03 14:34 ` Thomas Petazzoni
2018-12-03 14:36 ` Bartosz Golaszewski
2018-12-03 18:59 ` Philipp Richter
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=20181203145612.150037bc@windsurf.home \
--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