<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Jul 12, 2017 at 12:38 AM, Khem Raj <span dir="ltr"><<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Tue, Jul 11, 2017 at 3:02 PM, Andrea Galbusera <<a href="mailto:gizero@gmail.com">gizero@gmail.com</a>> wrote:<br>
><br>
><br>
> Il 11 lug 2017 8:00 PM, "Khem Raj" <<a href="mailto:raj.khem@gmail.com">raj.khem@gmail.com</a>> ha scritto:<br>
><br>
> On Tue, Jul 11, 2017 at 1:34 AM, Jussi Kukkonen<br>
> <<a href="mailto:jussi.kukkonen@intel.com">jussi.kukkonen@intel.com</a>> wrote:<br>
>> On 11 July 2017 at 11:27, Jussi Kukkonen <<a href="mailto:jussi.kukkonen@intel.com">jussi.kukkonen@intel.com</a>> wrote:<br>
>>><br>
>>> On 11 July 2017 at 10:42, Jussi Kukkonen <<a href="mailto:jussi.kukkonen@intel.com">jussi.kukkonen@intel.com</a>><br>
>>> wrote:<br>
>>>>><br>
>>>>> Exception: FileExistsError: [Errno 17] File exists:<br>
>>>>><br>
>>>>> '/home/gizero/work/<wbr>smartliving/distro/repo-<wbr>master/build-poky/tmp/<wbr>sysroots-components/<wbr>raspberrypi3/userland/usr/<wbr>include/KHR/khrplatform.h'<br>
>>>>> -><br>
>>>>><br>
>>>>> '/home/gizero/work/<wbr>smartliving/distro/repo-<wbr>master/build-poky/tmp/work/<wbr>cortexa7hf-neon-vfpv4-poky-<wbr>linux-gnueabi/gtk+3/3.22.16-<wbr>r0/recipe-sysroot/usr/include/<wbr>KHR/khrplatform.h'<br>
>>>><br>
>>>><br>
>>>> /usr/include/KHR/khrplatform.h is the egl platform header file, provided<br>
>>>> by both mesa and RPI userland. Does mesa end up in your gtk+3<br>
>>>> recipe-sysroot<br>
>>>> somehow?<br>
>>>><br>
>>>> For clarity: this could be a bug but it is unlikely to be related to the<br>
>>>> libepoxy change (it does not use or ship the actual header file).<br>
>>>><br>
>>><br>
>>><br>
>>> Actually this was maybe fixed by Otavios upgrade to mesa 17.1.4 -- mesa<br>
>>> accidentally shipped khrplatform.h even when egl was disabled (which is<br>
>>> what<br>
>>> mesa-gl in oe-core does).<br>
>>><br>
>><br>
>> Sorry, I've not had enough coffee. It was the other way round:<br>
>> khrplatform.h is the platform header that mesa now thinks is needed<br>
>> whether<br>
>> egl is enabled or not -- so they've started installing it in any case from<br>
>> 17.1.4 which means mesa-gl now provides khrplatform.h and thus conflicts<br>
>> with userland.<br>
>><br>
>> I don't know what the correct fix is yet, just wanted to correct my<br>
>> original<br>
>> wrong info.<br>
>><br>
><br>
> Post an update to sync this header for userland package.<br>
><br>
><br>
> Will this help solving the gtk+3 issue of mesa-gl and userland now both<br>
> providing the same header and causing recipe-sysroot construction to fail?<br>
<br>
</div></div>No it certainly would not. But we can then decide who provides it, in<br>
a easy way.<br>
</blockquote></div><br></div><div class="gmail_extra">I may be in the need to craft something locally to unbreak building with current master... Could you please shed some light on how this should be done then? Is this a matter of completely removing either mesa-gl or userland from gtk+3 deps or a more selective change to avoid the clash in recipe-sysroot?</div></div>