Bug 3913

Summary:	WARNING: The recipe mesa-dri is trying to install files into a shared area when those files already exist.
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Stoicescu Cornel <corneliux.stoicescu>
Component:	graphics	Assignee:	Laurentiu Palcu <laurentiu.palcu>
Status:	VERIFIED INVALID	QA Contact:
Severity:	normal
Priority:	Medium	CC:	meta.mr.watcher, meta.watcher, sgw
Version:	1.4
Target Milestone:	1.4
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Stoicescu Cornel 2013-02-19 17:16:52 UTC

branch: master
commit: 3ec4df57540421df2cda6b83c615bfb7cebccefd

Steps to reproduce: 
1) bitbake core-image-sato
2) notice warning: 

WARNING: The recipe mesa-dri is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
   /home/lserban/work/poky/build/tmp/sysroots/qemux86-64/usr/lib/libEGL.so.1
   Matched in manifest-qemux86-64-emgd-driver-bin
   /home/lserban/work/poky/build/tmp/sysroots/qemux86-64/usr/lib/libEGL.so
   Matched in manifest-qemux86-64-emgd-driver-bin
   /home/lserban/work/poky/build/tmp/sysroots/qemux86-64/usr/lib/libGLESv2.so.2
   Matched in manifest-qemux86-64-emgd-driver-bin
   /home/lserban/work/poky/build/tmp/sysroots/qemux86-64/usr/lib/libGLESv2.so
   Matched in manifest-qemux86-64-emgd-driver-bin
   /home/lserban/work/poky/build/tmp/sysroots/qemux86-64/usr/include/EGL/eglplatform.h
   Matched in manifest-qemux86-64-emgd-driver-bin
   /home/lserban/work/poky/build/tmp/sysroots/qemux86-64/usr/include/EGL/egl.h
   Matched in manifest-qemux86-64-emgd-driver-bin
   /home/lserban/work/poky/build/tmp/sysroots/qemux86-64/usr/include/EGL/eglext.h
   Matched in manifest-qemux86-64-emgd-driver-bin
   /home/lserban/work/poky/build/tmp/sysroots/qemux86-64/usr/include/GLES2/gl2.h
   Matched in manifest-qemux86-64-emgd-driver-bin
   /home/lserban/work/poky/build/tmp/sysroots/qemux86-64/usr/include/GLES2/gl2ext.h
   Matched in manifest-qemux86-64-emgd-driver-bin
   /home/lserban/work/poky/build/tmp/sysroots/qemux86-64/usr/include/GLES2/gl2platform.h
   Matched in manifest-qemux86-64-emgd-driver-bin
   /home/lserban/work/poky/build/tmp/sysroots/qemux86-64/usr/include/KHR/khrplatform.h
   Matched in manifest-qemux86-64-emgd-driver-bin
   /home/lserban/work/poky/build/tmp/sysroots/qemux86-64/usr/include/GLES/glext.h
   Matched in manifest-qemux86-64-emgd-driver-bin
   /home/lserban/work/poky/build/tmp/sysroots/qemux86-64/usr/include/GLES/gl.h
   Matched in manifest-qemux86-64-emgd-driver-bin
   /home/lserban/work/poky/build/tmp/sysroots/qemux86-64/usr/include/GLES/glplatform.h
   Matched in manifest-qemux86-64-emgd-driver-bin
Please verify which package should provide the above files.

Comment 1 Laurentiu Palcu 2013-02-21 10:19:29 UTC

I tried to reproduce this bug as described in the steps without luck. I used the commit mentioned in the report, did a bitbake core-image-sato from scratch. Please provide more info on how to reproduce the bug. This is my build configuration:

Build Configuration:
BB_VERSION        = "1.17.1"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-12.04"
TARGET_SYS        = "x86_64-poky-linux"
MACHINE           = "qemux86-64"
DISTRO            = "poky"
DISTRO_VERSION    = "1.3+snapshot-20130221"
TUNE_FEATURES     = "m64"
TARGET_FPU        = ""
meta
meta-yocto
meta-yocto-bsp    = "(nobranch):3ec4df57540421df2cda6b83c615bfb7cebccefd"

Comment 2 Saul Wold 2013-02-22 17:30:25 UTC

Is it possible that the failing build was done in a build area that already contained a build, possibly a a hardware target before doing this failing build?

Comment 3 Stoicescu Cornel 2013-02-25 09:14:14 UTC

I will try and reproduce this. It is possible there was another build before this. 

Thank you for the feedback Saul, that narrows down the possible previous builds list to crownbay and sugarbay.

Comment 4 Stoicescu Cornel 2013-02-28 14:00:13 UTC

I was not able to reproduce this. It is highly likely it was a contamination issue from a crownbay image that contains emgd-driver-bin.

Setting to resolved-invalid.

Comment 5 Stoicescu Cornel 2013-04-11 13:53:30 UTC

Have not seen this since. Verified in master:cb4db44c14959ca76870cfaf02b5d314ac68ba8f