[meta-intel] emgd-driver-dev and libgl-mesa-dev packaging conflict

[Darren Hart]

On 04/18/2013 07:37 PM, Kamble, Nitin A wrote:
> 
> 
>> -----Original Message-----
>> From: meta-intel-bounces at yoctoproject.org [mailto:meta-intel-
>> bounces at yoctoproject.org] On Behalf Of Kamble, Nitin A
>> Sent: Thursday, April 18, 2013 5:11 PM
>> To: Zanussi, Tom; Darren Hart
>> Cc: meta-intel at yoctoproject.org
>> Subject: Re: [meta-intel] emgd-driver-dev and libgl-mesa-dev packaging
>> conflict
>>
>>
>>
>>> -----Original Message-----
>>> From: Zanussi, Tom
>>> Sent: Thursday, April 18, 2013 4:57 PM
>>> To: Darren Hart
>>> Cc: Kamble, Nitin A; meta-intel at yoctoproject.org
>>> Subject: Re: emgd-driver-dev and libgl-mesa-dev packaging conflict
>>>
>>> On Thu, 2013-04-18 at 15:04 -0700, Darren Hart wrote:
>>>>
>>>> On 04/18/2013 02:50 PM, Tom Zanussi wrote:
>>>>> On Thu, 2013-04-18 at 14:44 -0700, Darren Hart wrote:
>>>>>>
>>>>>> On 04/18/2013 02:38 PM, Tom Zanussi wrote:
>>>>>>> On Thu, 2013-04-18 at 14:31 -0700, Darren Hart wrote:
>>>>>>>> Tom and Nitin,
>>>>>>>>
>>>>>>>> I see the following building for the minnow, which uses the
>>>>>>>> meta-intel/common emgd recipes. This is using the master branch
>>>>>>>> of poky and meta-intel.
>>>>>>>>
>>>>>>>> Have you built core-image-sato-sdk with the current set of recipes?
>>>>>>>>
>>>>>>>
>>>>>>> I haven't built core-image-sato-sdk with the current heads, but
>>>>>>> I usually do add tools-profile to my builds and the autobuilder
>>>>>>> builds core-image-sato-sdk, and hasn't had this problem.
>>>>>>>
>>>>>>> What do you have in your local.conf?
>>>>>>
>>>>>> Things I add:
>>>>>>
>>>>>> LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin"
>>>>>
>>>>> Oh, and how about adding 'commercial'?
>>>>
>>>> OK, added and the gst-ffmpeg stuff gets added. Still fails as described.
>>>>
>>>
>>> crownbay with 'commercial' etc built fine (core-image-sato-sdk with rpm).
>>
>>
>> With IPK packaging I am able to reproduce the issue. I think this can be easily
>> avoided by reverting this commit
>>
>> commit 5e314278e4cf37b7fbb2946f4f42a3236071e131
>> Author: Laurentiu Palcu <laurentiu.palcu at intel.com>
>> Date:   Wed Mar 13 13:05:48 2013 +0200
>>
>>     emgd-driver-bin: add pkgconfig files
>>
>>     Add pkgconfig files needed by other projects (for example newer libva
>>     packages look for egl.pc file).
>>
>>     Pkgconfig files added by this patch:
>>      * egl.pc
>>      * gl.pc
>>      * gles_cm.pc
>>      * glesv2.pc
>>
>>     Signed-off-by: Laurentiu Palcu <laurentiu.palcu at intel.com>
>>     Signed-off-by: Tom Zanussi <tom.zanussi at linux.intel.com>
>>
>>
>>
>> This commit was needed for newer libva, now we have pinned EMGD based
>> BSPs to older libva, so this commit is not really needed.
> 
> I verified that this indeed fixes the issue.

It more like hides the issue right?

The problem seems to be a continued conflict between emgd and mesa
supplying the same files.

Seems to me we need something like the anonymous python in the meta-intel
mesa bbappend from:

commit 1a5ab65544830dd571a368b9d9f6ec782ffc94ac
Author: Nitin A Kamble <nitin.a.kamble at intel.com>
Date:   Tue Oct 30 14:38:34 2012 -0700

    mesa-dri.bbappend: avoid conflict with emgd-driver-bin

Right?

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel