[OE-core] new meta-oe failures from master-next

[Khem Raj]

On Thu, Oct 24, 2019 at 9:15 AM <richard.purdie at linuxfoundation.org> wrote:
>
> On Wed, 2019-10-23 at 23:52 +0100, Khem Raj wrote:
> > On Wed, Oct 23, 2019 at 8:31 PM Richard Purdie
> > <richard.purdie at linuxfoundation.org> wrote:
> > > On Wed, 2019-10-23 at 16:29 +0100, Ross Burton wrote:
> > > > On 23/10/2019 14:03, Khem Raj wrote:
> > > > > Hi Richard
> > > > >
> > > > > New master-next I see these fails
> > > > >
> > > > > https://errors.yoctoproject.org/Errors/Build/91645/
> > > > >
> > > > > First two are important one's we already know why
> > > > > ti-display-sharing-fw fails to fetch
> > > >
> > > > ERROR: QA Issue: libiio: Files/directories were installed but not
> > > > shipped in any package:
> > > >    /usr/lib/python2.7
> > > >    /usr/lib/python2.7/site-packages
> > > >    /usr/lib/python2.7/site-packages/libiio-0.18-py2.7.egg-info
> > > >    /usr/lib/python2.7/site-packages/iio.pyc
> > > >    /usr/lib/python2.7/site-packages/iio.py
> > > >
> > > > That may have been triggered by some change in oe-core but that's
> > > > definitely an issue with libiio.
> > >
> > > Its from this cmake change:
> > >
> > > http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=dbba06d9153ae588c9496b40e5db18b3602bfad1
> > >
> >
> > I think its causing more failures, where suddenly, the recipes are
> > now
> > resorting to native python, is this patch correct I wonder ?
> >
> > see
> > https://git.openembedded.org/meta-openembedded-contrib/commit/?h=yoe/mut&id=5d02e814bc7d30f925b2eeec85eb053cec516f26
> >
> > https://git.openembedded.org/meta-openembedded-contrib/commit/?h=yoe/mut&id=3ab0af60e8512cbb718e8a0112d9c9aa98c620a4
>
> The cmake change makes python visible from HOSTTOOLS. That isn't wrong
> as such, it is a change in behaviour. If recipes don't set python
> enabled/disabled explicitly, there is some fallout from that. I'd say
> that is a bug in those recipes which aren't giving explicit
> configuration to dependencies though.
>

So now the behavior is interesting. It works fine if I build for a
machine where host-arch = target-arch
so if someone is building for x86_64 then they dont see the build
failures. IMO thats worse.

> Cheers,
>
> RIchard
>
>
>