On Tue, Jul 11, 2017 at 10:27 AM, Jussi Kukkonen <jussi.kukko...@intel.com> wrote:
> On 11 July 2017 at 10:42, Jussi Kukkonen <jussi.kukko...@intel.com> wrote: >> >> Exception: FileExistsError: [Errno 17] File exists: >>> '/home/gizero/work/smartliving/distro/repo-master/build-poky >>> /tmp/sysroots-components/raspberrypi3/userland/usr/include/KHR/khrplatform.h' >>> -> '/home/gizero/work/smartliving/distro/repo-master/build-poky >>> /tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/gtk+3/3.2 >>> 2.16-r0/recipe-sysroot/usr/include/KHR/khrplatform.h' >>> >> >> /usr/include/KHR/khrplatform.h is the egl platform header file, provided >> by both mesa and RPI userland. Does mesa end up in your gtk+3 >> recipe-sysroot somehow? >> >> For clarity: this could be a bug but it is unlikely to be related to the >> libepoxy change (it does not use or ship the actual header file). >> >> > > Actually this was maybe fixed by Otavios upgrade to mesa 17.1.4 -- mesa > accidentally shipped khrplatform.h even when egl was disabled (which is > what mesa-gl in oe-core does). > > Make sure you have oe-core commit f0762f5bad3 (poky: 773d10873). > Yes I have it, and the cleansstate mentioned above makes me think it got used as expected. Indeed the commit you mention is part of the bunch of commits after pulling which I got my builds broken... I'm confused! Any idea how to figure out which recipe get considered first in gtk+3's do_prepare_recipe_sysroot and effectively deliver khrplatform.h to the recipe-sysroot?
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
