Yes don't mix swfp and hwfp builds. That was my comment on freescale community.
Lauren Post i.MX Yocto Team Lead From: [email protected] [mailto:[email protected]] On Behalf Of Alex J Lennon Sent: Tuesday, November 05, 2013 6:25 AM To: [email protected] Subject: Re: [meta-freescale] Problems building fsl-image-gui for TARGET_FPU=vfp-neon [SOLVED] On 04/11/2013 09:42, Alex J Lennon wrote: Hi, I'm trying to build fsl-image-gui for soft float as I am using Mono in a project and Mono currently doesn't appear to support hard float. Git checkouts I'm using are all recent (i.e. within days), meta-yocto = "ajlennon/sqlite:3ab777991480aa4bff79130bd889ed25eba72fdc" meta-fsl-arm = "master:88117e976c16f22b9bbfeb26a52088e31f1d0c4d" meta-fsl-arm-extra = "master:5b753d3d130ed6932715329d0e887a015e628766" meta-fsl-demos = "master:87233da97fe0ead245773e092acb56faa24f3835" meta-mono = "master:ceae2e324a03bf2c616c98a69b4e16f7b7a6af03" I wasn't entirely clear on how to change the tuning to use the neon registers instead of hard float, and in the end I added the following line to local.conf DEFAULTTUNE_mx6 ?= "cortexa9-neon" This gets me building with bitbake reporting, TUNE_FEATURES = "armv7a vfp neon cortexa9" TARGET_FPU = "vfp-neon" I had some trouble rebuilding and in the end I removed the tmp/ directory and restarted the build. This gets me further but I'm now erroring on gpu-viv-bin-mx6q do_package() --- NOTE: Creating RPM package for gpu-viv-bin-mx6q NOTE: Creating RPM package for gpu-viv-bin-mx6q DEBUG: Python function write_specfile finished DEBUG: Executing shell function BUILDSPEC error: line 22: Illegal char '-' in EVR: Requires: libvdk-mx6 >= 3.10.9-1.0.0-hfp error: Package has no %description: gpu-viv-bin-mx6q-3.10.9+1.0.0+sfp-r0.cortexa9_vfp_neon_mx6 Building target platforms: cortexa9_vfp_neon_mx6-poky-linux-gnueabi WARNING: exit code 1 from a shell command. DEBUG: Python function do_package_rpm finished DEBUG: Python function do_package_write_rpm finished ERROR: Function failed: BUILDSPEC (log file is located at /data_drive/imx6/rootfs_builder/build/tmp/work/cortexa9-vfp-neon-mx6-poky-linux-gnueabi/gpu-viv-bin-mx6q/1_3.10.9-1.0.0-sfp-r0/temp/log$ --- Can anybody advise whether I'm overriding the default hfp tuning correctly, and what might be going wrong here? It looks to me as though there was some kind of issue with the dependencies as the .spec file being built still had references to hardfp packages I found this comment at the FSL community forum: "I tried this on imx6qsabresd and have no issues. Right before release we did have problems with disabling hwfp correctly but it was enabled in the final update. Also I've seen multiple times that switching between hwfp and swfp can corrupt build states. I always keep these completely separate builds both with cache and tmp directories." ref: https://community.freescale.com/thread/310233 When I created a new build tree and built for softfp within that tree it all seems to work. Many thanks, Alex Lennon On 01/11/2013 15:04, Doug Schwanke wrote: Thank you for the pointer. That is exactly what I needed. -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Otavio Salvador Sent: Thursday, October 31, 2013 10:25 AM To: Doug Schwanke Cc: [email protected]<mailto:[email protected]> Subject: Re: [meta-freescale] Unable to add "jack" into my image On Thu, Oct 31, 2013 at 1:15 PM, Doug Schwanke <[email protected]><mailto:[email protected]> wrote: I can "bitbake jack" without any errors, but when I add "jack" to my recipe, I get an error that jack not found in the base feeds. Is "jack" missing from the imx6qsabresd feed or do I need to add some kind of depends? Neither; this is common for people starting to Yocto to make this mistake. Basically you need to check the binary packages it builds. When you do: $: bitbake jack You are saying ... hey bitbake, please process jack recipe. This has no direct relation to the binaries you get as result. When you add something in IMAGE_INSTALL or similar, you are asking for the image to install the /binary/. For jack case, the binaries are: http://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-multimedi a/jack/jack_0.121.0.bb?h=dora#n38 Most probably, you're looking for jack-server binary. Regards, -- [Dynamic Devices Ltd]<http://www.dynamicdevices.co.uk/> Alex J Lennon / Director 1 Queensway, Liverpool L22 4RA mobile: +44 (0)7956 668178 [Linkedin]<http://www.linkedin.com/in/alexjlennon>[Skype]<skype:alexjlennon?add> This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. Company Name is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company. _______________________________________________ meta-freescale mailing list [email protected]<mailto:[email protected]> https://lists.yoctoproject.org/listinfo/meta-freescale -- [Dynamic Devices Ltd]<http://www.dynamicdevices.co.uk/> Alex J Lennon / Director 1 Queensway, Liverpool L22 4RA mobile: +44 (0)7956 668178 [Linkedin]<http://www.linkedin.com/in/alexjlennon>[Skype]<skype:alexjlennon?add> This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. Company Name is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.
<<inline: image001.png>>
<<inline: image002.png>>
<<inline: image003.png>>
_______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
