From: Gary Thomas <gary@mlbassoc.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: [meta-fsl-arm] Can't build QT5 for i.MX6
Date: Tue, 21 Jan 2014 14:52:23 -0700 [thread overview]
Message-ID: <52DEEC17.60406@mlbassoc.com> (raw)
I've been trying to build QT5 from meta-qt5 layer without success.
All attempts result in compile errors, as seen in http://ix.io/a2F
I'm using Poky/Yocto + meta-fsl-arm* latest master:
Build Configuration:
BB_VERSION = "1.21.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-12.04"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "wandboard-quad"
DISTRO = "poky"
DISTRO_VERSION = "1.5+snapshot-20140121"
TUNE_FEATURES = "armv7a vfp neon callconvention-hard cortexa9"
TARGET_FPU = "vfp-neon"
meta = "master:97d7e8689ca83a13ea511c0b91bf80974b8750b0"
meta-fsl-arm = "master:a899296ac603f549b28200a7c38d4ec4ca5c1ad5"
meta-fsl-arm-extra = "master:6a8759c593e8cd85f0dccb9e3b6de25adf2b3bb1"
meta-yocto
meta-yocto-bsp = "master:97d7e8689ca83a13ea511c0b91bf80974b8750b0"
meta-qt5 = "master:775d77e482f1ea203c78003cccd2547075fd720f"
I've tried different built hosts (Fedora/i586 as well) and other i.MX6
targets, all fail the same way.
The key error from the log seems to be:
/local/wandboard_test/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/qtbase/5.1.1-r0/qtbase-opensource-src-5.1.1/include/QtCore/../../src/corelib/io/qurl.h:132:9: error:
expected identifier before numeric constant
None = 0x0,
^
/local/wandboard_test/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/qtbase/5.1.1-r0/qtbase-opensource-src-5.1.1/include/QtCore/../../src/corelib/io/qurl.h:132:9: error:
expected '}' before numeric constant
It looks like somehow 'None' has been defined to be something?
It appears that QT5 has been built, at least at some point, according to
the page http://wiki.wandboard.org/index.php/Building_Qt5_using_yocto_on_Wandboard
I tried to duplicate this using the 'dora' branches with the same
failure as above.
The problem is definitely i.MX related as I can build for other ARM
targets, OMAP3, OMAP4, qemuarm, etc.
Any ideas about this? You can't imagine how many hours I've been chasing this one!
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2014-01-21 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 21:52 Gary Thomas [this message]
2014-01-21 22:00 ` [meta-fsl-arm] Can't build QT5 for i.MX6 John Weber
2014-01-23 12:08 ` Gary Thomas
2014-01-23 13:23 ` Gary Thomas
2014-01-23 15:15 ` John Weber
2014-01-23 15:17 ` Gary Thomas
2014-01-23 16:59 ` Morgan McKenzie
2014-01-23 19:38 ` Gary Thomas
2014-01-23 20:28 ` Eric Bénard
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=52DEEC17.60406@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=meta-freescale@yoctoproject.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 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.