From: Stefan Christ <s.christ@phytec.de>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-qt5] Backport fix for qt5-opengles2-test to fido?
Date: Tue, 8 Sep 2015 08:49:01 +0200 [thread overview]
Message-ID: <20150908064901.GA2368@lws-christ> (raw)
Hi,
I'm currently using the fido branch of meta-qt5 and having troubles with the
qt5-opengles2-test program. It segfaults on start.
The problem is fixed by the following commit in the master branch.
commit 6d9e2a6dfc21f7d9a3a11b4bcb426b5dfe6feaeb
Author: Andreas Müller <schnitzeltony@googlemail.com>
Date: Sat Jun 13 09:02:55 2015 +0200
qt5-opengles2-test: update to last commit
* don't segfault in case qtsensors does not find accelerometer values
Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Is it possible to backport this patch to fido?
Mit freundlichen Grüßen / Kind regards,
Stefan Christ
next reply other threads:[~2015-09-08 6:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 6:49 Stefan Christ [this message]
2015-09-08 7:29 ` [meta-qt5] Backport fix for qt5-opengles2-test to fido? Martin Jansa
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=20150908064901.GA2368@lws-christ \
--to=s.christ@phytec.de \
--cc=openembedded-devel@lists.openembedded.org \
/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