From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8341] New: Getting EGL Error: Could not create the egl surface: error = 0x300b on RPI-2b board.
Date: Sun, 13 Sep 2015 02:59:14 +0000 (UTC) [thread overview]
Message-ID: <bug-8341-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8341
Summary: Getting EGL Error: Could not create the egl surface:
error = 0x300b on RPI-2b board.
Product: buildroot
Version: 2015.05
Platform: Other
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: davy2002a at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
I am consistently getting a 0x300b error whenever attempting to execute a
custom Qt 5.5.0 application on my Raspberry PI 2 Model B unit, no matter what I
do, I have rebuilt this more then 5x and even did a full rebuild of the code of
both my application and buildroot using "make clean all".
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2015-09-13 2:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 2:59 bugzilla at busybox.net [this message]
2015-09-13 8:28 ` [Buildroot] [Bug 8341] Getting EGL Error: Could not create the egl surface: error = 0x300b on RPI-2b board bugzilla at busybox.net
2015-09-13 12:02 ` bugzilla at busybox.net
2015-09-16 14:28 ` bugzilla at busybox.net
2015-09-16 14:31 ` bugzilla at busybox.net
2015-09-16 17:36 ` bugzilla at busybox.net
2015-10-15 13:35 ` bugzilla at busybox.net
2016-08-31 20:45 ` bugzilla at busybox.net
2016-08-31 22:15 ` 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-8341-163@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.