[meta-freescale] [meta-fsl-arm] Can't build QT5 for i.MX6
John Weber
rjohnweber at gmail.com
Tue Jan 21 14:00:46 PST 2014
Hi Gary,
On 1/21/14 3:52 PM, Gary Thomas wrote:
> 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.
That's strange, because I just built it with Dora like 12 times in a row suing
the instructions from the above link while trying to see what was causing a boot
problem and never saw this failure.
>
> 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
>
More information about the meta-freescale
mailing list