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 13:45:17 +0100	[thread overview]
Message-ID: <20181203134517.40729dd9@windsurf.home> (raw)
In-Reply-To: <CA+Vb7ho5wgKxatazqbL4sdmtiEXiwSH8zw+LdYGr5vySBa0QBw@mail.gmail.com>

Hello Philipp,

Thanks for taking a look at your autobuilder failures! Please try to
Cc: the Buildroot mailing list on such discussions.

On Mon, 3 Dec 2018 12:26:33 +0100, Philipp Richter wrote:
> 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
>         ^
> 
> So there's an issue with the variadic function maybe because it's
> overriding a virtual variadic function ?
> According to this https://bugzilla.redhat.com/show_bug.cgi?id=1511021
> adding "[[gnu::optimize("O0")]]" to the function might be a
> workaround.
> Or maybe a newer gcc though for openrisc it seems to be stuck with gcc 5.
> I'll check it out and report back.

Note that it also happened on Xtensa:
http://autobuild.buildroot.net/results/38a/38a5481dff972954c02a74ab19f37e71d5f6510e/build-end.log,
which uses gcc 7.x.

Best regards,

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

       reply	other threads:[~2018-12-03 12:45 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   ` Thomas Petazzoni [this message]
2018-12-03 13:37     ` [Buildroot] [autobuild.buildroot.net] Your build results for 2018-12-02 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
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=20181203134517.40729dd9@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