From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11556] Can not build qt5base 5.11.2 with weston 3.0.0 and vivante GPU. error: invalid conversion from ‘void*’ to ‘EGLNativeDisplayType {aka wl_display*}’ [-fpermissive]
Date: Tue, 18 Dec 2018 22:38:44 +0000 [thread overview]
Message-ID: <bug-11556-163-tWfajO9SUT@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11556-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11556
--- Comment #9 from Peter Seiderer <ps.report@gmx.net> ---
(In reply to Patrick Koller from comment #6)
Still the same advice:
> Second test was without qt, only wayland/weston, did not compile out of the
> box, a quick fix was to upgrade to a buildroot toolchain instead of the given
> gcc-linaro-4.9.4 toolchain (did not investigate further).
Did run my successful build with buildroot gcc-7.4.0 toolchain...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-12-18 22:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 16:17 [Buildroot] [Bug 11556] New: Can not build qt5base 5.11.2 with weston 3.0.0 and vivante GPU. error: invalid conversion from ‘void*’ to ‘EGLNativeDisplayType {aka wl_display*}’ [-fpermissive] bugzilla at busybox.net
2018-12-11 21:54 ` [Buildroot] [Bug 11556] " bugzilla at busybox.net
2018-12-12 16:29 ` bugzilla at busybox.net
2018-12-13 10:43 ` bugzilla at busybox.net
2018-12-13 15:51 ` bugzilla at busybox.net
2018-12-13 20:02 ` bugzilla at busybox.net
2018-12-17 14:15 ` bugzilla at busybox.net
2018-12-17 17:38 ` bugzilla at busybox.net
2018-12-18 16:20 ` bugzilla at busybox.net
2018-12-18 22:38 ` bugzilla at busybox.net [this message]
2018-12-19 16:00 ` bugzilla at busybox.net
2018-12-19 17:17 ` bugzilla at busybox.net
2018-12-19 18:01 ` bugzilla at busybox.net
2018-12-20 20:26 ` bugzilla at busybox.net
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=bug-11556-163-tWfajO9SUT@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.