From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Do not generate NEON code for qt-4.6.2 embedded
Date: Fri, 12 Mar 2010 17:44:09 +0100 [thread overview]
Message-ID: <hndr0p$old$1@dough.gmane.org> (raw)
In-Reply-To: <1268407797-717-1-git-send-email-valentin.longchamp@epfl.ch>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12-03-10 16:29, Valentin Longchamp wrote:
> http://bugreports.qt.nokia.com/browse/QTBUG-8749
> Neon code is generated for armv6 processor, where it should be armv7 only.
> This results in illegal instructions with some of the qt4 libraries.
>
> The current solution is not optimal, I just needed a quick fix for my arch
> and I don't have the needed knowledge in OE to fix it cleanly, but I wanted
> to point this issue out.
Thanks for looking into this, could you please redo this patch with a PR
increase so distributions get the update automatically?
regards,
Koen
> ---
> recipes/qt4/qt4-embedded_4.6.2.bb | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/recipes/qt4/qt4-embedded_4.6.2.bb b/recipes/qt4/qt4-embedded_4.6.2.bb
> index 94ecd01..2d59609 100644
> --- a/recipes/qt4/qt4-embedded_4.6.2.bb
> +++ b/recipes/qt4/qt4-embedded_4.6.2.bb
> @@ -2,5 +2,7 @@ require qt4-embedded.inc
>
> PR = "${INC_PR}.0"
>
> +QT_CONFIG_FLAGS_append_armv6 = " -no-neon "
> +
> require qt-${PV}.inc
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLmm9ZMkyGM64RGpERAnhkAJ4juTtN1P8CFWLeAjgQ0Mweon/WGQCgrhvN
vxsU6USZPP5CTP6ka7TTXDQ=
=Nf3F
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-03-12 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 15:29 [PATCH] Do not generate NEON code for qt-4.6.2 embedded Valentin Longchamp
2010-03-12 16:44 ` Koen Kooi [this message]
2010-03-15 17:04 ` [PATCH] Do not generate NEON code for qt-4.6.2 embedded on armv6 Valentin Longchamp
2010-03-15 17:15 ` Koen Kooi
2010-03-16 0:36 ` Holger Hans Peter Freyther
2010-03-16 1:50 ` Khem Raj
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='hndr0p$old$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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