[OE-core] [PATCH 6/9] linux-yocto-dev: bump to v5.2-rc

[richard.purdie at linuxfoundation.org]

On Wed, 2019-07-10 at 10:21 -0400, Bruce Ashfield wrote:
> On Wed, Jul 10, 2019 at 10:15 AM Martin Hundebøll <martin at geanix.com>
> wrote:
> > Hi Bruce,
> > 
> > On 30/05/2019 14.44, bruce.ashfield at gmail.com wrote:
> > > From: Bruce Ashfield <bruce.ashfield at gmail.com>
> > > 
> > > Signed-off-by: Bruce Ashfield <bruce.ashfield at gmail.com>
> > > ---
> > >   meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
> > >   1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb
> > > b/meta/recipes-kernel/linux/linux-yocto-dev.bb
> > > index ae8c343008..3a055c12ad 100644
> > > --- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
> > > +++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
> > > @@ -30,7 +30,7 @@ SRC_URI = "git://git.yoctoproject.org/linux-
> > > yocto-dev.git;branch=${KBRANCH};name
> > >   SRCREV_machine ?= '${@oe.utils.conditional("PREFERRED_PROVIDER_
> > > virtual/kernel", "linux-yocto-dev", "${AUTOREV}",
> > > "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
> > >   SRCREV_meta ?= '${@oe.utils.conditional("PREFERRED_PROVIDER_vir
> > > tual/kernel", "linux-yocto-dev", "${AUTOREV}",
> > > "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
> > > 
> > > -LINUX_VERSION ?= "5.0-rc+"
> > > +LINUX_VERSION ?= "5.2-rc+"
> > >   LINUX_VERSION_EXTENSION ?= "-yoctodev-${LINUX_KERNEL_TYPE}"
> > >   PV = "${LINUX_VERSION}+git${SRCPV}"
> > 
> > My own kernel recipe (more or less mainline) failed to build when I
> > bumped to v5.2. It fails to generate the out-of-tree Makefile due
> > to a
> > missing dependency on `realpath`[1].
> > 
> > The quick-fix is to add coreutils-native to DEPENDS, but I am not
> > sure
> > if this is what we want.
> > 
> > Have you seen the same?
> 
> Nope, I haven't seen that. But then again, all my machines have
> realpath available.
> 
> As you hinted, building all of coreutils as a dependency for the
> kernel is a bit heavy. We could make
> realpath a host requirement,  or otherwise, split out realpath (but
> you'd still need to build coreutils, so
> that really doesn't help).
> 
> I'd lean towards just making it a host requirement .. but I'm sure
> Richard can advise better than me
> on the pro's and con's of the options.

realpath is in the standard HOSTTOOLS in bitbake.conf so its already
required?

Cheers,

Richard