11370 2017-04-16 06:10:04 +0000 core-image-clutter: ERROR: mesa is trying to install files into a shared area 2017-06-16 16:18:51 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake unspecified Other arm RESOLVED NOTABUG Medium major 2.4 1 goel.mohit006 goel.mohit006 jku poky.bs.watcher poky.watcher randy.macleod ross.burton --- --- Don't know oldest_to_newest 72530 0 goel.mohit006 2017-04-16 06:10:04 +0000 this is my details Build Configuration: BB_VERSION = "1.26.0" BUILD_SYS = "i686-linux" NATIVELSBSTRING = "Ubuntu-14.04" TARGET_SYS = "arm-phytec-linux-gnueabi" MACHINE = "phyboard-mira-imx6-3" DISTRO = "yogurt" DISTRO_VERSION = "i.MX6-PD15.3.0" TUNE_FEATURES = "arm armv7a vfp neon callconvention-hard cortexa9" TARGET_FPU = "vfp-neon" meta meta-yocto = "(nobranch):06d9c894636352a6c93711c7284d02b0c794a527" meta-phytec = "(nobranch):e8166e3e8bf2c26b8665fd52f61890cd851927da" meta-yogurt = "(nobranch):8f8487fd45b70e7bb68c3ee84463dfb76c72fc2b" meta-oe meta-networking meta-python meta-multimedia = "(nobranch):a7c1a2b0e6947740758136216e45ca6ca66321fc" meta-qt5 = "(nobranch):90919b9d86988e7da01fa2c0a07246b5b5600a5d" meta-ruby = "(nobranch):a7c1a2b0e6947740758136216e45ca6ca66321fc" when i am making core-image clutter then it is showing this error ERROR: The recipe mesa is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/lib/libGLESv1_CM.so.1 Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/lib/libEGL.so Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/lib/libGLESv1_CM.so Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/lib/libGLESv2.so Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/lib/libGLESv1_CM.so.1.1.0 Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/lib/libEGL.so.1 Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/lib/libGLESv2.so.2 Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/lib/libGLESv2.so.2.0.0 Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/lib/pkgconfig/glesv2.pc Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/lib/pkgconfig/egl.pc Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/lib/pkgconfig/glesv1_cm.pc Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/include/KHR/khrplatform.h Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/include/GLES/egl.h Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/include/GLES/glext.h Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/include/GLES/glplatform.h Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/include/GLES/gl.h Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/include/GLES2/gl2ext.h Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/include/GLES2/gl2platform.h Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/include/GLES2/gl2.h Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/include/EGL/egl.h Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/include/EGL/eglext.h Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot /home/mk/shhiv/build/tmp-glibc/sysroots/phyboard-mira-imx6-3/usr/include/EGL/eglplatform.h Matched in manifest-phyboard-mira-imx6-3-imx-gpu-viv.populate_sysroot 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 build 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: /home/mk/shhiv/build/tmp-glibc/work/cortexa9hf-vfp-neon-phytec-linux-gnueabi/mesa/2_10.4.4-r0/temp/log.do_populate_sysroot.2583 ERROR: Task 3 (/home/mk/shhiv/sources/poky/meta/recipes-graphics/mesa/mesa_10.4.4.bb, do_populate_sysroot) failed with exit code '1' and if i remove the mesa then is is asking that nothing provide liborc-.04 and it is required i googlgled it and found that replace liborc with orc solve the problem but i dnt know where to replace this so please help thanks in advance 72712 1 jku 2017-04-20 11:33:55 +0000 The beef is here: > 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. Can you try that (without "removing mesa" or other changes like that) please? 72723 2 randy.macleod 2017-04-20 14:34:09 +0000 FYI: The original title was: in bitbake when i am making core-image-clutter it is showing ERROR: The recipe mesa is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /home/mk/shhiv/build/tmp-glibc/sysroots/phybo I shortened it to help readers. 73097 3 sjolley.yp.pm 2017-05-07 14:05:40 +0000 He e-mailed me to say: If I am removing mesa then it will show that liborc is missing . I am new to yocto so plz if want anu details plz elaborate I am having some question that is not bug can you suggest me any better community from where I can clear my doubts Thank you for your support 73098 4 goel.mohit006 2017-05-07 15:01:05 +0000 (In reply to comment #1) > The beef is here: > > > 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. > > Can you try that (without "removing mesa" or other changes like that) please ya i have tried so many times but still it is showing same error 73191 5 goel.mohit006 2017-05-11 14:48:17 +0000 I have already provide info if any info ie required please update thanks 73204 6 ross.burton 2017-05-11 15:47:17 +0000 This appears to be a bug in the meta-phytec BSP, if it provides its own GL implementation (which it appears to in imx-gpu-viv) then it should ensure that mesa can't be built. The meta-phytec README says to conect support@phytec.de directly. Note that the release of oe-core/meta-oe that you're using is two years old now, so ideally attempt upgrading to a newer release. There appears to be a release of meta-phytec for 2.2/morty, which is the current stable release. 73447 7 goel.mohit006 2017-05-23 18:00:03 +0000 in this if first i bitbaked mesa is installed without any error after installing the mesa i changed the file name like egl.h changed to eglmesa.h like i have changed all the error files after yhis if i will bitbake it will install without any error image build successfully with out any error i know this is wrong but this could be the solution if my build knows that ehl.h provided by mesa is eglmesa.h now i dont knw how to do that if any one know please help me i have mailed to pytec.de but didnt get any answer plz help in that thanks in advance 73450 8 ross.burton 2017-05-23 19:20:19 +0000 Renaming files is wrong, you need to follow the dependencies ('bitbake core-image-clutter -g -u depexp' can help) to find out why it wants to build both mesa and the BSP GL stack, and stop it building mesa.