If we do not provide that option (arm-XXX-gcc hello.c ) then it gives below error. fatal error: gnu/stubs-soft.h: No such file or directory
=> your toolchain support only hard fpu if you want to use softfp , you must change your toolchain do you use linaro-toolchain gcc-4.9??? linaro-toolchain gcc-4.9 only hard fpu -----Original Message----- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of yocto-requ...@yoctoproject.org Sent: Monday, June 01, 2015 11:48 PM To: yocto@yoctoproject.org Subject: yocto Digest, Vol 57, Issue 1 Send yocto mailing list submissions to yocto@yoctoproject.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.yoctoproject.org/listinfo/yocto or, via email, send a message with subject or body 'help' to yocto-requ...@yoctoproject.org You can reach the person managing the list at yocto-ow...@yoctoproject.org When replying, please edit your Subject line so it is more specific than "Re: Contents of yocto digest..." Today's Topics: 1. Re: cortexa15 toolchain compilation option (Neelkumar Patel) 2. Strange configure error (???) (Neuer User) 3. Re: build hello_world.c in yocto (Victor Rodriguez) 4. Re: build hello_world.c in yocto (Burton, Ross) 5. Multi recipes for different defconfig on the same kernel source (Joel (Xi Zhou) Zhou) ---------------------------------------------------------------------- Message: 1 Date: Mon, 1 Jun 2015 07:02:33 +0000 From: Neelkumar Patel <neel.pa...@einfochips.com> To: "yocto@yoctoproject.org" <yocto@yoctoproject.org> Subject: Re: [yocto] cortexa15 toolchain compilation option Message-ID: <hk2pr0201mb0931b1e128c7f804cb9deed6ff...@hk2pr0201mb0931.apcprd02.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" Hi, Sorry option is -mfloat-abi=hard. We have to provide below option during compilation. arm-XXX-gcc -mfloat-abi=hard hello.c We do not want to give -mfloat-abi=hard option during compilation. If we do not provide that option (arm-XXX-gcc hello.c ) then it gives below error. fatal error: gnu/stubs-soft.h: No such file or directory Thanks From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Neelkumar Patel Sent: 01 June 2015 12:04 To: yocto@yoctoproject.org Subject: [yocto] cortexa15 toolchain compilation option Hi, We are building the toolchain for cortexa15 CPU in oe-core and we are able to build the toolchain but during the compilation of the application we have to provide manually option "--with-float=hard". e.g. We have one application called "hello.c". We have to provide below option for compilation. If we do not provide --with-float option then we are getting compilation error. arm-XXX-gcc --with-float=hard hello.c Is there any option to remove "-with-float" option during the application compilation. Is there any change we have to do in oe-core ?? Thanks in Advance. ************************************************************************************************************************************************************* eInfochips Business Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated. Company has taken enough precautions to prevent the spread of viruses. However the co mpany accepts no liability for any damage caused by any virus transmitted by this email. ************************************************************************************************************************************************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20150601/f845016f/attachment-0001.html> ------------------------------ Message: 2 Date: Mon, 01 Jun 2015 11:23:19 +0200 From: Neuer User <auslands...@gmx.de> To: yocto@yoctoproject.org Subject: [yocto] Strange configure error (???) Message-ID: <mkh8a7$kt6$1...@ger.gmane.org> Content-Type: text/plain; charset=utf-8 Hi I'm currently moving from Dora to Fido. I moved all my recipes to a new yocto installation and are modifying the recipes where necessary. I have a very strange error when configuring a kernel recipe (linux-cubox-i). Actually, there is no error when using the defaut recipe included in fido. Only if I add the following bbappend file in order to change the kernel configuration, I get the error: FILESEXTRAPATHS_prepend := "${THISDIR}/linux-cubox-i:" SRC_URI = "file://defconfig \ file://videoin.cfg \ file://networking.cfg \ file://wlan.cfg \ file://dm-crypt.cfg \ file://no-caam.cfg \ file://leds.cfg \ file://mod-to-builtin.cfg \ file://watchdog-nowayout.cfg \ " KERNEL_IMAGETYPE_cubox-i = "zImage" Error: | DEBUG: Executing python function sysroot_cleansstate | DEBUG: Python function sysroot_cleansstate finished | DEBUG: Executing shell function do_configure | WARNING: exit code 128 from a shell command. | ERROR: Function failed: do_configure (log file is located at /home/ubuntu/yocto1.8/build/tmp/work/cubox_i-poky-linux-gnueabi/linux-cubox-i/3.14.14-r0/temp/log.do_configure.29043) Nothing more in the configure log. :( Any idea, what is wrong? In general I just want to use a diffent kernel config. Actually a kernel config that worked before without problems on dora. I really have no idea, why this isn't working or even what the error means. Thanks for any help Michael ------------------------------ Message: 3 Date: Mon, 1 Jun 2015 07:08:19 -0500 From: Victor Rodriguez <vm.ro...@gmail.com> To: "Burton, Ross" <ross.bur...@intel.com> Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org> Subject: Re: [yocto] build hello_world.c in yocto Message-ID: <CAK5mtexC81Yi9C2YA6O4SuKZ=vQ6wk8=cuynz8myoq4uaoz...@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 On Sun, May 31, 2015 at 5:48 PM, Burton, Ross <ross.bur...@intel.com> wrote: > > On 29 May 2015 at 21:59, Victor Rodriguez <vm.ro...@gmail.com> wrote: >> >> Question what are the necessary IMAGE_INSTALL_append to build a c >> hello world in an core-image-minimal ? > > > The easy way is to add tools-sdk to IMAGE_FEATURES. That gives you a > complete toolchain (not just gcc) and more pieces. > > Ross Thanks a lot Ross I will try this on e, I had the idea that just with EXTRA_IMAGE_FEATURES = "debug-tweaks dev-pkgs" Thanks Victor Rodriguez ------------------------------ Message: 4 Date: Mon, 1 Jun 2015 13:22:03 +0100 From: "Burton, Ross" <ross.bur...@intel.com> To: Victor Rodriguez <vm.ro...@gmail.com> Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org> Subject: Re: [yocto] build hello_world.c in yocto Message-ID: <cajto0lzqh+u5fnkf_vvvuyw7kaxrmdltenai1ucpz2-uepb...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" On 1 June 2015 at 13:08, Victor Rodriguez <vm.ro...@gmail.com> wrote: > EXTRA_IMAGE_FEATURES = "debug-tweaks dev-pkgs" > As the documentation says ( http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#ref-features-image), dev-pkgs is just the headers and library links for the packages you've installed. No tools come with that. Ross -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20150601/d1930302/attachment-0001.html> ------------------------------ Message: 5 Date: Mon, 1 Jun 2015 14:48:14 +0000 From: "Joel (Xi Zhou) Zhou" <joel.z...@broadcom.com> To: "yocto@yoctoproject.org" <yocto@yoctoproject.org> Subject: [yocto] Multi recipes for different defconfig on the same kernel source Message-ID: <9f136ee5fb53d64397ed1089a0e760e0162d2...@sjexchmb12.corp.ad.broadcom.com> Content-Type: text/plain; charset="us-ascii" Hi all, I need to create multiple recipes for different kernel config based on the same kernel source. In my experiment, I create a new recipe linux-brcm-nand based on linux-brcm, the only different is the kernel defconfig file. >From the following error message, it looks like the idea of multi-kernel >providers. What is the correct way to different kernel config on the same kernel source? Thanks, Joel ---------------------------------- ERROR: The recipe linux-brcm-nand is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /projects/poky/build64/tmp/sysroots/brcm/pkgdata/runtime/kernel Matched in manifest-brcm-linux-brcm.packagedata /projects/poky/build64/tmp/sysroots/brcm/pkgdata/runtime/kernel.packaged Matched in manifest-brcm-linux-brcm.packagedata ... /projects/poky/build64/tmp/sysroots/brcm/pkgdata/kernel-depmod/System.map-3.14.29 Matched in manifest-brcm-linux-brcm.packagedata Please verify which recipe should provide the above files. The build has stopped as continuing in this scenario WILL break things, if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error however switching DISTRO_FEATURES on an existing build directory is not supported, you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_DUPWHITELIST may be the correct solution. It could also be your buil d is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above. ERROR: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases. ERROR: Function failed: sstate_task_postfunc ERROR: Logfile of failure stored in: /projects/poky/build64/tmp/work/brcm -poky-linux/linux-brcm-nand/3.14.29-r6/temp/log.do_packagedata.40045 NOTE: recipe linux-brcm-nand-3.14.29-r6: task do_packagedata: Failed ERROR: Task 11 (/projects/poky/build64../meta-brcm/meta/recipes-kernel/linux/linux-brcm-nand_3.14.29.bb, do_packagedata) failed with exit code '1' NOTE: Tasks Summary: Attempted 447 tasks of which 445 didn't need to be rerun and 2 failed. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20150601/6ccd580f/attachment.html> ------------------------------ -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto End of yocto Digest, Vol 57, Issue 1 ************************************ -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
