Error when recompiling linux-ti-staging kernel

Error when recompiling linux-ti-staging kernel

[Craig McQueen]

I'm using meta-ti with Poky dizzy to build linux-ti-staging 3.14.x for a BeagleBone Black based system.

When I do a rebuild of linux-ti-staging, it does most of the compile but then fails with an error:

| touch: cannot touch '/home/craigm/yocto/poky/<boardname>/tmp/work/<boardname>-poky-linux-gnueabi/linux-ti-staging/3.14.39-r22b+gitrAUTOINC+ba552b4bc7/image/lib/modules/3.14.39/build': Permission denied
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compileconfigs (log file is located at /home/craigm/yocto/poky/<boardname>/tmp/work/<boardname>-poky-linux-gnueabi/linux-ti-staging/3.14.39-r22b+gitrAUTOINC+ba552b4bc7/temp/log.do_compileconfigs.4657)

Checking that file, I find that it's a symlink that points to /usr/src/kernel, which doesn't exist.

My current work-around is to do "bitbake linux-ti-staging -c clean" then rebuild my image. It works fine as long as it's a fresh build. But that slows down the development cycle.

Why might this be happening?

-- 
Craig McQueen

Re: Error when recompiling linux-ti-staging kernel

[Denys Dmytriyenko]

On Thu, Apr 30, 2015 at 10:50:12AM +1000, Craig McQueen wrote:
> I'm using meta-ti with Poky dizzy to build linux-ti-staging 3.14.x for a 
> BeagleBone Black based system.
> 
> When I do a rebuild of linux-ti-staging, it does most of the compile but 
> then fails with an error:
> 
> | touch: cannot touch '/home/craigm/yocto/poky/<boardname>/tmp/work/<boardname>-poky-linux-gnueabi/linux-ti-staging/3.14.39-r22b+gitrAUTOINC+ba552b4bc7/image/lib/modules/3.14.39/build': Permission denied
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_compileconfigs (log file is located at /home/craigm/yocto/poky/<boardname>/tmp/work/<boardname>-poky-linux-gnueabi/linux-ti-staging/3.14.39-r22b+gitrAUTOINC+ba552b4bc7/temp/log.do_compileconfigs.4657)
> 
> Checking that file, I find that it's a symlink that points to 
> /usr/src/kernel, which doesn't exist.
> 
> My current work-around is to do "bitbake linux-ti-staging -c clean" then 
> rebuild my image. It works fine as long as it's a fresh build. But that 
> slows down the development cycle.
> 
> Why might this be happening?

Hmm, interesting. Which branch of meta-ti do you use for dizzy?

-- 
Denys

Re: Error when recompiling linux-ti-staging kernel

[Craig McQueen]

> -----Original Message-----
> From: Denys Dmytriyenko [mailto:denys@ti.com]
> Sent: Saturday, 2 May 2015 6:03 AM
> To: Craig McQueen
> Cc: meta-ti@yoctoproject.org
> Subject: Re: [meta-ti] Error when recompiling linux-ti-staging kernel
> 
> On Thu, Apr 30, 2015 at 10:50:12AM +1000, Craig McQueen wrote:
> > I'm using meta-ti with Poky dizzy to build linux-ti-staging 3.14.x for
> > a BeagleBone Black based system.
> >
> > When I do a rebuild of linux-ti-staging, it does most of the compile
> > but then fails with an error:
> >
> > | touch: cannot touch
> > | '/home/craigm/yocto/poky/<boardname>/tmp/work/<boardname>-
> poky-linux
> > | -gnueabi/linux-ti-staging/3.14.39-r22b+gitrAUTOINC+ba552b4bc7/image/
> > | lib/modules/3.14.39/build': Permission denied
> > | WARNING: exit code 1 from a shell command.
> > | ERROR: Function failed: do_compileconfigs (log file is located at
> > | /home/craigm/yocto/poky/<boardname>/tmp/work/<boardname>-
> poky-linux-
> > | gnueabi/linux-ti-staging/3.14.39-r22b+gitrAUTOINC+ba552b4bc7/temp/lo
> > | g.do_compileconfigs.4657)
> >
> > Checking that file, I find that it's a symlink that points to
> > /usr/src/kernel, which doesn't exist.
> >
> > My current work-around is to do "bitbake linux-ti-staging -c clean"
> > then rebuild my image. It works fine as long as it's a fresh build.
> > But that slows down the development cycle.
> >
> > Why might this be happening?
> 
> Hmm, interesting. Which branch of meta-ti do you use for dizzy?

I've been using meta-ti master branch. I don't think meta-ti even has a dizzy branch (although it does have a daisy branch).

-- 
Craig McQueen

Re: Error when recompiling linux-ti-staging kernel

[Craig McQueen]

> -----Original Message-----
> From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-
> bounces@yoctoproject.org] On Behalf Of Craig McQueen
> Sent: Tuesday, 5 May 2015 10:17 AM
> To: Denys Dmytriyenko <denys@ti.com>
> Cc: meta-ti@yoctoproject.org
> Subject: Re: [meta-ti] Error when recompiling linux-ti-staging kernel
> 
> > -----Original Message-----
> > From: Denys Dmytriyenko [mailto:denys@ti.com]
> > Sent: Saturday, 2 May 2015 6:03 AM
> > To: Craig McQueen
> > Cc: meta-ti@yoctoproject.org
> > Subject: Re: [meta-ti] Error when recompiling linux-ti-staging kernel
> >
> > On Thu, Apr 30, 2015 at 10:50:12AM +1000, Craig McQueen wrote:
> > > I'm using meta-ti with Poky dizzy to build linux-ti-staging 3.14.x
> > > for a BeagleBone Black based system.
> > >
> > > When I do a rebuild of linux-ti-staging, it does most of the compile
> > > but then fails with an error:
> > >
> > > | touch: cannot touch
> > > | '/home/craigm/yocto/poky/<boardname>/tmp/work/<boardname>-
> > poky-linux
> > > | -gnueabi/linux-ti-staging/3.14.39-r22b+gitrAUTOINC+ba552b4bc7/imag
> > > | e/
> > > | lib/modules/3.14.39/build': Permission denied
> > > | WARNING: exit code 1 from a shell command.
> > > | ERROR: Function failed: do_compileconfigs (log file is located at
> > > | /home/craigm/yocto/poky/<boardname>/tmp/work/<boardname>-
> > poky-linux-
> > > | gnueabi/linux-ti-staging/3.14.39-r22b+gitrAUTOINC+ba552b4bc7/temp/
> > > | lo
> > > | g.do_compileconfigs.4657)
> > >
> > > Checking that file, I find that it's a symlink that points to
> > > /usr/src/kernel, which doesn't exist.
> > >
> > > My current work-around is to do "bitbake linux-ti-staging -c clean"
> > > then rebuild my image. It works fine as long as it's a fresh build.
> > > But that slows down the development cycle.
> > >
> > > Why might this be happening?
> >
> > Hmm, interesting. Which branch of meta-ti do you use for dizzy?
> 
> I've been using meta-ti master branch. I don't think meta-ti even has a dizzy
> branch (although it does have a daisy branch).

This seems to be due to the following line in multi-kernel.inc:

    touch "${D}/lib/modules/${KERNEL_VERSION}/build"

I'm not sure what purpose it's intended to serve, but it's problematic. (I can see it's being used to build a "systest" kernel, although why it's doing that, I'm not yet sure.)

-- 
Craig McQueen