Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 15:34:31 +0100	[thread overview]
Message-ID: <20181203153431.0c2a82f1@windsurf.home> (raw)
In-Reply-To: <CAMRc=Mc1SqoZKZ45xT7LS9g=0mpA7Av1AJF6qEZmeFeBgL+qrw@mail.gmail.com>

Hello,

On Mon, 3 Dec 2018 15:25:25 +0100, Bartosz Golaszewski wrote:

> > How can a bug in pulseview/libsigrokdecode after libttorrent-rasterbar ?
> >
> > See the build failures we are talking about, they affect the
> > libtorrent-rasterbar package:
> >  
> 
> I'm not following you here I'm afraid. This has nothing to do with any
> other package - this is purely a pulseview bug. It appears after my
> previous version bump and is confined to pulseview.

Are you looking at:

  http://autobuild.buildroot.net/results/753/753059dd52da9ec2aa1b06f3b64b0ab5ee3e059a/build-end.log

Let me paste the relevant part:

In file included from peer_connection.cpp:56:0:
../include/libtorrent/peer_connection.hpp:550:8: error: generic thunk code fails for method 'virtual void libtorrent::peer_connection::_ZThn96_NK10libtorrent15peer_connection8peer_logENS_14peer_log_alert11direction_tEPKcS4_z(libtorrent::peer_log_alert::direction_t, const char*, const char*, ...) const' which uses '...'
   void peer_log(peer_log_alert::direction_t direction
        ^~~~~~~~
make[2]: *** [peer_connection.lo] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/home/dawncrow/buildroot-test/scripts/instance-0/output/build/libtorrent-rasterbar-1.1.11/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/dawncrow/buildroot-test/scripts/instance-0/output/build/libtorrent-rasterbar-1.1.11'
make: *** [/home/dawncrow/buildroot-test/scripts/instance-0/output/build/libtorrent-rasterbar-1.1.11/.stamp_built] Error 2
make: Leaving directory `/home/dawncrow/buildroot-test/scripts/instance-0/buildroot'

Where do you see a pulseview issue ?

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-12-03 14:34 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
2018-12-03 14:25             ` Bartosz Golaszewski
2018-12-03 14:34               ` Thomas Petazzoni [this message]
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=20181203153431.0c2a82f1@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