From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Xtensa toolchain issue ?
Date: Wed, 2 Jan 2019 11:21:30 +0100 [thread overview]
Message-ID: <20190102112130.0b8d32f8@windsurf> (raw)
Hello Max,
We have a build failure of the libtorrent-rasterbar package that seems
to be toolchain related, and happens on Xtensa:
http://autobuild.buildroot.net/?reason=libtorrent-rasterbar-1.1.11
The failure looks like this:
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
^~~~~~~~
CXX packet_buffer.lo
It is worth mentioning though that the exact same issue happens on the
OpenRISC architecture, and that Xtensa and OpenRISC seem to be the two
only affected architectures.
It is apparently a bug in gcc 7.x, that has been fixed in gcc 8.x,
according to https://bugzilla.redhat.com/show_bug.cgi?id=1511021, but
this bug report doesn't give any detail on which commit could have
fixed that.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next reply other threads:[~2019-01-02 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 10:21 Thomas Petazzoni [this message]
2019-01-03 22:17 ` [Buildroot] Xtensa toolchain issue ? Max Filippov
2019-01-04 9:27 ` Thomas Petazzoni
2019-01-04 23:44 ` Max Filippov
2019-01-10 14:56 ` Thomas Petazzoni
2019-01-14 20:09 ` Max Filippov
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=20190102112130.0b8d32f8@windsurf \
--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 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.