From: Marc Reilly <marc@cpdesign.com.au>
To: "Patches and discussions about the oe-core layer"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] qt4(embedded and x11): disable neon for armv6-vfp
Date: Fri, 16 Sep 2011 11:31:37 +1000 [thread overview]
Message-ID: <201109161131.37982.marc@cpdesign.com.au> (raw)
In-Reply-To: <1316078776-19890-3-git-send-email-denis@eukrea.com>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
On Thursday, September 15, 2011 07:26:16 PM Denis Carikli wrote:
> without the -no-neon flag, neon is "autodetected"
> by looking if the compiler is capable of compiling
> a neon test, and succeed, and neon is then enabled
> during the compilation.
>
> Signed-off-by: Denis Carikli <denis@eukrea.com>
> QT_CONFIG_FLAGS_append_armv6 = " -no-neon "
> +QT_CONFIG_FLAGS_append_armv6-vfp = " -no-neon "
I also ran into this problem, with the same fix.
There are a couple of other places with armv6 overrides that could misbehave,
notably:
TARGET_CC_ARCH_append_armv6 = " -D__SOFTFP__"
(python_2.6.6.bb)
QEMU_OPTIONS_armv6 = "-cpu arm1136"
(bitbake.conf)
Is there a way to do this more generically?, something like:
QT_CONFIG_FLAGS_append_armv6* = " ... "
Cheers
Marc
[-- Attachment #2: Type: text/html, Size: 5452 bytes --]
prev parent reply other threads:[~2011-09-16 1:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 9:26 Some QT patches Denis Carikli
2011-09-15 9:26 ` [PATCH 1/2] qt4.inc: package qtdemo's docs in a separate package Denis Carikli
2011-09-15 16:08 ` Eric Bénard
2011-09-15 16:19 ` [PATCH v2] " Denis Carikli
2011-09-15 9:26 ` [PATCH 2/2] qt4(embedded and x11): disable neon for armv6-vfp Denis Carikli
2011-09-16 1:31 ` Marc Reilly [this message]
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=201109161131.37982.marc@cpdesign.com.au \
--to=marc@cpdesign.com.au \
--cc=openembedded-core@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