Migration from 1.7.1 to 1.8 - kernel-abiversion missing

Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Schaumlöffel, Jan]

[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]

Hi everyone,

I have a working root fs based on "dizzy", for which I created a customized machine config, a custom package config recipe and a custom image recipe.
When running into problems with the python installation on that rootfs I decided to upgrade to Poky 1.8 "fido".

So I checked out the "fido" branches of the following repositories:

-          git.yoctoproject.org/git/poky

-          github.com/openembedded/openembedded-core.git

-          github.com/openembedded/meta-openembedded.git

After that, a lot of packages were rebuilt (obviously), but everything seemed to work, excluding the last step:

NOTE: Executing buildhistory_get_image_installed ...
DEBUG: Executing shell function buildhistory_get_image_installed
DEBUG: Shell function buildhistory_get_image_installed finished
NOTE: Executing: ldconfig -/.../mymachine -poky-linux-gnueabi/mymachine-image/1.0-r0/rootfs-c new -v
ERROR: No kernel-abiversion file found (/.../pkgdata/kernel-depmod/kernel-abiversion), cannot run depmod, aborting
DEBUG: Python function do_rootfs finished
ERROR: Function failed: do_rootfs

I already verified that a completely "vanilla" setup from these repositories (i.e. source oe-init-build-env into empty directory, then bitbake core-image-minimal) does indeed complete.
The problem is re-introduced as soon as I do not build with MACHINE ?= "beaglebone" but with my own machine configuration. Naturally I compared the configurations without finding anything too suspicious.

So, before I go into any further lengths about my machine configuration: Are there any general hints why the "kernel-abiversion" file might go missing after migrating from 1.7 to 1.8?

KR and TIA,
Jan

[-- Attachment #2: Type: text/html, Size: 10283 bytes --]

Re: Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Bruce Ashfield]

On 2015-04-28 02:49 AM, Schaumlöffel, Jan wrote:
> Hi everyone,
>
> I have a working root fs based on “dizzy”, for which I created a
> customized machine config, a custom package config recipe and a custom
> image recipe.
>
> When running into problems with the python installation on that rootfs I
> decided to upgrade to Poky 1.8 “fido”.
>
> So I checked out the “fido” branches of the following repositories:
>
> -git.yoctoproject.org/git/poky
>
> -github.com/openembedded/openembedded-core.git
>
> -github.com/openembedded/meta-openembedded.git
>
> After that, a lot of packages were rebuilt (obviously), but everything
> seemed to work, excluding the last step:
>
> NOTE: Executing buildhistory_get_image_installed ...
>
> DEBUG: Executing shell function buildhistory_get_image_installed
>
> DEBUG: Shell function buildhistory_get_image_installed finished
>
> NOTE: Executing: ldconfig -/…/mymachine
> -poky-linux-gnueabi/mymachine-image/1.0-r0/rootfs-c new -v
>
> ERROR: No kernel-abiversion file found
> (/…/pkgdata/kernel-depmod/kernel-abiversion), cannot run depmod, aborting
>
> DEBUG: Python function do_rootfs finished
>
> ERROR: Function failed: do_rootfs
>
> I already verified that a completely “vanilla” setup from these
> repositories (i.e. source oe-init-build-env into empty directory, then
> bitbake core-image-minimal) does indeed complete.
>
> The problem is re-introduced as soon as I do not build with MACHINE ?=
> “beaglebone” but with my own machine configuration. Naturally I compared
> the configurations without finding anything too suspicious.
>
> So, before I go into any further lengths about my machine configuration:
> Are there any general hints why the “kernel-abiversion” file might go
> missing after migrating from 1.7 to 1.8?

Hmmm. It shouldn't have gone missing. Bits of the kernel build
outputs did move around in 1.8, but the abiversion is still
generated and placed in the STAGING_KERNEL_BUILDDIR.

As for modules, it is placed in the PKGDESTWORK directory as part
of packaging.

After your build has failed, if you look in STAGING_KERNEL_BUILDDIR
do you see the abiversion file ?

Bruce


>
> KR and TIA,
>
> Jan
>
>
>

Re: Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Schaumlöffel, Jan]

> Hmmm. It shouldn't have gone missing. Bits of the kernel build outputs 
> did move around in 1.8, but the abiversion is still generated and 
> placed in the STAGING_KERNEL_BUILDDIR.

I was just wondering, is there an easy way to resolve these Paths from the command line? I do not have a lot of experience with bitbake, so I have no good guess where STAGING_KERNEL_BUILDDIR should be located.
 
Also, I don't quite get why the kernel abiversion and kernel modules are needed at all, because I build the kernel externally with no modules at all. Although in the future it might be nice to integrate building the kernel into the bitbake process, at the moment I would be equally happy to just leave off everything that has to do with the kernel.

> After your build has failed, if you look in STAGING_KERNEL_BUILDDIR do 
> you see the abiversion file ?

There are three instances of the file:

~/yocto-build-fido$ find . -name kernel-abiversion
./tmp/work/beaglebone-poky-linux-gnueabi/linux-yocto/3.14.36+gitAUTOINC+162dfe3bb0_dbe5b52e93-r0/pkgdata/kernel-depmod/kernel-abiversion
./tmp/sysroots/beaglebone/pkgdata/kernel-depmod/kernel-abiversion
./tmp/work-shared/beaglebone/kernel-build-artifacts/kernel-abiversion

Jan

Re: Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Bruce Ashfield]

On 2015-04-28 11:36 AM, Schaumlöffel, Jan wrote:
>> Hmmm. It shouldn't have gone missing. Bits of the kernel build outputs
>> did move around in 1.8, but the abiversion is still generated and
>> placed in the STAGING_KERNEL_BUILDDIR.
>
> I was just wondering, is there an easy way to resolve these Paths from the ommand line? I do not have a lot of experience with bitbake, so I have no good guess where STAGING_KERNEL_BUILDDIR should be located.

I always just run bitbake -e <your target>, and then either grep or
capture the output. The value and places the variable are set will be
in the bulk data export. Others may have fancier ways to do the
same thing.

>
> Also, I don't quite get why the kernel abiversion and kernel modules are needed at all, because I build the kernel externally with no modules at all. Although in the future it might be nice to integrate building the kernel into the bitbake process, at the moment I would be equally happy to just leave off everything that has to do with the kernel.

Have you tried setting linux-dummy as the preferred provider for the
kernel ? That would skip the build processing doing anything more than
satisfying the various kernel dependencies.

>
>> After your build has failed, if you look in STAGING_KERNEL_BUILDDIR do
>> you see the abiversion file ?
>
> There are three instances of the file:
>
> ~/yocto-build-fido$ find . -name kernel-abiversion
> ./tmp/work/beaglebone-poky-linux-gnueabi/linux-yocto/3.14.36+gitAUTOINC+162dfe3bb0_dbe5b52e93-r0/pkgdata/kernel-depmod/kernel-abiversion
> ./tmp/sysroots/beaglebone/pkgdata/kernel-depmod/kernel-abiversion
> ./tmp/work-shared/beaglebone/kernel-build-artifacts/kernel-abiversion

Those are where I'd expect them for 1.8, so they should be found and
used by the various parts of the build process. Something different
is happening in your build .. hmm.

Bruce

>
> Jan
>

Re: Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Schaumlöffel, Jan]

> Have you tried setting linux-dummy as the preferred provider for the kernel
> ? That would skip the build processing doing anything more than satisfying
> the various kernel dependencies.

Ah, that's a good hint, I'll try that.

> >
> >> After your build has failed, if you look in STAGING_KERNEL_BUILDDIR
> >> do you see the abiversion file ?
> >
> > There are three instances of the file:
> >
> > ~/yocto-build-fido$ find . -name kernel-abiversion
> > ./tmp/work/beaglebone-poky-linux-gnueabi/linux-
> yocto/3.14.36+gitAUTOIN
> > C+162dfe3bb0_dbe5b52e93-r0/pkgdata/kernel-depmod/kernel-abiversion
> > ./tmp/sysroots/beaglebone/pkgdata/kernel-depmod/kernel-abiversion
> > ./tmp/work-shared/beaglebone/kernel-build-artifacts/kernel-abiversion
> 
> Those are where I'd expect them for 1.8, so they should be found and used
> by the various parts of the build process. Something different is happening in
> your build .. hmm.

It looks like those were from another run, built from scratch in a new directory I now see the following result:


NOTE: Executing RunQueue Tasks
ERROR: No kernel-abiversion file found (/home/astro/yocto-build-reproduce/tmp/sysroots/u159/pkgdata/kernel-depmod/kernel-abiversion), cannot run depmod, aborting
ERROR: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /home/astro/yocto-build-reproduce/tmp/work/u159-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.7440
ERROR: Task 7 (/home/astro/git/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1776 tasks of which 93 didn't need to be rerun and 1 failed.
No currently running tasks (1775 of 1777)

Summary: 1 task failed:
  /home/astro/git/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
astro@eldk-vm:~/yocto-build-reproduce$ find . -name kernel-abiversion
astro@eldk-vm:~/yocto-build-reproduce$ bitbake -e core-image-minimal | grep STAGING_KERNEL_BUILDDIR
# $STAGING_KERNEL_BUILDDIR
STAGING_KERNEL_BUILDDIR="/home/astro/yocto-build-reproduce/tmp/work-shared/u159/kernel-build-artifacts"
astro@eldk-vm:~/yocto-build-reproduce$ ls -la /home/astro/yocto-build-reproduce/tmp/work-shared/u159/kernel-build-artifacts
ls: cannot access /home/astro/yocto-build-reproduce/tmp/work-shared/u159/kernel-build-artifacts: No such file or directory
astro@eldk-vm:~/yocto-build-reproduce$

It looks like the entire STAGING_KERNEL_BUILDDIR is missing.


I'll try some more variatons of my setup to try and narrow down why that happens.

Jan

Re: Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Bruce Ashfield]

On 04/29/2015 03:38 AM, Schaumlöffel, Jan wrote:
>> Have you tried setting linux-dummy as the preferred provider for the kernel
>> ? That would skip the build processing doing anything more than satisfying
>> the various kernel dependencies.
>
> Ah, that's a good hint, I'll try that.
>
>>>
>>>> After your build has failed, if you look in STAGING_KERNEL_BUILDDIR
>>>> do you see the abiversion file ?
>>>
>>> There are three instances of the file:
>>>
>>> ~/yocto-build-fido$ find . -name kernel-abiversion
>>> ./tmp/work/beaglebone-poky-linux-gnueabi/linux-
>> yocto/3.14.36+gitAUTOIN
>>> C+162dfe3bb0_dbe5b52e93-r0/pkgdata/kernel-depmod/kernel-abiversion
>>> ./tmp/sysroots/beaglebone/pkgdata/kernel-depmod/kernel-abiversion
>>> ./tmp/work-shared/beaglebone/kernel-build-artifacts/kernel-abiversion
>>
>> Those are where I'd expect them for 1.8, so they should be found and used
>> by the various parts of the build process. Something different is happening in
>> your build .. hmm.
>
> It looks like those were from another run, built from scratch in a new directory I now see the following result:
>
>
> NOTE: Executing RunQueue Tasks
> ERROR: No kernel-abiversion file found (/home/astro/yocto-build-reproduce/tmp/sysroots/u159/pkgdata/kernel-depmod/kernel-abiversion), cannot run depmod, aborting
> ERROR: Function failed: do_rootfs
> ERROR: Logfile of failure stored in: /home/astro/yocto-build-reproduce/tmp/work/u159-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.7440
> ERROR: Task 7 (/home/astro/git/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 1776 tasks of which 93 didn't need to be rerun and 1 failed.
> No currently running tasks (1775 of 1777)
>
> Summary: 1 task failed:
>    /home/astro/git/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs
> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
> astro@eldk-vm:~/yocto-build-reproduce$ find . -name kernel-abiversion
> astro@eldk-vm:~/yocto-build-reproduce$ bitbake -e core-image-minimal | grep STAGING_KERNEL_BUILDDIR
> # $STAGING_KERNEL_BUILDDIR
> STAGING_KERNEL_BUILDDIR="/home/astro/yocto-build-reproduce/tmp/work-shared/u159/kernel-build-artifacts"
> astro@eldk-vm:~/yocto-build-reproduce$ ls -la /home/astro/yocto-build-reproduce/tmp/work-shared/u159/kernel-build-artifacts
> ls: cannot access /home/astro/yocto-build-reproduce/tmp/work-shared/u159/kernel-build-artifacts: No such file or directory
> astro@eldk-vm:~/yocto-build-reproduce$
>
> It looks like the entire STAGING_KERNEL_BUILDDIR is missing.
>
>
> I'll try some more variatons of my setup to try and narrow down why that happens.
>

That is really odd. I'll be interested to hear how that happened. I just
did a test and it points to where I expect:

  [/home/bruc...poky/build]> bitbake -e core-image-minimal | grep 
STAGING_KERNEL_BUILDDIR
# $STAGING_KERNEL_BUILDDIR
STAGING_KERNEL_BUILDDIR="/home/bruce/poky/build/tmp/work-shared/qemux86-64/kernel-build-artifacts"

Bruce



> Jan
>

Re: Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Schaumlöffel, Jan]

> That is really odd. I'll be interested to hear how that happened. I just did a
> test and it points to where I expect:
> 
>   [/home/bruc...poky/build]> bitbake -e core-image-minimal | grep
> STAGING_KERNEL_BUILDDIR # $STAGING_KERNEL_BUILDDIR
> STAGING_KERNEL_BUILDDIR="/home/bruce/poky/build/tmp/work-
> shared/qemux86-64/kernel-build-artifacts"
>

So I experimented a bit more and found a minimal set of steps to reproduce the problem. Maybe that might give someone a clue as to what is happening and/or how to resolve it.

Steps to reproduce:

- clone Poky repository, checkout branch 'fido'
- go to meta-yocto-bsp/conf/machine and copy beaglebone.conf to another file (I used astro.conf)
- from poky repository do source oe-init-build-env into new build directory
- edit conf/local.conf to set MACHINE ?= "astro" (use filename from second step) and DL_DIR (if present)
- run bitbake core-image-minimal

-> kernel-abiversion is missing, build fails

- edit conf/local.conf, set MACHINE ?= "beaglebone"
- run bitbake core-image-minimal

-> image builds fine

It stays the same if the copied config is in a custom BSP layer, some minor modifications are made, etc., but to eliminate complexity I just put that into the meta-yocto-bsp layer. What strikes me as really odd is that now the only thing changed between working and non-working configuration seems to be the filename of the machine configuration - what am I missing?

How do I create a working machine configuration for Poky 1.8? (In 1.7.1 I just took some machine configuration from eldk, fiddled around with it a bit, put it into my BSP layer and never had any trouble with that.)

Regards,
Jan

Re: Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Bruce Ashfield]

On 2015-04-30 3:14 AM, Schaumlöffel, Jan wrote:
>> That is really odd. I'll be interested to hear how that happened. I just did a
>> test and it points to where I expect:
>>
>>    [/home/bruc...poky/build]> bitbake -e core-image-minimal | grep
>> STAGING_KERNEL_BUILDDIR # $STAGING_KERNEL_BUILDDIR
>> STAGING_KERNEL_BUILDDIR="/home/bruce/poky/build/tmp/work-
>> shared/qemux86-64/kernel-build-artifacts"
>>
>
> So I experimented a bit more and found a minimal set of steps to reproduce the problem. Maybe that might give someone a clue as to what is happening and/or how to resolve it.
>
> Steps to reproduce:
>
> - clone Poky repository, checkout branch 'fido'
> - go to meta-yocto-bsp/conf/machine and copy beaglebone.conf to another file (I used astro.conf)
> - from poky repository do source oe-init-build-env into new build directory
> - edit conf/local.conf to set MACHINE ?= "astro" (use filename from second step) and DL_DIR (if present)
> - run bitbake core-image-minimal
>
> -> kernel-abiversion is missing, build fails
>
> - edit conf/local.conf, set MACHINE ?= "beaglebone"
> - run bitbake core-image-minimal
>
> -> image builds fine
>
> It stays the same if the copied config is in a custom BSP layer, some minor modifications are made, etc., but to eliminate complexity I just put that into the meta-yocto-bsp layer. What strikes me as really odd is that now the only thing changed between working and non-working configuration seems to be the filename of the machine configuration - what am I missing?
>

What kernel recipe is used when your machine is set to 'astro' ?
Something custom ? Or have you added machine compatibility to
another known kernel recipe ?

The big difference that I see would be the kernel recipe, and
some of the tasks not executing (and hence not generating the
abiversion file).

Bruce

> How do I create a working machine configuration for Poky 1.8? (In 1.7.1 I just took some machine configuration from eldk, fiddled around with it a bit, put it into my BSP layer and never had any trouble with that.)
>
> Regards,
> Jan
>

Re: Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Schaumlöffel, Jan]

> What kernel recipe is used when your machine is set to 'astro' ?
> Something custom ? Or have you added machine compatibility to another
> known kernel recipe ?

How would I see which kernel recipe is used?

I did not customize anything except for aforementioned steps, simply copied beaglebone.conf to astro.conf in the same directory. Also I did not touch any kernel recipes (kernel is built externally), maybe that's what's missing?

Jan

Re: Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Bruce Ashfield]

On 2015-04-30 08:27 AM, Schaumlöffel, Jan wrote:
>> What kernel recipe is used when your machine is set to 'astro' ?
>> Something custom ? Or have you added machine compatibility to another
>> known kernel recipe ?
>
> How would I see which kernel recipe is used?

This is where my brute force techniques probably break down. I just
do a 'bitbake virtual/kernel' and you'll see it display which
recipe is being built.

If you haven't added compatibility for your new machine to any
recipe, I'm betting that linux-dummy is used.

>
> I did not customize anything except for aforementioned steps, simply copied beaglebone.conf to astro.conf in the same directory. Also I did not touch any kernel recipes (kernel is built externally), maybe that's what's missing?

It is plausible. But in theory, linux-dummy should still provide
what you need (but since it doesn't build anything, there is
no abi .. and no modules can be built against it) .. so the
error isn't graceful.

Bruce

>
> Jan
>

Re: Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
<bruce.ashfield@windriver.com> wrote:
> It is plausible. But in theory, linux-dummy should still provide
> what you need (but since it doesn't build anything, there is
> no abi .. and no modules can be built against it) .. so the
> error isn't graceful.
>
> Bruce

I can confirm this same problem is happening to me.  I just updated
one of my builds from 1.7 to 1.8 and am also getting my rootfs to fail
due to no abi kernel version:

ERROR: No kernel-abiversion file found
(/home/hutch/yocto_1.8_davinci/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
cannot run depmod, aborting
ERROR: Function failed: do_rootfs
ERROR: Logfile of failure stored in:
/home/hutch/yocto_1.8_davinci/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.23558
ERROR: Task 7 (/home/hutch/yocto_1.8_davinci/poky/meta/recipes-core/images/core-image-nodeam.bb,
do_rootfs) failed with exit code '1'

This is for an AM1808 build.  I'm using fido branch of yocto and
openembedded and master of meta-ti (since it doesn't have a fido
branch yet).

STAGING_KERNEL_BUILDDIR="/home/hutch/yocto_1.8_davinci/poky/build/tmp/work-shared/am180x-evm/kernel-build-artifacts"

I didn't do anything different in my local.conf than what I normally
do.  linux-dummy was also built with my last yocto 1.7 build and it
didn't have this problem.

Regards,

Brian

Re: [yocto] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
<bruce.ashfield@windriver.com> wrote:
> It is plausible. But in theory, linux-dummy should still provide
> what you need (but since it doesn't build anything, there is
> no abi .. and no modules can be built against it) .. so the
> error isn't graceful.
>
> Bruce

I can confirm this same problem is happening to me.  I just updated
one of my builds from 1.7 to 1.8 and am also getting my rootfs to fail
due to no abi kernel version:

ERROR: No kernel-abiversion file found
(/home/hutch/yocto_1.8_davinci/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
cannot run depmod, aborting
ERROR: Function failed: do_rootfs
ERROR: Logfile of failure stored in:
/home/hutch/yocto_1.8_davinci/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.23558
ERROR: Task 7 (/home/hutch/yocto_1.8_davinci/poky/meta/recipes-core/images/core-image-nodeam.bb,
do_rootfs) failed with exit code '1'

This is for an AM1808 build.  I'm using fido branch of yocto and
openembedded and master of meta-ti (since it doesn't have a fido
branch yet).

STAGING_KERNEL_BUILDDIR="/home/hutch/yocto_1.8_davinci/poky/build/tmp/work-shared/am180x-evm/kernel-build-artifacts"

I didn't do anything different in my local.conf than what I normally
do.  linux-dummy was also built with my last yocto 1.7 build and it
didn't have this problem.

Regards,

Brian

Re: Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Mon, May 11, 2015 at 2:10 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
>> It is plausible. But in theory, linux-dummy should still provide
>> what you need (but since it doesn't build anything, there is
>> no abi .. and no modules can be built against it) .. so the
>> error isn't graceful.
>>
>> Bruce
>
> I can confirm this same problem is happening to me.  I just updated
> one of my builds from 1.7 to 1.8 and am also getting my rootfs to fail
> due to no abi kernel version:
>
> ERROR: No kernel-abiversion file found
> (/home/hutch/yocto_1.8_davinci/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
> cannot run depmod, aborting
> ERROR: Function failed: do_rootfs
> ERROR: Logfile of failure stored in:
> /home/hutch/yocto_1.8_davinci/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.23558
> ERROR: Task 7 (/home/hutch/yocto_1.8_davinci/poky/meta/recipes-core/images/core-image-nodeam.bb,
> do_rootfs) failed with exit code '1'
>
> This is for an AM1808 build.  I'm using fido branch of yocto and
> openembedded and master of meta-ti (since it doesn't have a fido
> branch yet).
>
> STAGING_KERNEL_BUILDDIR="/home/hutch/yocto_1.8_davinci/poky/build/tmp/work-shared/am180x-evm/kernel-build-artifacts"
>
> I didn't do anything different in my local.conf than what I normally
> do.  linux-dummy was also built with my last yocto 1.7 build and it
> didn't have this problem.
>
> Regards,
>
> Brian

Is this where these messages are coming from?

Richard's patch [OE-core] [PATCH] kernel: Fix depmod for multilib
http://lists.openembedded.org/pipermail/openembedded-core/2015-January/101171.html

Regards,

Brian

Re: [yocto] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Mon, May 11, 2015 at 2:10 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
>> It is plausible. But in theory, linux-dummy should still provide
>> what you need (but since it doesn't build anything, there is
>> no abi .. and no modules can be built against it) .. so the
>> error isn't graceful.
>>
>> Bruce
>
> I can confirm this same problem is happening to me.  I just updated
> one of my builds from 1.7 to 1.8 and am also getting my rootfs to fail
> due to no abi kernel version:
>
> ERROR: No kernel-abiversion file found
> (/home/hutch/yocto_1.8_davinci/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
> cannot run depmod, aborting
> ERROR: Function failed: do_rootfs
> ERROR: Logfile of failure stored in:
> /home/hutch/yocto_1.8_davinci/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.23558
> ERROR: Task 7 (/home/hutch/yocto_1.8_davinci/poky/meta/recipes-core/images/core-image-nodeam.bb,
> do_rootfs) failed with exit code '1'
>
> This is for an AM1808 build.  I'm using fido branch of yocto and
> openembedded and master of meta-ti (since it doesn't have a fido
> branch yet).
>
> STAGING_KERNEL_BUILDDIR="/home/hutch/yocto_1.8_davinci/poky/build/tmp/work-shared/am180x-evm/kernel-build-artifacts"
>
> I didn't do anything different in my local.conf than what I normally
> do.  linux-dummy was also built with my last yocto 1.7 build and it
> didn't have this problem.
>
> Regards,
>
> Brian

Is this where these messages are coming from?

Richard's patch [OE-core] [PATCH] kernel: Fix depmod for multilib
http://lists.openembedded.org/pipermail/openembedded-core/2015-January/101171.html

Regards,

Brian

Re: Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Bruce Ashfield]

On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
>> It is plausible. But in theory, linux-dummy should still provide
>> what you need (but since it doesn't build anything, there is
>> no abi .. and no modules can be built against it) .. so the
>> error isn't graceful.
>>
>> Bruce
>
> I can confirm this same problem is happening to me.  I just updated
> one of my builds from 1.7 to 1.8 and am also getting my rootfs to fail
> due to no abi kernel version:

We still have a race condition in the 1.8 branch for the population
of the build-artifacts directory.

If modules start building, they'll race against the population of the
abiversion, and you may see that message.

There's a proposed patch for master, but I don't think it is in
fido yet.

Bruce

>
> ERROR: No kernel-abiversion file found
> (/home/hutch/yocto_1.8_davinci/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
> cannot run depmod, aborting
> ERROR: Function failed: do_rootfs
> ERROR: Logfile of failure stored in:
> /home/hutch/yocto_1.8_davinci/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.23558
> ERROR: Task 7 (/home/hutch/yocto_1.8_davinci/poky/meta/recipes-core/images/core-image-nodeam.bb,
> do_rootfs) failed with exit code '1'
>
> This is for an AM1808 build.  I'm using fido branch of yocto and
> openembedded and master of meta-ti (since it doesn't have a fido
> branch yet).
>
> STAGING_KERNEL_BUILDDIR="/home/hutch/yocto_1.8_davinci/poky/build/tmp/work-shared/am180x-evm/kernel-build-artifacts"
>
> I didn't do anything different in my local.conf than what I normally
> do.  linux-dummy was also built with my last yocto 1.7 build and it
> didn't have this problem.
>
> Regards,
>
> Brian
>

Re: [yocto] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Bruce Ashfield]

On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
>> It is plausible. But in theory, linux-dummy should still provide
>> what you need (but since it doesn't build anything, there is
>> no abi .. and no modules can be built against it) .. so the
>> error isn't graceful.
>>
>> Bruce
>
> I can confirm this same problem is happening to me.  I just updated
> one of my builds from 1.7 to 1.8 and am also getting my rootfs to fail
> due to no abi kernel version:

We still have a race condition in the 1.8 branch for the population
of the build-artifacts directory.

If modules start building, they'll race against the population of the
abiversion, and you may see that message.

There's a proposed patch for master, but I don't think it is in
fido yet.

Bruce

>
> ERROR: No kernel-abiversion file found
> (/home/hutch/yocto_1.8_davinci/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
> cannot run depmod, aborting
> ERROR: Function failed: do_rootfs
> ERROR: Logfile of failure stored in:
> /home/hutch/yocto_1.8_davinci/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.23558
> ERROR: Task 7 (/home/hutch/yocto_1.8_davinci/poky/meta/recipes-core/images/core-image-nodeam.bb,
> do_rootfs) failed with exit code '1'
>
> This is for an AM1808 build.  I'm using fido branch of yocto and
> openembedded and master of meta-ti (since it doesn't have a fido
> branch yet).
>
> STAGING_KERNEL_BUILDDIR="/home/hutch/yocto_1.8_davinci/poky/build/tmp/work-shared/am180x-evm/kernel-build-artifacts"
>
> I didn't do anything different in my local.conf than what I normally
> do.  linux-dummy was also built with my last yocto 1.7 build and it
> didn't have this problem.
>
> Regards,
>
> Brian
>

Re: Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
<bruce.ashfield@windriver.com> wrote:
> On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>
>> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>> <bruce.ashfield@windriver.com> wrote:
>>>
>>> It is plausible. But in theory, linux-dummy should still provide
>>> what you need (but since it doesn't build anything, there is
>>> no abi .. and no modules can be built against it) .. so the
>>> error isn't graceful.
>>>
>>> Bruce
>>
>>
>> I can confirm this same problem is happening to me.  I just updated
>> one of my builds from 1.7 to 1.8 and am also getting my rootfs to fail
>> due to no abi kernel version:
>
>
> We still have a race condition in the 1.8 branch for the population
> of the build-artifacts directory.
>
> If modules start building, they'll race against the population of the
> abiversion, and you may see that message.
>
> There's a proposed patch for master, but I don't think it is in
> fido yet.
>
> Bruce

Hi Bruce,

I did some searches and looks like there are a number of 'race'
condition fixes but it wasn't obvious which one I may need.  Is it
this one:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98

Regards,

Brian

Re: [yocto] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
<bruce.ashfield@windriver.com> wrote:
> On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>
>> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>> <bruce.ashfield@windriver.com> wrote:
>>>
>>> It is plausible. But in theory, linux-dummy should still provide
>>> what you need (but since it doesn't build anything, there is
>>> no abi .. and no modules can be built against it) .. so the
>>> error isn't graceful.
>>>
>>> Bruce
>>
>>
>> I can confirm this same problem is happening to me.  I just updated
>> one of my builds from 1.7 to 1.8 and am also getting my rootfs to fail
>> due to no abi kernel version:
>
>
> We still have a race condition in the 1.8 branch for the population
> of the build-artifacts directory.
>
> If modules start building, they'll race against the population of the
> abiversion, and you may see that message.
>
> There's a proposed patch for master, but I don't think it is in
> fido yet.
>
> Bruce

Hi Bruce,

I did some searches and looks like there are a number of 'race'
condition fixes but it wasn't obvious which one I may need.  Is it
this one:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98

Regards,

Brian

Re: Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Bruce Ashfield]

On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
> On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
>> On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>
>>> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>> <bruce.ashfield@windriver.com> wrote:
>>>>
>>>> It is plausible. But in theory, linux-dummy should still provide
>>>> what you need (but since it doesn't build anything, there is
>>>> no abi .. and no modules can be built against it) .. so the
>>>> error isn't graceful.
>>>>
>>>> Bruce
>>>
>>>
>>> I can confirm this same problem is happening to me.  I just updated
>>> one of my builds from 1.7 to 1.8 and am also getting my rootfs to fail
>>> due to no abi kernel version:
>>
>>
>> We still have a race condition in the 1.8 branch for the population
>> of the build-artifacts directory.
>>
>> If modules start building, they'll race against the population of the
>> abiversion, and you may see that message.
>>
>> There's a proposed patch for master, but I don't think it is in
>> fido yet.
>>
>> Bruce
>
> Hi Bruce,
>
> I did some searches and looks like there are a number of 'race'
> condition fixes but it wasn't obvious which one I may need.  Is it
> this one:
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>

That's the one that should make sure that the shared workdir
(Which has the abiversion) is in place before building any modules.

I can't say that it is exactly your issue, but it is the change
I was thinking of.

Bruce

> Regards,
>
> Brian
>

Re: [yocto] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Bruce Ashfield]

On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
> On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
>> On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>
>>> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>> <bruce.ashfield@windriver.com> wrote:
>>>>
>>>> It is plausible. But in theory, linux-dummy should still provide
>>>> what you need (but since it doesn't build anything, there is
>>>> no abi .. and no modules can be built against it) .. so the
>>>> error isn't graceful.
>>>>
>>>> Bruce
>>>
>>>
>>> I can confirm this same problem is happening to me.  I just updated
>>> one of my builds from 1.7 to 1.8 and am also getting my rootfs to fail
>>> due to no abi kernel version:
>>
>>
>> We still have a race condition in the 1.8 branch for the population
>> of the build-artifacts directory.
>>
>> If modules start building, they'll race against the population of the
>> abiversion, and you may see that message.
>>
>> There's a proposed patch for master, but I don't think it is in
>> fido yet.
>>
>> Bruce
>
> Hi Bruce,
>
> I did some searches and looks like there are a number of 'race'
> condition fixes but it wasn't obvious which one I may need.  Is it
> this one:
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>

That's the one that should make sure that the shared workdir
(Which has the abiversion) is in place before building any modules.

I can't say that it is exactly your issue, but it is the change
I was thinking of.

Bruce

> Regards,
>
> Brian
>

Re: [meta-ti] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Denys Dmytriyenko]

On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
> On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
> >On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
> ><bruce.ashfield@windriver.com> wrote:
> >>On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
> >>>
> >>>On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
> >>><bruce.ashfield@windriver.com> wrote:
> >>>>
> >>>>It is plausible. But in theory, linux-dummy should still provide
> >>>>what you need (but since it doesn't build anything, there is
> >>>>no abi .. and no modules can be built against it) .. so the
> >>>>error isn't graceful.
> >>>>
> >>>>Bruce
> >>>
> >>>
> >>>I can confirm this same problem is happening to me.  I just updated
> >>>one of my builds from 1.7 to 1.8 and am also getting my rootfs to fail
> >>>due to no abi kernel version:
> >>
> >>
> >>We still have a race condition in the 1.8 branch for the population
> >>of the build-artifacts directory.
> >>
> >>If modules start building, they'll race against the population of the
> >>abiversion, and you may see that message.
> >>
> >>There's a proposed patch for master, but I don't think it is in
> >>fido yet.
> >>
> >>Bruce
> >
> >Hi Bruce,
> >
> >I did some searches and looks like there are a number of 'race'
> >condition fixes but it wasn't obvious which one I may need.  Is it
> >this one:
> >http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
> >
> 
> That's the one that should make sure that the shared workdir
> (Which has the abiversion) is in place before building any modules.
> 
> I can't say that it is exactly your issue, but it is the change
> I was thinking of.

Brian,

Were you able to try the above mentioned commit against am180x in meta-ti? Did 
it solve the missing abi kernel version? Thanks.

-- 
Denys

Re: [yocto] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Denys Dmytriyenko]

On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
> On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
> >On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
> ><bruce.ashfield@windriver.com> wrote:
> >>On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
> >>>
> >>>On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
> >>><bruce.ashfield@windriver.com> wrote:
> >>>>
> >>>>It is plausible. But in theory, linux-dummy should still provide
> >>>>what you need (but since it doesn't build anything, there is
> >>>>no abi .. and no modules can be built against it) .. so the
> >>>>error isn't graceful.
> >>>>
> >>>>Bruce
> >>>
> >>>
> >>>I can confirm this same problem is happening to me.  I just updated
> >>>one of my builds from 1.7 to 1.8 and am also getting my rootfs to fail
> >>>due to no abi kernel version:
> >>
> >>
> >>We still have a race condition in the 1.8 branch for the population
> >>of the build-artifacts directory.
> >>
> >>If modules start building, they'll race against the population of the
> >>abiversion, and you may see that message.
> >>
> >>There's a proposed patch for master, but I don't think it is in
> >>fido yet.
> >>
> >>Bruce
> >
> >Hi Bruce,
> >
> >I did some searches and looks like there are a number of 'race'
> >condition fixes but it wasn't obvious which one I may need.  Is it
> >this one:
> >http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
> >
> 
> That's the one that should make sure that the shared workdir
> (Which has the abiversion) is in place before building any modules.
> 
> I can't say that it is exactly your issue, but it is the change
> I was thinking of.

Brian,

Were you able to try the above mentioned commit against am180x in meta-ti? Did 
it solve the missing abi kernel version? Thanks.

-- 
Denys

Re: [meta-ti] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 2213 bytes --]

On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>
> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
> > On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
> > >On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
> > ><bruce.ashfield@windriver.com> wrote:
> > >>On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
> > >>>
> > >>>On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
> > >>><bruce.ashfield@windriver.com> wrote:
> > >>>>
> > >>>>It is plausible. But in theory, linux-dummy should still provide
> > >>>>what you need (but since it doesn't build anything, there is
> > >>>>no abi .. and no modules can be built against it) .. so the
> > >>>>error isn't graceful.
> > >>>>
> > >>>>Bruce
> > >>>
> > >>>
> > >>>I can confirm this same problem is happening to me.  I just updated
> > >>>one of my builds from 1.7 to 1.8 and am also getting my rootfs to
fail
> > >>>due to no abi kernel version:
> > >>
> > >>
> > >>We still have a race condition in the 1.8 branch for the population
> > >>of the build-artifacts directory.
> > >>
> > >>If modules start building, they'll race against the population of the
> > >>abiversion, and you may see that message.
> > >>
> > >>There's a proposed patch for master, but I don't think it is in
> > >>fido yet.
> > >>
> > >>Bruce
> > >
> > >Hi Bruce,
> > >
> > >I did some searches and looks like there are a number of 'race'
> > >condition fixes but it wasn't obvious which one I may need.  Is it
> > >this one:
> > >
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
> > >
> >
> > That's the one that should make sure that the shared workdir
> > (Which has the abiversion) is in place before building any modules.
> >
> > I can't say that it is exactly your issue, but it is the change
> > I was thinking of.
>
> Brian,
>
> Were you able to try the above mentioned commit against am180x in
meta-ti? Did
> it solve the missing abi kernel version? Thanks.
>
> --
> Denys

Hi Denys,

No, I got caught up in something else ... I'll try it tomorrow and report
back after I cherry pick that commit Bruce mentioned.

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 3405 bytes --]

Re: [yocto] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 2213 bytes --]

On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>
> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
> > On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
> > >On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
> > ><bruce.ashfield@windriver.com> wrote:
> > >>On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
> > >>>
> > >>>On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
> > >>><bruce.ashfield@windriver.com> wrote:
> > >>>>
> > >>>>It is plausible. But in theory, linux-dummy should still provide
> > >>>>what you need (but since it doesn't build anything, there is
> > >>>>no abi .. and no modules can be built against it) .. so the
> > >>>>error isn't graceful.
> > >>>>
> > >>>>Bruce
> > >>>
> > >>>
> > >>>I can confirm this same problem is happening to me.  I just updated
> > >>>one of my builds from 1.7 to 1.8 and am also getting my rootfs to
fail
> > >>>due to no abi kernel version:
> > >>
> > >>
> > >>We still have a race condition in the 1.8 branch for the population
> > >>of the build-artifacts directory.
> > >>
> > >>If modules start building, they'll race against the population of the
> > >>abiversion, and you may see that message.
> > >>
> > >>There's a proposed patch for master, but I don't think it is in
> > >>fido yet.
> > >>
> > >>Bruce
> > >
> > >Hi Bruce,
> > >
> > >I did some searches and looks like there are a number of 'race'
> > >condition fixes but it wasn't obvious which one I may need.  Is it
> > >this one:
> > >
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
> > >
> >
> > That's the one that should make sure that the shared workdir
> > (Which has the abiversion) is in place before building any modules.
> >
> > I can't say that it is exactly your issue, but it is the change
> > I was thinking of.
>
> Brian,
>
> Were you able to try the above mentioned commit against am180x in
meta-ti? Did
> it solve the missing abi kernel version? Thanks.
>
> --
> Denys

Hi Denys,

No, I got caught up in something else ... I'll try it tomorrow and report
back after I cherry pick that commit Bruce mentioned.

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 3405 bytes --]

Re: [meta-ti] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>>
>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>> > On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>> > >On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>> > ><bruce.ashfield@windriver.com> wrote:
>> > >>On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>> > >>>
>> > >>>On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>> > >>><bruce.ashfield@windriver.com> wrote:
>> > >>>>
>> > >>>>It is plausible. But in theory, linux-dummy should still provide
>> > >>>>what you need (but since it doesn't build anything, there is
>> > >>>>no abi .. and no modules can be built against it) .. so the
>> > >>>>error isn't graceful.
>> > >>>>
>> > >>>>Bruce
>> > >>>
>> > >>>
>> > >>>I can confirm this same problem is happening to me.  I just updated
>> > >>>one of my builds from 1.7 to 1.8 and am also getting my rootfs to
>> > >>> fail
>> > >>>due to no abi kernel version:
>> > >>
>> > >>
>> > >>We still have a race condition in the 1.8 branch for the population
>> > >>of the build-artifacts directory.
>> > >>
>> > >>If modules start building, they'll race against the population of the
>> > >>abiversion, and you may see that message.
>> > >>
>> > >>There's a proposed patch for master, but I don't think it is in
>> > >>fido yet.
>> > >>
>> > >>Bruce
>> > >
>> > >Hi Bruce,
>> > >
>> > >I did some searches and looks like there are a number of 'race'
>> > >condition fixes but it wasn't obvious which one I may need.  Is it
>> > >this one:
>> >
>> > > >http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>> > >
>> >
>> > That's the one that should make sure that the shared workdir
>> > (Which has the abiversion) is in place before building any modules.
>> >
>> > I can't say that it is exactly your issue, but it is the change
>> > I was thinking of.
>>
>> Brian,
>>
>> Were you able to try the above mentioned commit against am180x in meta-ti?
>> Did
>> it solve the missing abi kernel version? Thanks.
>>
>> --
>> Denys
>
> Hi Denys,
>
> No, I got caught up in something else ... I'll try it tomorrow and report
> back after I cherry pick that commit Bruce mentioned.
>
> Regards,
>
> Brian

Update.  Not sure if I did this right but this is what I did.  I added
master as a remote and cherry picked
02d0a003d603266114512160b209876199241e98.  Next I just went for it and
tried to bitbake my image again and got the same result as before.
Next I did a bitbake cleanall on virtual/kernel and tried to make my
image again and still got the same result.

I'm going to leave this build as is and setup a new one using 1.8
master and see if I get the same thing again.  I'll leave this broken
build alone for a while in case someone wants me to try something with
it to fix it.

Regards,

Brian

Re: [yocto] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>>
>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>> > On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>> > >On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>> > ><bruce.ashfield@windriver.com> wrote:
>> > >>On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>> > >>>
>> > >>>On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>> > >>><bruce.ashfield@windriver.com> wrote:
>> > >>>>
>> > >>>>It is plausible. But in theory, linux-dummy should still provide
>> > >>>>what you need (but since it doesn't build anything, there is
>> > >>>>no abi .. and no modules can be built against it) .. so the
>> > >>>>error isn't graceful.
>> > >>>>
>> > >>>>Bruce
>> > >>>
>> > >>>
>> > >>>I can confirm this same problem is happening to me.  I just updated
>> > >>>one of my builds from 1.7 to 1.8 and am also getting my rootfs to
>> > >>> fail
>> > >>>due to no abi kernel version:
>> > >>
>> > >>
>> > >>We still have a race condition in the 1.8 branch for the population
>> > >>of the build-artifacts directory.
>> > >>
>> > >>If modules start building, they'll race against the population of the
>> > >>abiversion, and you may see that message.
>> > >>
>> > >>There's a proposed patch for master, but I don't think it is in
>> > >>fido yet.
>> > >>
>> > >>Bruce
>> > >
>> > >Hi Bruce,
>> > >
>> > >I did some searches and looks like there are a number of 'race'
>> > >condition fixes but it wasn't obvious which one I may need.  Is it
>> > >this one:
>> >
>> > > >http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>> > >
>> >
>> > That's the one that should make sure that the shared workdir
>> > (Which has the abiversion) is in place before building any modules.
>> >
>> > I can't say that it is exactly your issue, but it is the change
>> > I was thinking of.
>>
>> Brian,
>>
>> Were you able to try the above mentioned commit against am180x in meta-ti?
>> Did
>> it solve the missing abi kernel version? Thanks.
>>
>> --
>> Denys
>
> Hi Denys,
>
> No, I got caught up in something else ... I'll try it tomorrow and report
> back after I cherry pick that commit Bruce mentioned.
>
> Regards,
>
> Brian

Update.  Not sure if I did this right but this is what I did.  I added
master as a remote and cherry picked
02d0a003d603266114512160b209876199241e98.  Next I just went for it and
tried to bitbake my image again and got the same result as before.
Next I did a bitbake cleanall on virtual/kernel and tried to make my
image again and still got the same result.

I'm going to leave this build as is and setup a new one using 1.8
master and see if I get the same thing again.  I'll leave this broken
build alone for a while in case someone wants me to try something with
it to fix it.

Regards,

Brian

Re: [meta-ti] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>
>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>>>
>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>> > On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>> > >On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>> > ><bruce.ashfield@windriver.com> wrote:
>>> > >>On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>> > >>>
>>> > >>>On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>> > >>><bruce.ashfield@windriver.com> wrote:
>>> > >>>>
>>> > >>>>It is plausible. But in theory, linux-dummy should still provide
>>> > >>>>what you need (but since it doesn't build anything, there is
>>> > >>>>no abi .. and no modules can be built against it) .. so the
>>> > >>>>error isn't graceful.
>>> > >>>>
>>> > >>>>Bruce
>>> > >>>
>>> > >>>
>>> > >>>I can confirm this same problem is happening to me.  I just updated
>>> > >>>one of my builds from 1.7 to 1.8 and am also getting my rootfs to
>>> > >>> fail
>>> > >>>due to no abi kernel version:
>>> > >>
>>> > >>
>>> > >>We still have a race condition in the 1.8 branch for the population
>>> > >>of the build-artifacts directory.
>>> > >>
>>> > >>If modules start building, they'll race against the population of the
>>> > >>abiversion, and you may see that message.
>>> > >>
>>> > >>There's a proposed patch for master, but I don't think it is in
>>> > >>fido yet.
>>> > >>
>>> > >>Bruce
>>> > >
>>> > >Hi Bruce,
>>> > >
>>> > >I did some searches and looks like there are a number of 'race'
>>> > >condition fixes but it wasn't obvious which one I may need.  Is it
>>> > >this one:
>>> >
>>> > > >http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>> > >
>>> >
>>> > That's the one that should make sure that the shared workdir
>>> > (Which has the abiversion) is in place before building any modules.
>>> >
>>> > I can't say that it is exactly your issue, but it is the change
>>> > I was thinking of.
>>>
>>> Brian,
>>>
>>> Were you able to try the above mentioned commit against am180x in meta-ti?
>>> Did
>>> it solve the missing abi kernel version? Thanks.
>>>
>>> --
>>> Denys
>>
>> Hi Denys,
>>
>> No, I got caught up in something else ... I'll try it tomorrow and report
>> back after I cherry pick that commit Bruce mentioned.
>>
>> Regards,
>>
>> Brian
>
> Update.  Not sure if I did this right but this is what I did.  I added
> master as a remote and cherry picked
> 02d0a003d603266114512160b209876199241e98.  Next I just went for it and
> tried to bitbake my image again and got the same result as before.
> Next I did a bitbake cleanall on virtual/kernel and tried to make my
> image again and still got the same result.
>
> I'm going to leave this build as is and setup a new one using 1.8
> master and see if I get the same thing again.  I'll leave this broken
> build alone for a while in case someone wants me to try something with
> it to fix it.
>
> Regards,
>
> Brian

Yet another update ... I did a fresh checkout of master and tried to
build and had the same kernelabiversion error:

WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
now#######################
                                                          | ETA:
00:00:28
WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for now
WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
now########################################

 | ETA:  00:00:26
Parsing recipes: 100%
|##############################################################################################################################################################################|
Time: 00:01:02
Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
targets, 182 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: multiple providers are available for u-boot (u-boot,
u-boot-glsdk, u-boot-ti-staging)
NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg

Build Configuration:
BB_VERSION        = "1.27.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Debian-7.8"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "am180x-evm"
DISTRO            = "poky"
DISTRO_VERSION    = "1.8+snapshot-20150515"
TUNE_FEATURES     = "arm armv5 thumb dsp"
TARGET_FPU        = "soft"
meta
meta-yocto
meta-yocto-bsp    = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
meta-ti           = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
meta-oe
meta-python
meta-networking
meta-webserver    = "master:53d55216c8c721d3b66ec8f968737bf081def870"

NOTE: Preparing RunQueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
apache2-dev requires /usr/bin/perl, but no providers found in its
RDEPENDS [file-rdeps]
ERROR: No kernel-abiversion file found
(/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
cannot run depmod, aborting
ERROR: Function failed: do_rootfs
ERROR: Logfile of failure stored in:
/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
ERROR: Task 7 (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to be
rerun and 1 failed.
Waiting for 0 running tasks to finish:

Summary: 1 task failed:
  /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
do_rootfs
Summary: There were 4 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

Re: [yocto] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>
>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>>>
>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>> > On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>> > >On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>> > ><bruce.ashfield@windriver.com> wrote:
>>> > >>On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>> > >>>
>>> > >>>On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>> > >>><bruce.ashfield@windriver.com> wrote:
>>> > >>>>
>>> > >>>>It is plausible. But in theory, linux-dummy should still provide
>>> > >>>>what you need (but since it doesn't build anything, there is
>>> > >>>>no abi .. and no modules can be built against it) .. so the
>>> > >>>>error isn't graceful.
>>> > >>>>
>>> > >>>>Bruce
>>> > >>>
>>> > >>>
>>> > >>>I can confirm this same problem is happening to me.  I just updated
>>> > >>>one of my builds from 1.7 to 1.8 and am also getting my rootfs to
>>> > >>> fail
>>> > >>>due to no abi kernel version:
>>> > >>
>>> > >>
>>> > >>We still have a race condition in the 1.8 branch for the population
>>> > >>of the build-artifacts directory.
>>> > >>
>>> > >>If modules start building, they'll race against the population of the
>>> > >>abiversion, and you may see that message.
>>> > >>
>>> > >>There's a proposed patch for master, but I don't think it is in
>>> > >>fido yet.
>>> > >>
>>> > >>Bruce
>>> > >
>>> > >Hi Bruce,
>>> > >
>>> > >I did some searches and looks like there are a number of 'race'
>>> > >condition fixes but it wasn't obvious which one I may need.  Is it
>>> > >this one:
>>> >
>>> > > >http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>> > >
>>> >
>>> > That's the one that should make sure that the shared workdir
>>> > (Which has the abiversion) is in place before building any modules.
>>> >
>>> > I can't say that it is exactly your issue, but it is the change
>>> > I was thinking of.
>>>
>>> Brian,
>>>
>>> Were you able to try the above mentioned commit against am180x in meta-ti?
>>> Did
>>> it solve the missing abi kernel version? Thanks.
>>>
>>> --
>>> Denys
>>
>> Hi Denys,
>>
>> No, I got caught up in something else ... I'll try it tomorrow and report
>> back after I cherry pick that commit Bruce mentioned.
>>
>> Regards,
>>
>> Brian
>
> Update.  Not sure if I did this right but this is what I did.  I added
> master as a remote and cherry picked
> 02d0a003d603266114512160b209876199241e98.  Next I just went for it and
> tried to bitbake my image again and got the same result as before.
> Next I did a bitbake cleanall on virtual/kernel and tried to make my
> image again and still got the same result.
>
> I'm going to leave this build as is and setup a new one using 1.8
> master and see if I get the same thing again.  I'll leave this broken
> build alone for a while in case someone wants me to try something with
> it to fix it.
>
> Regards,
>
> Brian

Yet another update ... I did a fresh checkout of master and tried to
build and had the same kernelabiversion error:

WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
now#######################
                                                          | ETA:
00:00:28
WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for now
WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
now########################################

 | ETA:  00:00:26
Parsing recipes: 100%
|##############################################################################################################################################################################|
Time: 00:01:02
Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
targets, 182 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: multiple providers are available for u-boot (u-boot,
u-boot-glsdk, u-boot-ti-staging)
NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg

Build Configuration:
BB_VERSION        = "1.27.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Debian-7.8"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "am180x-evm"
DISTRO            = "poky"
DISTRO_VERSION    = "1.8+snapshot-20150515"
TUNE_FEATURES     = "arm armv5 thumb dsp"
TARGET_FPU        = "soft"
meta
meta-yocto
meta-yocto-bsp    = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
meta-ti           = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
meta-oe
meta-python
meta-networking
meta-webserver    = "master:53d55216c8c721d3b66ec8f968737bf081def870"

NOTE: Preparing RunQueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
apache2-dev requires /usr/bin/perl, but no providers found in its
RDEPENDS [file-rdeps]
ERROR: No kernel-abiversion file found
(/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
cannot run depmod, aborting
ERROR: Function failed: do_rootfs
ERROR: Logfile of failure stored in:
/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
ERROR: Task 7 (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to be
rerun and 1 failed.
Waiting for 0 running tasks to finish:

Summary: 1 task failed:
  /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
do_rootfs
Summary: There were 4 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

Re: [meta-ti] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
> On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>>
>>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>>>>
>>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>>> > On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>>> > >On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>>> > ><bruce.ashfield@windriver.com> wrote:
>>>> > >>On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>> > >>>
>>>> > >>>On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>>> > >>><bruce.ashfield@windriver.com> wrote:
>>>> > >>>>
>>>> > >>>>It is plausible. But in theory, linux-dummy should still provide
>>>> > >>>>what you need (but since it doesn't build anything, there is
>>>> > >>>>no abi .. and no modules can be built against it) .. so the
>>>> > >>>>error isn't graceful.
>>>> > >>>>
>>>> > >>>>Bruce
>>>> > >>>
>>>> > >>>
>>>> > >>>I can confirm this same problem is happening to me.  I just updated
>>>> > >>>one of my builds from 1.7 to 1.8 and am also getting my rootfs to
>>>> > >>> fail
>>>> > >>>due to no abi kernel version:
>>>> > >>
>>>> > >>
>>>> > >>We still have a race condition in the 1.8 branch for the population
>>>> > >>of the build-artifacts directory.
>>>> > >>
>>>> > >>If modules start building, they'll race against the population of the
>>>> > >>abiversion, and you may see that message.
>>>> > >>
>>>> > >>There's a proposed patch for master, but I don't think it is in
>>>> > >>fido yet.
>>>> > >>
>>>> > >>Bruce
>>>> > >
>>>> > >Hi Bruce,
>>>> > >
>>>> > >I did some searches and looks like there are a number of 'race'
>>>> > >condition fixes but it wasn't obvious which one I may need.  Is it
>>>> > >this one:
>>>> >
>>>> > > >http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>>> > >
>>>> >
>>>> > That's the one that should make sure that the shared workdir
>>>> > (Which has the abiversion) is in place before building any modules.
>>>> >
>>>> > I can't say that it is exactly your issue, but it is the change
>>>> > I was thinking of.
>>>>
>>>> Brian,
>>>>
>>>> Were you able to try the above mentioned commit against am180x in meta-ti?
>>>> Did
>>>> it solve the missing abi kernel version? Thanks.
>>>>
>>>> --
>>>> Denys
>>>
>>> Hi Denys,
>>>
>>> No, I got caught up in something else ... I'll try it tomorrow and report
>>> back after I cherry pick that commit Bruce mentioned.
>>>
>>> Regards,
>>>
>>> Brian
>>
>> Update.  Not sure if I did this right but this is what I did.  I added
>> master as a remote and cherry picked
>> 02d0a003d603266114512160b209876199241e98.  Next I just went for it and
>> tried to bitbake my image again and got the same result as before.
>> Next I did a bitbake cleanall on virtual/kernel and tried to make my
>> image again and still got the same result.
>>
>> I'm going to leave this build as is and setup a new one using 1.8
>> master and see if I get the same thing again.  I'll leave this broken
>> build alone for a while in case someone wants me to try something with
>> it to fix it.
>>
>> Regards,
>>
>> Brian
>
> Yet another update ... I did a fresh checkout of master and tried to
> build and had the same kernelabiversion error:
>
> WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
> now#######################
>                                                           | ETA:
> 00:00:28
> WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for now
> WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
> now########################################
>
>  | ETA:  00:00:26
> Parsing recipes: 100%
> |##############################################################################################################################################################################|
> Time: 00:01:02
> Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
> targets, 182 skipped, 0 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
> NOTE: multiple providers are available for u-boot (u-boot,
> u-boot-glsdk, u-boot-ti-staging)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
> NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
>
> Build Configuration:
> BB_VERSION        = "1.27.0"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "Debian-7.8"
> TARGET_SYS        = "arm-poky-linux-gnueabi"
> MACHINE           = "am180x-evm"
> DISTRO            = "poky"
> DISTRO_VERSION    = "1.8+snapshot-20150515"
> TUNE_FEATURES     = "arm armv5 thumb dsp"
> TARGET_FPU        = "soft"
> meta
> meta-yocto
> meta-yocto-bsp    = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
> meta-ti           = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
> meta-oe
> meta-python
> meta-networking
> meta-webserver    = "master:53d55216c8c721d3b66ec8f968737bf081def870"
>
> NOTE: Preparing RunQueue
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
> apache2-dev requires /usr/bin/perl, but no providers found in its
> RDEPENDS [file-rdeps]
> ERROR: No kernel-abiversion file found
> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
> cannot run depmod, aborting
> ERROR: Function failed: do_rootfs
> ERROR: Logfile of failure stored in:
> /home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
> ERROR: Task 7 (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
> do_rootfs) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to be
> rerun and 1 failed.
> Waiting for 0 running tasks to finish:
>
> Summary: 1 task failed:
>   /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
> do_rootfs
> Summary: There were 4 WARNING messages shown.
> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

More info for those that care ...

The end of the error log file has:
DEBUG: Executing python function write_image_manifest
DEBUG: Python function write_image_manifest finished
NOTE: Executing: ldconfig
-r/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/rootfs-c
new -v
ERROR: No kernel-abiversion file found
(/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
cannot run depmod, aborting
DEBUG: Python function do_rootfs finished
ERROR: Function failed: do_rootfs

I have a linux-dummy director in pkgdata but no kernel-depmod directory exists.

Regards,

Brian

Re: [yocto] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
> On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>>
>>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>>>>
>>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>>> > On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>>> > >On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>>> > ><bruce.ashfield@windriver.com> wrote:
>>>> > >>On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>> > >>>
>>>> > >>>On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>>> > >>><bruce.ashfield@windriver.com> wrote:
>>>> > >>>>
>>>> > >>>>It is plausible. But in theory, linux-dummy should still provide
>>>> > >>>>what you need (but since it doesn't build anything, there is
>>>> > >>>>no abi .. and no modules can be built against it) .. so the
>>>> > >>>>error isn't graceful.
>>>> > >>>>
>>>> > >>>>Bruce
>>>> > >>>
>>>> > >>>
>>>> > >>>I can confirm this same problem is happening to me.  I just updated
>>>> > >>>one of my builds from 1.7 to 1.8 and am also getting my rootfs to
>>>> > >>> fail
>>>> > >>>due to no abi kernel version:
>>>> > >>
>>>> > >>
>>>> > >>We still have a race condition in the 1.8 branch for the population
>>>> > >>of the build-artifacts directory.
>>>> > >>
>>>> > >>If modules start building, they'll race against the population of the
>>>> > >>abiversion, and you may see that message.
>>>> > >>
>>>> > >>There's a proposed patch for master, but I don't think it is in
>>>> > >>fido yet.
>>>> > >>
>>>> > >>Bruce
>>>> > >
>>>> > >Hi Bruce,
>>>> > >
>>>> > >I did some searches and looks like there are a number of 'race'
>>>> > >condition fixes but it wasn't obvious which one I may need.  Is it
>>>> > >this one:
>>>> >
>>>> > > >http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>>> > >
>>>> >
>>>> > That's the one that should make sure that the shared workdir
>>>> > (Which has the abiversion) is in place before building any modules.
>>>> >
>>>> > I can't say that it is exactly your issue, but it is the change
>>>> > I was thinking of.
>>>>
>>>> Brian,
>>>>
>>>> Were you able to try the above mentioned commit against am180x in meta-ti?
>>>> Did
>>>> it solve the missing abi kernel version? Thanks.
>>>>
>>>> --
>>>> Denys
>>>
>>> Hi Denys,
>>>
>>> No, I got caught up in something else ... I'll try it tomorrow and report
>>> back after I cherry pick that commit Bruce mentioned.
>>>
>>> Regards,
>>>
>>> Brian
>>
>> Update.  Not sure if I did this right but this is what I did.  I added
>> master as a remote and cherry picked
>> 02d0a003d603266114512160b209876199241e98.  Next I just went for it and
>> tried to bitbake my image again and got the same result as before.
>> Next I did a bitbake cleanall on virtual/kernel and tried to make my
>> image again and still got the same result.
>>
>> I'm going to leave this build as is and setup a new one using 1.8
>> master and see if I get the same thing again.  I'll leave this broken
>> build alone for a while in case someone wants me to try something with
>> it to fix it.
>>
>> Regards,
>>
>> Brian
>
> Yet another update ... I did a fresh checkout of master and tried to
> build and had the same kernelabiversion error:
>
> WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
> now#######################
>                                                           | ETA:
> 00:00:28
> WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for now
> WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
> now########################################
>
>  | ETA:  00:00:26
> Parsing recipes: 100%
> |##############################################################################################################################################################################|
> Time: 00:01:02
> Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
> targets, 182 skipped, 0 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
> NOTE: multiple providers are available for u-boot (u-boot,
> u-boot-glsdk, u-boot-ti-staging)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
> NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
>
> Build Configuration:
> BB_VERSION        = "1.27.0"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "Debian-7.8"
> TARGET_SYS        = "arm-poky-linux-gnueabi"
> MACHINE           = "am180x-evm"
> DISTRO            = "poky"
> DISTRO_VERSION    = "1.8+snapshot-20150515"
> TUNE_FEATURES     = "arm armv5 thumb dsp"
> TARGET_FPU        = "soft"
> meta
> meta-yocto
> meta-yocto-bsp    = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
> meta-ti           = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
> meta-oe
> meta-python
> meta-networking
> meta-webserver    = "master:53d55216c8c721d3b66ec8f968737bf081def870"
>
> NOTE: Preparing RunQueue
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
> apache2-dev requires /usr/bin/perl, but no providers found in its
> RDEPENDS [file-rdeps]
> ERROR: No kernel-abiversion file found
> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
> cannot run depmod, aborting
> ERROR: Function failed: do_rootfs
> ERROR: Logfile of failure stored in:
> /home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
> ERROR: Task 7 (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
> do_rootfs) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to be
> rerun and 1 failed.
> Waiting for 0 running tasks to finish:
>
> Summary: 1 task failed:
>   /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
> do_rootfs
> Summary: There were 4 WARNING messages shown.
> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

More info for those that care ...

The end of the error log file has:
DEBUG: Executing python function write_image_manifest
DEBUG: Python function write_image_manifest finished
NOTE: Executing: ldconfig
-r/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/rootfs-c
new -v
ERROR: No kernel-abiversion file found
(/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
cannot run depmod, aborting
DEBUG: Python function do_rootfs finished
ERROR: Function failed: do_rootfs

I have a linux-dummy director in pkgdata but no kernel-depmod directory exists.

Regards,

Brian

Re: [meta-ti] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Bruce Ashfield]

On Fri, May 15, 2015 at 4:21 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
> On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>> On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>>>
>>>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>>>>>
>>>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>>>> > On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>>>> > >On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>>>> > ><bruce.ashfield@windriver.com> wrote:
>>>>> > >>On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>>> > >>>
>>>>> > >>>On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>>>> > >>><bruce.ashfield@windriver.com> wrote:
>>>>> > >>>>
>>>>> > >>>>It is plausible. But in theory, linux-dummy should still provide
>>>>> > >>>>what you need (but since it doesn't build anything, there is
>>>>> > >>>>no abi .. and no modules can be built against it) .. so the
>>>>> > >>>>error isn't graceful.
>>>>> > >>>>
>>>>> > >>>>Bruce
>>>>> > >>>
>>>>> > >>>
>>>>> > >>>I can confirm this same problem is happening to me.  I just updated
>>>>> > >>>one of my builds from 1.7 to 1.8 and am also getting my rootfs to
>>>>> > >>> fail
>>>>> > >>>due to no abi kernel version:
>>>>> > >>
>>>>> > >>
>>>>> > >>We still have a race condition in the 1.8 branch for the population
>>>>> > >>of the build-artifacts directory.
>>>>> > >>
>>>>> > >>If modules start building, they'll race against the population of the
>>>>> > >>abiversion, and you may see that message.
>>>>> > >>
>>>>> > >>There's a proposed patch for master, but I don't think it is in
>>>>> > >>fido yet.
>>>>> > >>
>>>>> > >>Bruce
>>>>> > >
>>>>> > >Hi Bruce,
>>>>> > >
>>>>> > >I did some searches and looks like there are a number of 'race'
>>>>> > >condition fixes but it wasn't obvious which one I may need.  Is it
>>>>> > >this one:
>>>>> >
>>>>> > > >http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>>>> > >
>>>>> >
>>>>> > That's the one that should make sure that the shared workdir
>>>>> > (Which has the abiversion) is in place before building any modules.
>>>>> >
>>>>> > I can't say that it is exactly your issue, but it is the change
>>>>> > I was thinking of.
>>>>>
>>>>> Brian,
>>>>>
>>>>> Were you able to try the above mentioned commit against am180x in meta-ti?
>>>>> Did
>>>>> it solve the missing abi kernel version? Thanks.
>>>>>
>>>>> --
>>>>> Denys
>>>>
>>>> Hi Denys,
>>>>
>>>> No, I got caught up in something else ... I'll try it tomorrow and report
>>>> back after I cherry pick that commit Bruce mentioned.
>>>>
>>>> Regards,
>>>>
>>>> Brian
>>>
>>> Update.  Not sure if I did this right but this is what I did.  I added
>>> master as a remote and cherry picked
>>> 02d0a003d603266114512160b209876199241e98.  Next I just went for it and
>>> tried to bitbake my image again and got the same result as before.
>>> Next I did a bitbake cleanall on virtual/kernel and tried to make my
>>> image again and still got the same result.
>>>
>>> I'm going to leave this build as is and setup a new one using 1.8
>>> master and see if I get the same thing again.  I'll leave this broken
>>> build alone for a while in case someone wants me to try something with
>>> it to fix it.
>>>
>>> Regards,
>>>
>>> Brian
>>
>> Yet another update ... I did a fresh checkout of master and tried to
>> build and had the same kernelabiversion error:
>>
>> WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
>> now#######################
>>                                                           | ETA:
>> 00:00:28
>> WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for now
>> WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
>> now########################################
>>
>>  | ETA:  00:00:26
>> Parsing recipes: 100%
>> |##############################################################################################################################################################################|
>> Time: 00:01:02
>> Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
>> targets, 182 skipped, 0 masked, 0 errors.
>> NOTE: Resolving any missing task queue dependencies
>> NOTE: multiple providers are available for u-boot (u-boot,
>> u-boot-glsdk, u-boot-ti-staging)
>> NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
>> NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
>> NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
>>
>> Build Configuration:
>> BB_VERSION        = "1.27.0"
>> BUILD_SYS         = "x86_64-linux"
>> NATIVELSBSTRING   = "Debian-7.8"
>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>> MACHINE           = "am180x-evm"
>> DISTRO            = "poky"
>> DISTRO_VERSION    = "1.8+snapshot-20150515"
>> TUNE_FEATURES     = "arm armv5 thumb dsp"
>> TARGET_FPU        = "soft"
>> meta
>> meta-yocto
>> meta-yocto-bsp    = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
>> meta-ti           = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
>> meta-oe
>> meta-python
>> meta-networking
>> meta-webserver    = "master:53d55216c8c721d3b66ec8f968737bf081def870"
>>
>> NOTE: Preparing RunQueue
>> NOTE: Executing SetScene Tasks
>> NOTE: Executing RunQueue Tasks
>> WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
>> apache2-dev requires /usr/bin/perl, but no providers found in its
>> RDEPENDS [file-rdeps]
>> ERROR: No kernel-abiversion file found
>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>> cannot run depmod, aborting
>> ERROR: Function failed: do_rootfs
>> ERROR: Logfile of failure stored in:
>> /home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
>> ERROR: Task 7 (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>> do_rootfs) failed with exit code '1'
>> NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to be
>> rerun and 1 failed.
>> Waiting for 0 running tasks to finish:
>>
>> Summary: 1 task failed:
>>   /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>> do_rootfs
>> Summary: There were 4 WARNING messages shown.
>> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
>
> More info for those that care ...
>
> The end of the error log file has:
> DEBUG: Executing python function write_image_manifest
> DEBUG: Python function write_image_manifest finished
> NOTE: Executing: ldconfig
> -r/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/rootfs-c
> new -v
> ERROR: No kernel-abiversion file found
> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
> cannot run depmod, aborting
> DEBUG: Python function do_rootfs finished
> ERROR: Function failed: do_rootfs
>
> I have a linux-dummy director in pkgdata but no kernel-depmod directory exists.
>

Interesting. Looks like we have some sort of bad dependency. I'm poking around
to see if I can reproduce this locally.

Bruce

> Regards,
>
> Brian
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Re: [yocto] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Bruce Ashfield]

On Fri, May 15, 2015 at 4:21 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
> On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>> On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>>>
>>>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>>>>>
>>>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>>>> > On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>>>> > >On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>>>> > ><bruce.ashfield@windriver.com> wrote:
>>>>> > >>On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>>> > >>>
>>>>> > >>>On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>>>> > >>><bruce.ashfield@windriver.com> wrote:
>>>>> > >>>>
>>>>> > >>>>It is plausible. But in theory, linux-dummy should still provide
>>>>> > >>>>what you need (but since it doesn't build anything, there is
>>>>> > >>>>no abi .. and no modules can be built against it) .. so the
>>>>> > >>>>error isn't graceful.
>>>>> > >>>>
>>>>> > >>>>Bruce
>>>>> > >>>
>>>>> > >>>
>>>>> > >>>I can confirm this same problem is happening to me.  I just updated
>>>>> > >>>one of my builds from 1.7 to 1.8 and am also getting my rootfs to
>>>>> > >>> fail
>>>>> > >>>due to no abi kernel version:
>>>>> > >>
>>>>> > >>
>>>>> > >>We still have a race condition in the 1.8 branch for the population
>>>>> > >>of the build-artifacts directory.
>>>>> > >>
>>>>> > >>If modules start building, they'll race against the population of the
>>>>> > >>abiversion, and you may see that message.
>>>>> > >>
>>>>> > >>There's a proposed patch for master, but I don't think it is in
>>>>> > >>fido yet.
>>>>> > >>
>>>>> > >>Bruce
>>>>> > >
>>>>> > >Hi Bruce,
>>>>> > >
>>>>> > >I did some searches and looks like there are a number of 'race'
>>>>> > >condition fixes but it wasn't obvious which one I may need.  Is it
>>>>> > >this one:
>>>>> >
>>>>> > > >http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>>>> > >
>>>>> >
>>>>> > That's the one that should make sure that the shared workdir
>>>>> > (Which has the abiversion) is in place before building any modules.
>>>>> >
>>>>> > I can't say that it is exactly your issue, but it is the change
>>>>> > I was thinking of.
>>>>>
>>>>> Brian,
>>>>>
>>>>> Were you able to try the above mentioned commit against am180x in meta-ti?
>>>>> Did
>>>>> it solve the missing abi kernel version? Thanks.
>>>>>
>>>>> --
>>>>> Denys
>>>>
>>>> Hi Denys,
>>>>
>>>> No, I got caught up in something else ... I'll try it tomorrow and report
>>>> back after I cherry pick that commit Bruce mentioned.
>>>>
>>>> Regards,
>>>>
>>>> Brian
>>>
>>> Update.  Not sure if I did this right but this is what I did.  I added
>>> master as a remote and cherry picked
>>> 02d0a003d603266114512160b209876199241e98.  Next I just went for it and
>>> tried to bitbake my image again and got the same result as before.
>>> Next I did a bitbake cleanall on virtual/kernel and tried to make my
>>> image again and still got the same result.
>>>
>>> I'm going to leave this build as is and setup a new one using 1.8
>>> master and see if I get the same thing again.  I'll leave this broken
>>> build alone for a while in case someone wants me to try something with
>>> it to fix it.
>>>
>>> Regards,
>>>
>>> Brian
>>
>> Yet another update ... I did a fresh checkout of master and tried to
>> build and had the same kernelabiversion error:
>>
>> WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
>> now#######################
>>                                                           | ETA:
>> 00:00:28
>> WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for now
>> WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
>> now########################################
>>
>>  | ETA:  00:00:26
>> Parsing recipes: 100%
>> |##############################################################################################################################################################################|
>> Time: 00:01:02
>> Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
>> targets, 182 skipped, 0 masked, 0 errors.
>> NOTE: Resolving any missing task queue dependencies
>> NOTE: multiple providers are available for u-boot (u-boot,
>> u-boot-glsdk, u-boot-ti-staging)
>> NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
>> NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
>> NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
>>
>> Build Configuration:
>> BB_VERSION        = "1.27.0"
>> BUILD_SYS         = "x86_64-linux"
>> NATIVELSBSTRING   = "Debian-7.8"
>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>> MACHINE           = "am180x-evm"
>> DISTRO            = "poky"
>> DISTRO_VERSION    = "1.8+snapshot-20150515"
>> TUNE_FEATURES     = "arm armv5 thumb dsp"
>> TARGET_FPU        = "soft"
>> meta
>> meta-yocto
>> meta-yocto-bsp    = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
>> meta-ti           = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
>> meta-oe
>> meta-python
>> meta-networking
>> meta-webserver    = "master:53d55216c8c721d3b66ec8f968737bf081def870"
>>
>> NOTE: Preparing RunQueue
>> NOTE: Executing SetScene Tasks
>> NOTE: Executing RunQueue Tasks
>> WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
>> apache2-dev requires /usr/bin/perl, but no providers found in its
>> RDEPENDS [file-rdeps]
>> ERROR: No kernel-abiversion file found
>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>> cannot run depmod, aborting
>> ERROR: Function failed: do_rootfs
>> ERROR: Logfile of failure stored in:
>> /home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
>> ERROR: Task 7 (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>> do_rootfs) failed with exit code '1'
>> NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to be
>> rerun and 1 failed.
>> Waiting for 0 running tasks to finish:
>>
>> Summary: 1 task failed:
>>   /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>> do_rootfs
>> Summary: There were 4 WARNING messages shown.
>> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
>
> More info for those that care ...
>
> The end of the error log file has:
> DEBUG: Executing python function write_image_manifest
> DEBUG: Python function write_image_manifest finished
> NOTE: Executing: ldconfig
> -r/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/rootfs-c
> new -v
> ERROR: No kernel-abiversion file found
> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
> cannot run depmod, aborting
> DEBUG: Python function do_rootfs finished
> ERROR: Function failed: do_rootfs
>
> I have a linux-dummy director in pkgdata but no kernel-depmod directory exists.
>

Interesting. Looks like we have some sort of bad dependency. I'm poking around
to see if I can reproduce this locally.

Bruce

> Regards,
>
> Brian
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Re: [meta-ti] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Bruce Ashfield]

On 2015-05-19 07:39 AM, Bruce Ashfield wrote:
> On Fri, May 15, 2015 at 4:21 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>> On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>> On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>>> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>>>>
>>>>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>>>>>>
>>>>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>>>>>> On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>>>>>>> On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>> On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>>>>>>>>
>>>>>>>>>> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> It is plausible. But in theory, linux-dummy should still provide
>>>>>>>>>>> what you need (but since it doesn't build anything, there is
>>>>>>>>>>> no abi .. and no modules can be built against it) .. so the
>>>>>>>>>>> error isn't graceful.
>>>>>>>>>>>
>>>>>>>>>>> Bruce
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I can confirm this same problem is happening to me.  I just updated
>>>>>>>>>> one of my builds from 1.7 to 1.8 and am also getting my rootfs to
>>>>>>>>>> fail
>>>>>>>>>> due to no abi kernel version:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> We still have a race condition in the 1.8 branch for the population
>>>>>>>>> of the build-artifacts directory.
>>>>>>>>>
>>>>>>>>> If modules start building, they'll race against the population of the
>>>>>>>>> abiversion, and you may see that message.
>>>>>>>>>
>>>>>>>>> There's a proposed patch for master, but I don't think it is in
>>>>>>>>> fido yet.
>>>>>>>>>
>>>>>>>>> Bruce
>>>>>>>>
>>>>>>>> Hi Bruce,
>>>>>>>>
>>>>>>>> I did some searches and looks like there are a number of 'race'
>>>>>>>> condition fixes but it wasn't obvious which one I may need.  Is it
>>>>>>>> this one:
>>>>>>>
>>>>>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>>>>>>>
>>>>>>>
>>>>>>> That's the one that should make sure that the shared workdir
>>>>>>> (Which has the abiversion) is in place before building any modules.
>>>>>>>
>>>>>>> I can't say that it is exactly your issue, but it is the change
>>>>>>> I was thinking of.
>>>>>>
>>>>>> Brian,
>>>>>>
>>>>>> Were you able to try the above mentioned commit against am180x in meta-ti?
>>>>>> Did
>>>>>> it solve the missing abi kernel version? Thanks.
>>>>>>
>>>>>> --
>>>>>> Denys
>>>>>
>>>>> Hi Denys,
>>>>>
>>>>> No, I got caught up in something else ... I'll try it tomorrow and report
>>>>> back after I cherry pick that commit Bruce mentioned.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Brian
>>>>
>>>> Update.  Not sure if I did this right but this is what I did.  I added
>>>> master as a remote and cherry picked
>>>> 02d0a003d603266114512160b209876199241e98.  Next I just went for it and
>>>> tried to bitbake my image again and got the same result as before.
>>>> Next I did a bitbake cleanall on virtual/kernel and tried to make my
>>>> image again and still got the same result.
>>>>
>>>> I'm going to leave this build as is and setup a new one using 1.8
>>>> master and see if I get the same thing again.  I'll leave this broken
>>>> build alone for a while in case someone wants me to try something with
>>>> it to fix it.
>>>>
>>>> Regards,
>>>>
>>>> Brian
>>>
>>> Yet another update ... I did a fresh checkout of master and tried to
>>> build and had the same kernelabiversion error:
>>>
>>> WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
>>> now#######################
>>>                                                            | ETA:
>>> 00:00:28
>>> WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for now
>>> WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
>>> now########################################
>>>
>>>   | ETA:  00:00:26
>>> Parsing recipes: 100%
>>> |##############################################################################################################################################################################|
>>> Time: 00:01:02
>>> Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
>>> targets, 182 skipped, 0 masked, 0 errors.
>>> NOTE: Resolving any missing task queue dependencies
>>> NOTE: multiple providers are available for u-boot (u-boot,
>>> u-boot-glsdk, u-boot-ti-staging)
>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
>>> NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
>>>
>>> Build Configuration:
>>> BB_VERSION        = "1.27.0"
>>> BUILD_SYS         = "x86_64-linux"
>>> NATIVELSBSTRING   = "Debian-7.8"
>>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>>> MACHINE           = "am180x-evm"
>>> DISTRO            = "poky"
>>> DISTRO_VERSION    = "1.8+snapshot-20150515"
>>> TUNE_FEATURES     = "arm armv5 thumb dsp"
>>> TARGET_FPU        = "soft"
>>> meta
>>> meta-yocto
>>> meta-yocto-bsp    = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
>>> meta-ti           = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
>>> meta-oe
>>> meta-python
>>> meta-networking
>>> meta-webserver    = "master:53d55216c8c721d3b66ec8f968737bf081def870"
>>>
>>> NOTE: Preparing RunQueue
>>> NOTE: Executing SetScene Tasks
>>> NOTE: Executing RunQueue Tasks
>>> WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
>>> apache2-dev requires /usr/bin/perl, but no providers found in its
>>> RDEPENDS [file-rdeps]
>>> ERROR: No kernel-abiversion file found
>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>> cannot run depmod, aborting
>>> ERROR: Function failed: do_rootfs
>>> ERROR: Logfile of failure stored in:
>>> /home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
>>> ERROR: Task 7 (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>> do_rootfs) failed with exit code '1'
>>> NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to be
>>> rerun and 1 failed.
>>> Waiting for 0 running tasks to finish:
>>>
>>> Summary: 1 task failed:
>>>    /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>> do_rootfs
>>> Summary: There were 4 WARNING messages shown.
>>> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
>>
>> More info for those that care ...
>>
>> The end of the error log file has:
>> DEBUG: Executing python function write_image_manifest
>> DEBUG: Python function write_image_manifest finished
>> NOTE: Executing: ldconfig
>> -r/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/rootfs-c
>> new -v
>> ERROR: No kernel-abiversion file found
>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>> cannot run depmod, aborting
>> DEBUG: Python function do_rootfs finished
>> ERROR: Function failed: do_rootfs
>>
>> I have a linux-dummy director in pkgdata but no kernel-depmod directory exists.
>>
>
> Interesting. Looks like we have some sort of bad dependency. I'm poking around
> to see if I can reproduce this locally.

Brian,

I'm trying to wrap my head around this. Which kernel did you say
was building in your configuration ? Was it really linux-dummy, or
is there a bootable kernel in play ?

Looking at the dependencies, I can see how the depmodwrapper requires
that a kernel be built and the abiversion file created. But in the
case of linux-dummy, there's no header files to use and generate the
abiversion, so it won't be available for depmod.

Which takes me back to one of my original questions, why is depmod
running if the kernel isn't being built as part of this image .. and
that leads me to think I'm missing some important information.

Bruce

>
> Bruce
>
>> Regards,
>>
>> Brian
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>
>

Re: [yocto] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Bruce Ashfield]

On 2015-05-19 07:39 AM, Bruce Ashfield wrote:
> On Fri, May 15, 2015 at 4:21 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>> On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>> On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>>> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>>>>
>>>>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>>>>>>
>>>>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>>>>>> On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>>>>>>> On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>> On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>>>>>>>>
>>>>>>>>>> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> It is plausible. But in theory, linux-dummy should still provide
>>>>>>>>>>> what you need (but since it doesn't build anything, there is
>>>>>>>>>>> no abi .. and no modules can be built against it) .. so the
>>>>>>>>>>> error isn't graceful.
>>>>>>>>>>>
>>>>>>>>>>> Bruce
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I can confirm this same problem is happening to me.  I just updated
>>>>>>>>>> one of my builds from 1.7 to 1.8 and am also getting my rootfs to
>>>>>>>>>> fail
>>>>>>>>>> due to no abi kernel version:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> We still have a race condition in the 1.8 branch for the population
>>>>>>>>> of the build-artifacts directory.
>>>>>>>>>
>>>>>>>>> If modules start building, they'll race against the population of the
>>>>>>>>> abiversion, and you may see that message.
>>>>>>>>>
>>>>>>>>> There's a proposed patch for master, but I don't think it is in
>>>>>>>>> fido yet.
>>>>>>>>>
>>>>>>>>> Bruce
>>>>>>>>
>>>>>>>> Hi Bruce,
>>>>>>>>
>>>>>>>> I did some searches and looks like there are a number of 'race'
>>>>>>>> condition fixes but it wasn't obvious which one I may need.  Is it
>>>>>>>> this one:
>>>>>>>
>>>>>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>>>>>>>
>>>>>>>
>>>>>>> That's the one that should make sure that the shared workdir
>>>>>>> (Which has the abiversion) is in place before building any modules.
>>>>>>>
>>>>>>> I can't say that it is exactly your issue, but it is the change
>>>>>>> I was thinking of.
>>>>>>
>>>>>> Brian,
>>>>>>
>>>>>> Were you able to try the above mentioned commit against am180x in meta-ti?
>>>>>> Did
>>>>>> it solve the missing abi kernel version? Thanks.
>>>>>>
>>>>>> --
>>>>>> Denys
>>>>>
>>>>> Hi Denys,
>>>>>
>>>>> No, I got caught up in something else ... I'll try it tomorrow and report
>>>>> back after I cherry pick that commit Bruce mentioned.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Brian
>>>>
>>>> Update.  Not sure if I did this right but this is what I did.  I added
>>>> master as a remote and cherry picked
>>>> 02d0a003d603266114512160b209876199241e98.  Next I just went for it and
>>>> tried to bitbake my image again and got the same result as before.
>>>> Next I did a bitbake cleanall on virtual/kernel and tried to make my
>>>> image again and still got the same result.
>>>>
>>>> I'm going to leave this build as is and setup a new one using 1.8
>>>> master and see if I get the same thing again.  I'll leave this broken
>>>> build alone for a while in case someone wants me to try something with
>>>> it to fix it.
>>>>
>>>> Regards,
>>>>
>>>> Brian
>>>
>>> Yet another update ... I did a fresh checkout of master and tried to
>>> build and had the same kernelabiversion error:
>>>
>>> WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
>>> now#######################
>>>                                                            | ETA:
>>> 00:00:28
>>> WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for now
>>> WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
>>> now########################################
>>>
>>>   | ETA:  00:00:26
>>> Parsing recipes: 100%
>>> |##############################################################################################################################################################################|
>>> Time: 00:01:02
>>> Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
>>> targets, 182 skipped, 0 masked, 0 errors.
>>> NOTE: Resolving any missing task queue dependencies
>>> NOTE: multiple providers are available for u-boot (u-boot,
>>> u-boot-glsdk, u-boot-ti-staging)
>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
>>> NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
>>>
>>> Build Configuration:
>>> BB_VERSION        = "1.27.0"
>>> BUILD_SYS         = "x86_64-linux"
>>> NATIVELSBSTRING   = "Debian-7.8"
>>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>>> MACHINE           = "am180x-evm"
>>> DISTRO            = "poky"
>>> DISTRO_VERSION    = "1.8+snapshot-20150515"
>>> TUNE_FEATURES     = "arm armv5 thumb dsp"
>>> TARGET_FPU        = "soft"
>>> meta
>>> meta-yocto
>>> meta-yocto-bsp    = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
>>> meta-ti           = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
>>> meta-oe
>>> meta-python
>>> meta-networking
>>> meta-webserver    = "master:53d55216c8c721d3b66ec8f968737bf081def870"
>>>
>>> NOTE: Preparing RunQueue
>>> NOTE: Executing SetScene Tasks
>>> NOTE: Executing RunQueue Tasks
>>> WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
>>> apache2-dev requires /usr/bin/perl, but no providers found in its
>>> RDEPENDS [file-rdeps]
>>> ERROR: No kernel-abiversion file found
>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>> cannot run depmod, aborting
>>> ERROR: Function failed: do_rootfs
>>> ERROR: Logfile of failure stored in:
>>> /home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
>>> ERROR: Task 7 (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>> do_rootfs) failed with exit code '1'
>>> NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to be
>>> rerun and 1 failed.
>>> Waiting for 0 running tasks to finish:
>>>
>>> Summary: 1 task failed:
>>>    /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>> do_rootfs
>>> Summary: There were 4 WARNING messages shown.
>>> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
>>
>> More info for those that care ...
>>
>> The end of the error log file has:
>> DEBUG: Executing python function write_image_manifest
>> DEBUG: Python function write_image_manifest finished
>> NOTE: Executing: ldconfig
>> -r/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/rootfs-c
>> new -v
>> ERROR: No kernel-abiversion file found
>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>> cannot run depmod, aborting
>> DEBUG: Python function do_rootfs finished
>> ERROR: Function failed: do_rootfs
>>
>> I have a linux-dummy director in pkgdata but no kernel-depmod directory exists.
>>
>
> Interesting. Looks like we have some sort of bad dependency. I'm poking around
> to see if I can reproduce this locally.

Brian,

I'm trying to wrap my head around this. Which kernel did you say
was building in your configuration ? Was it really linux-dummy, or
is there a bootable kernel in play ?

Looking at the dependencies, I can see how the depmodwrapper requires
that a kernel be built and the abiversion file created. But in the
case of linux-dummy, there's no header files to use and generate the
abiversion, so it won't be available for depmod.

Which takes me back to one of my original questions, why is depmod
running if the kernel isn't being built as part of this image .. and
that leads me to think I'm missing some important information.

Bruce

>
> Bruce
>
>> Regards,
>>
>> Brian
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>
>

Re: [meta-ti] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Tue, May 19, 2015 at 12:31 PM, Bruce Ashfield
<bruce.ashfield@windriver.com> wrote:
> On 2015-05-19 07:39 AM, Bruce Ashfield wrote:
>>
>> On Fri, May 15, 2015 at 4:21 PM, Brian Hutchinson <b.hutchman@gmail.com>
>> wrote:
>>>
>>> On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson <b.hutchman@gmail.com>
>>> wrote:
>>>>
>>>> On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson <b.hutchman@gmail.com>
>>>> wrote:
>>>>>
>>>>> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson
>>>>> <b.hutchman@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>>>>>>>
>>>>>>>
>>>>>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>>>>>>>
>>>>>>>> On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>>>>>>>>
>>>>>>>>> On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>
>>>>>>>>>> On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> It is plausible. But in theory, linux-dummy should still provide
>>>>>>>>>>>> what you need (but since it doesn't build anything, there is
>>>>>>>>>>>> no abi .. and no modules can be built against it) .. so the
>>>>>>>>>>>> error isn't graceful.
>>>>>>>>>>>>
>>>>>>>>>>>> Bruce
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> I can confirm this same problem is happening to me.  I just
>>>>>>>>>>> updated
>>>>>>>>>>> one of my builds from 1.7 to 1.8 and am also getting my rootfs to
>>>>>>>>>>> fail
>>>>>>>>>>> due to no abi kernel version:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> We still have a race condition in the 1.8 branch for the
>>>>>>>>>> population
>>>>>>>>>> of the build-artifacts directory.
>>>>>>>>>>
>>>>>>>>>> If modules start building, they'll race against the population of
>>>>>>>>>> the
>>>>>>>>>> abiversion, and you may see that message.
>>>>>>>>>>
>>>>>>>>>> There's a proposed patch for master, but I don't think it is in
>>>>>>>>>> fido yet.
>>>>>>>>>>
>>>>>>>>>> Bruce
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi Bruce,
>>>>>>>>>
>>>>>>>>> I did some searches and looks like there are a number of 'race'
>>>>>>>>> condition fixes but it wasn't obvious which one I may need.  Is it
>>>>>>>>> this one:
>>>>>>>>
>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> That's the one that should make sure that the shared workdir
>>>>>>>> (Which has the abiversion) is in place before building any modules.
>>>>>>>>
>>>>>>>> I can't say that it is exactly your issue, but it is the change
>>>>>>>> I was thinking of.
>>>>>>>
>>>>>>>
>>>>>>> Brian,
>>>>>>>
>>>>>>> Were you able to try the above mentioned commit against am180x in
>>>>>>> meta-ti?
>>>>>>> Did
>>>>>>> it solve the missing abi kernel version? Thanks.
>>>>>>>
>>>>>>> --
>>>>>>> Denys
>>>>>>
>>>>>>
>>>>>> Hi Denys,
>>>>>>
>>>>>> No, I got caught up in something else ... I'll try it tomorrow and
>>>>>> report
>>>>>> back after I cherry pick that commit Bruce mentioned.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Brian
>>>>>
>>>>>
>>>>> Update.  Not sure if I did this right but this is what I did.  I added
>>>>> master as a remote and cherry picked
>>>>> 02d0a003d603266114512160b209876199241e98.  Next I just went for it and
>>>>> tried to bitbake my image again and got the same result as before.
>>>>> Next I did a bitbake cleanall on virtual/kernel and tried to make my
>>>>> image again and still got the same result.
>>>>>
>>>>> I'm going to leave this build as is and setup a new one using 1.8
>>>>> master and see if I get the same thing again.  I'll leave this broken
>>>>> build alone for a while in case someone wants me to try something with
>>>>> it to fix it.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Brian
>>>>
>>>>
>>>> Yet another update ... I did a fresh checkout of master and tried to
>>>> build and had the same kernelabiversion error:
>>>>
>>>> WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
>>>> now#######################
>>>>                                                            | ETA:
>>>> 00:00:28
>>>> WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for now
>>>> WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
>>>> now########################################
>>>>
>>>>   | ETA:  00:00:26
>>>> Parsing recipes: 100%
>>>>
>>>> |##############################################################################################################################################################################|
>>>> Time: 00:01:02
>>>> Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
>>>> targets, 182 skipped, 0 masked, 0 errors.
>>>> NOTE: Resolving any missing task queue dependencies
>>>> NOTE: multiple providers are available for u-boot (u-boot,
>>>> u-boot-glsdk, u-boot-ti-staging)
>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
>>>> NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
>>>>
>>>> Build Configuration:
>>>> BB_VERSION        = "1.27.0"
>>>> BUILD_SYS         = "x86_64-linux"
>>>> NATIVELSBSTRING   = "Debian-7.8"
>>>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>>>> MACHINE           = "am180x-evm"
>>>> DISTRO            = "poky"
>>>> DISTRO_VERSION    = "1.8+snapshot-20150515"
>>>> TUNE_FEATURES     = "arm armv5 thumb dsp"
>>>> TARGET_FPU        = "soft"
>>>> meta
>>>> meta-yocto
>>>> meta-yocto-bsp    = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
>>>> meta-ti           = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
>>>> meta-oe
>>>> meta-python
>>>> meta-networking
>>>> meta-webserver    = "master:53d55216c8c721d3b66ec8f968737bf081def870"
>>>>
>>>> NOTE: Preparing RunQueue
>>>> NOTE: Executing SetScene Tasks
>>>> NOTE: Executing RunQueue Tasks
>>>> WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
>>>> apache2-dev requires /usr/bin/perl, but no providers found in its
>>>> RDEPENDS [file-rdeps]
>>>> ERROR: No kernel-abiversion file found
>>>>
>>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>>> cannot run depmod, aborting
>>>> ERROR: Function failed: do_rootfs
>>>> ERROR: Logfile of failure stored in:
>>>>
>>>> /home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
>>>> ERROR: Task 7
>>>> (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>> do_rootfs) failed with exit code '1'
>>>> NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to be
>>>> rerun and 1 failed.
>>>> Waiting for 0 running tasks to finish:
>>>>
>>>> Summary: 1 task failed:
>>>>
>>>> /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>> do_rootfs
>>>> Summary: There were 4 WARNING messages shown.
>>>> Summary: There were 2 ERROR messages shown, returning a non-zero exit
>>>> code.
>>>
>>>
>>> More info for those that care ...
>>>
>>> The end of the error log file has:
>>> DEBUG: Executing python function write_image_manifest
>>> DEBUG: Python function write_image_manifest finished
>>> NOTE: Executing: ldconfig
>>>
>>> -r/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/rootfs-c
>>> new -v
>>> ERROR: No kernel-abiversion file found
>>>
>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>> cannot run depmod, aborting
>>> DEBUG: Python function do_rootfs finished
>>> ERROR: Function failed: do_rootfs
>>>
>>> I have a linux-dummy director in pkgdata but no kernel-depmod directory
>>> exists.
>>>
>>
>> Interesting. Looks like we have some sort of bad dependency. I'm poking
>> around
>> to see if I can reproduce this locally.
>
>
> Brian,
>
> I'm trying to wrap my head around this. Which kernel did you say
> was building in your configuration ? Was it really linux-dummy, or
> is there a bootable kernel in play ?
>
> Looking at the dependencies, I can see how the depmodwrapper requires
> that a kernel be built and the abiversion file created. But in the
> case of linux-dummy, there's no header files to use and generate the
> abiversion, so it won't be available for depmod.
>
> Which takes me back to one of my original questions, why is depmod
> running if the kernel isn't being built as part of this image .. and
> that leads me to think I'm missing some important information.
>
> Bruce

Hi Bruce,

Thanks for looking into it.

I have the meta-ti layer included and in the past, it did build a real
kernel version.  I don't know when (because I don't use the kernel
built by the system, I use one from outside bitbake) but this release
(1.8) and last (1.7) has built linux-dummy instead of a real version
and I didn't tell it to.

Maybe I'm doing something wrong on my end but I built this release the
same way I've built all of them (and I've been doing it from the start
of yocto project).

The only other layers I use are meta-openembedded and meta-ti.

Regards,

Brian

Re: [yocto] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Tue, May 19, 2015 at 12:31 PM, Bruce Ashfield
<bruce.ashfield@windriver.com> wrote:
> On 2015-05-19 07:39 AM, Bruce Ashfield wrote:
>>
>> On Fri, May 15, 2015 at 4:21 PM, Brian Hutchinson <b.hutchman@gmail.com>
>> wrote:
>>>
>>> On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson <b.hutchman@gmail.com>
>>> wrote:
>>>>
>>>> On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson <b.hutchman@gmail.com>
>>>> wrote:
>>>>>
>>>>> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson
>>>>> <b.hutchman@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>>>>>>>
>>>>>>>
>>>>>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>>>>>>>
>>>>>>>> On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>>>>>>>>
>>>>>>>>> On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>
>>>>>>>>>> On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> It is plausible. But in theory, linux-dummy should still provide
>>>>>>>>>>>> what you need (but since it doesn't build anything, there is
>>>>>>>>>>>> no abi .. and no modules can be built against it) .. so the
>>>>>>>>>>>> error isn't graceful.
>>>>>>>>>>>>
>>>>>>>>>>>> Bruce
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> I can confirm this same problem is happening to me.  I just
>>>>>>>>>>> updated
>>>>>>>>>>> one of my builds from 1.7 to 1.8 and am also getting my rootfs to
>>>>>>>>>>> fail
>>>>>>>>>>> due to no abi kernel version:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> We still have a race condition in the 1.8 branch for the
>>>>>>>>>> population
>>>>>>>>>> of the build-artifacts directory.
>>>>>>>>>>
>>>>>>>>>> If modules start building, they'll race against the population of
>>>>>>>>>> the
>>>>>>>>>> abiversion, and you may see that message.
>>>>>>>>>>
>>>>>>>>>> There's a proposed patch for master, but I don't think it is in
>>>>>>>>>> fido yet.
>>>>>>>>>>
>>>>>>>>>> Bruce
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi Bruce,
>>>>>>>>>
>>>>>>>>> I did some searches and looks like there are a number of 'race'
>>>>>>>>> condition fixes but it wasn't obvious which one I may need.  Is it
>>>>>>>>> this one:
>>>>>>>>
>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> That's the one that should make sure that the shared workdir
>>>>>>>> (Which has the abiversion) is in place before building any modules.
>>>>>>>>
>>>>>>>> I can't say that it is exactly your issue, but it is the change
>>>>>>>> I was thinking of.
>>>>>>>
>>>>>>>
>>>>>>> Brian,
>>>>>>>
>>>>>>> Were you able to try the above mentioned commit against am180x in
>>>>>>> meta-ti?
>>>>>>> Did
>>>>>>> it solve the missing abi kernel version? Thanks.
>>>>>>>
>>>>>>> --
>>>>>>> Denys
>>>>>>
>>>>>>
>>>>>> Hi Denys,
>>>>>>
>>>>>> No, I got caught up in something else ... I'll try it tomorrow and
>>>>>> report
>>>>>> back after I cherry pick that commit Bruce mentioned.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Brian
>>>>>
>>>>>
>>>>> Update.  Not sure if I did this right but this is what I did.  I added
>>>>> master as a remote and cherry picked
>>>>> 02d0a003d603266114512160b209876199241e98.  Next I just went for it and
>>>>> tried to bitbake my image again and got the same result as before.
>>>>> Next I did a bitbake cleanall on virtual/kernel and tried to make my
>>>>> image again and still got the same result.
>>>>>
>>>>> I'm going to leave this build as is and setup a new one using 1.8
>>>>> master and see if I get the same thing again.  I'll leave this broken
>>>>> build alone for a while in case someone wants me to try something with
>>>>> it to fix it.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Brian
>>>>
>>>>
>>>> Yet another update ... I did a fresh checkout of master and tried to
>>>> build and had the same kernelabiversion error:
>>>>
>>>> WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
>>>> now#######################
>>>>                                                            | ETA:
>>>> 00:00:28
>>>> WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for now
>>>> WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
>>>> now########################################
>>>>
>>>>   | ETA:  00:00:26
>>>> Parsing recipes: 100%
>>>>
>>>> |##############################################################################################################################################################################|
>>>> Time: 00:01:02
>>>> Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
>>>> targets, 182 skipped, 0 masked, 0 errors.
>>>> NOTE: Resolving any missing task queue dependencies
>>>> NOTE: multiple providers are available for u-boot (u-boot,
>>>> u-boot-glsdk, u-boot-ti-staging)
>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
>>>> NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
>>>>
>>>> Build Configuration:
>>>> BB_VERSION        = "1.27.0"
>>>> BUILD_SYS         = "x86_64-linux"
>>>> NATIVELSBSTRING   = "Debian-7.8"
>>>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>>>> MACHINE           = "am180x-evm"
>>>> DISTRO            = "poky"
>>>> DISTRO_VERSION    = "1.8+snapshot-20150515"
>>>> TUNE_FEATURES     = "arm armv5 thumb dsp"
>>>> TARGET_FPU        = "soft"
>>>> meta
>>>> meta-yocto
>>>> meta-yocto-bsp    = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
>>>> meta-ti           = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
>>>> meta-oe
>>>> meta-python
>>>> meta-networking
>>>> meta-webserver    = "master:53d55216c8c721d3b66ec8f968737bf081def870"
>>>>
>>>> NOTE: Preparing RunQueue
>>>> NOTE: Executing SetScene Tasks
>>>> NOTE: Executing RunQueue Tasks
>>>> WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
>>>> apache2-dev requires /usr/bin/perl, but no providers found in its
>>>> RDEPENDS [file-rdeps]
>>>> ERROR: No kernel-abiversion file found
>>>>
>>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>>> cannot run depmod, aborting
>>>> ERROR: Function failed: do_rootfs
>>>> ERROR: Logfile of failure stored in:
>>>>
>>>> /home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
>>>> ERROR: Task 7
>>>> (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>> do_rootfs) failed with exit code '1'
>>>> NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to be
>>>> rerun and 1 failed.
>>>> Waiting for 0 running tasks to finish:
>>>>
>>>> Summary: 1 task failed:
>>>>
>>>> /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>> do_rootfs
>>>> Summary: There were 4 WARNING messages shown.
>>>> Summary: There were 2 ERROR messages shown, returning a non-zero exit
>>>> code.
>>>
>>>
>>> More info for those that care ...
>>>
>>> The end of the error log file has:
>>> DEBUG: Executing python function write_image_manifest
>>> DEBUG: Python function write_image_manifest finished
>>> NOTE: Executing: ldconfig
>>>
>>> -r/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/rootfs-c
>>> new -v
>>> ERROR: No kernel-abiversion file found
>>>
>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>> cannot run depmod, aborting
>>> DEBUG: Python function do_rootfs finished
>>> ERROR: Function failed: do_rootfs
>>>
>>> I have a linux-dummy director in pkgdata but no kernel-depmod directory
>>> exists.
>>>
>>
>> Interesting. Looks like we have some sort of bad dependency. I'm poking
>> around
>> to see if I can reproduce this locally.
>
>
> Brian,
>
> I'm trying to wrap my head around this. Which kernel did you say
> was building in your configuration ? Was it really linux-dummy, or
> is there a bootable kernel in play ?
>
> Looking at the dependencies, I can see how the depmodwrapper requires
> that a kernel be built and the abiversion file created. But in the
> case of linux-dummy, there's no header files to use and generate the
> abiversion, so it won't be available for depmod.
>
> Which takes me back to one of my original questions, why is depmod
> running if the kernel isn't being built as part of this image .. and
> that leads me to think I'm missing some important information.
>
> Bruce

Hi Bruce,

Thanks for looking into it.

I have the meta-ti layer included and in the past, it did build a real
kernel version.  I don't know when (because I don't use the kernel
built by the system, I use one from outside bitbake) but this release
(1.8) and last (1.7) has built linux-dummy instead of a real version
and I didn't tell it to.

Maybe I'm doing something wrong on my end but I built this release the
same way I've built all of them (and I've been doing it from the start
of yocto project).

The only other layers I use are meta-openembedded and meta-ti.

Regards,

Brian

Re: [yocto] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Patricia Holden]

I'm new to this project and environment, but do have some input on this 
problem.  I've 
been running into the same issue and trying to get my image going so 
that I can get a bootable image ready for a client by next week.  I have 
tried using linux-dummy and creating my own "linux-xxx" to try to get 
the problem resolved.  I always end in the same failure.  I looked at 
STAGING_KERNEL_BUILDDIR using "bitbake -e core-image-minimal |grep 
STAGING_KERNEL_BUILDDIR.  It is set correctly to my linux-build 
directory and I see the abi version file in my linux-build directory 
too.  In the error log, however, the path being accessed is not the 
STAGING_KERNEL_BUILDDIR. It's looking for the abi version in 
$HOME/poky/build/tmp/sysroots/ags0-qemux86/pkgdata/kernel-depmod/kernel-
abiversion.

I'm now contemplating just going with the yocto-linux and then adding a 
patch in my bsp recipe-kernels to try to get around this problem.

Any thoughts or suggestions are most appreciated!

Re: [meta-ti] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Tue, May 19, 2015 at 12:42 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
> On Tue, May 19, 2015 at 12:31 PM, Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
>> On 2015-05-19 07:39 AM, Bruce Ashfield wrote:
>>>
>>> On Fri, May 15, 2015 at 4:21 PM, Brian Hutchinson <b.hutchman@gmail.com>
>>> wrote:
>>>>
>>>> On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson <b.hutchman@gmail.com>
>>>> wrote:
>>>>>
>>>>> On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson <b.hutchman@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson
>>>>>> <b.hutchman@gmail.com> wrote:
>>>>>>>
>>>>>>>
>>>>>>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>>>>>>>>
>>>>>>>>> On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>>>>>>>>>
>>>>>>>>>> On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> It is plausible. But in theory, linux-dummy should still provide
>>>>>>>>>>>>> what you need (but since it doesn't build anything, there is
>>>>>>>>>>>>> no abi .. and no modules can be built against it) .. so the
>>>>>>>>>>>>> error isn't graceful.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Bruce
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> I can confirm this same problem is happening to me.  I just
>>>>>>>>>>>> updated
>>>>>>>>>>>> one of my builds from 1.7 to 1.8 and am also getting my rootfs to
>>>>>>>>>>>> fail
>>>>>>>>>>>> due to no abi kernel version:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> We still have a race condition in the 1.8 branch for the
>>>>>>>>>>> population
>>>>>>>>>>> of the build-artifacts directory.
>>>>>>>>>>>
>>>>>>>>>>> If modules start building, they'll race against the population of
>>>>>>>>>>> the
>>>>>>>>>>> abiversion, and you may see that message.
>>>>>>>>>>>
>>>>>>>>>>> There's a proposed patch for master, but I don't think it is in
>>>>>>>>>>> fido yet.
>>>>>>>>>>>
>>>>>>>>>>> Bruce
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi Bruce,
>>>>>>>>>>
>>>>>>>>>> I did some searches and looks like there are a number of 'race'
>>>>>>>>>> condition fixes but it wasn't obvious which one I may need.  Is it
>>>>>>>>>> this one:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> That's the one that should make sure that the shared workdir
>>>>>>>>> (Which has the abiversion) is in place before building any modules.
>>>>>>>>>
>>>>>>>>> I can't say that it is exactly your issue, but it is the change
>>>>>>>>> I was thinking of.
>>>>>>>>
>>>>>>>>
>>>>>>>> Brian,
>>>>>>>>
>>>>>>>> Were you able to try the above mentioned commit against am180x in
>>>>>>>> meta-ti?
>>>>>>>> Did
>>>>>>>> it solve the missing abi kernel version? Thanks.
>>>>>>>>
>>>>>>>> --
>>>>>>>> Denys
>>>>>>>
>>>>>>>
>>>>>>> Hi Denys,
>>>>>>>
>>>>>>> No, I got caught up in something else ... I'll try it tomorrow and
>>>>>>> report
>>>>>>> back after I cherry pick that commit Bruce mentioned.
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Brian
>>>>>>
>>>>>>
>>>>>> Update.  Not sure if I did this right but this is what I did.  I added
>>>>>> master as a remote and cherry picked
>>>>>> 02d0a003d603266114512160b209876199241e98.  Next I just went for it and
>>>>>> tried to bitbake my image again and got the same result as before.
>>>>>> Next I did a bitbake cleanall on virtual/kernel and tried to make my
>>>>>> image again and still got the same result.
>>>>>>
>>>>>> I'm going to leave this build as is and setup a new one using 1.8
>>>>>> master and see if I get the same thing again.  I'll leave this broken
>>>>>> build alone for a while in case someone wants me to try something with
>>>>>> it to fix it.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Brian
>>>>>
>>>>>
>>>>> Yet another update ... I did a fresh checkout of master and tried to
>>>>> build and had the same kernelabiversion error:
>>>>>
>>>>> WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
>>>>> now#######################
>>>>>                                                            | ETA:
>>>>> 00:00:28
>>>>> WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for now
>>>>> WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
>>>>> now########################################
>>>>>
>>>>>   | ETA:  00:00:26
>>>>> Parsing recipes: 100%
>>>>>
>>>>> |##############################################################################################################################################################################|
>>>>> Time: 00:01:02
>>>>> Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
>>>>> targets, 182 skipped, 0 masked, 0 errors.
>>>>> NOTE: Resolving any missing task queue dependencies
>>>>> NOTE: multiple providers are available for u-boot (u-boot,
>>>>> u-boot-glsdk, u-boot-ti-staging)
>>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
>>>>> NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
>>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
>>>>>
>>>>> Build Configuration:
>>>>> BB_VERSION        = "1.27.0"
>>>>> BUILD_SYS         = "x86_64-linux"
>>>>> NATIVELSBSTRING   = "Debian-7.8"
>>>>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>>>>> MACHINE           = "am180x-evm"
>>>>> DISTRO            = "poky"
>>>>> DISTRO_VERSION    = "1.8+snapshot-20150515"
>>>>> TUNE_FEATURES     = "arm armv5 thumb dsp"
>>>>> TARGET_FPU        = "soft"
>>>>> meta
>>>>> meta-yocto
>>>>> meta-yocto-bsp    = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
>>>>> meta-ti           = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
>>>>> meta-oe
>>>>> meta-python
>>>>> meta-networking
>>>>> meta-webserver    = "master:53d55216c8c721d3b66ec8f968737bf081def870"
>>>>>
>>>>> NOTE: Preparing RunQueue
>>>>> NOTE: Executing SetScene Tasks
>>>>> NOTE: Executing RunQueue Tasks
>>>>> WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
>>>>> apache2-dev requires /usr/bin/perl, but no providers found in its
>>>>> RDEPENDS [file-rdeps]
>>>>> ERROR: No kernel-abiversion file found
>>>>>
>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>>>> cannot run depmod, aborting
>>>>> ERROR: Function failed: do_rootfs
>>>>> ERROR: Logfile of failure stored in:
>>>>>
>>>>> /home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
>>>>> ERROR: Task 7
>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>>> do_rootfs) failed with exit code '1'
>>>>> NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to be
>>>>> rerun and 1 failed.
>>>>> Waiting for 0 running tasks to finish:
>>>>>
>>>>> Summary: 1 task failed:
>>>>>
>>>>> /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>>> do_rootfs
>>>>> Summary: There were 4 WARNING messages shown.
>>>>> Summary: There were 2 ERROR messages shown, returning a non-zero exit
>>>>> code.
>>>>
>>>>
>>>> More info for those that care ...
>>>>
>>>> The end of the error log file has:
>>>> DEBUG: Executing python function write_image_manifest
>>>> DEBUG: Python function write_image_manifest finished
>>>> NOTE: Executing: ldconfig
>>>>
>>>> -r/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/rootfs-c
>>>> new -v
>>>> ERROR: No kernel-abiversion file found
>>>>
>>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>>> cannot run depmod, aborting
>>>> DEBUG: Python function do_rootfs finished
>>>> ERROR: Function failed: do_rootfs
>>>>
>>>> I have a linux-dummy director in pkgdata but no kernel-depmod directory
>>>> exists.
>>>>
>>>
>>> Interesting. Looks like we have some sort of bad dependency. I'm poking
>>> around
>>> to see if I can reproduce this locally.
>>
>>
>> Brian,
>>
>> I'm trying to wrap my head around this. Which kernel did you say
>> was building in your configuration ? Was it really linux-dummy, or
>> is there a bootable kernel in play ?
>>
>> Looking at the dependencies, I can see how the depmodwrapper requires
>> that a kernel be built and the abiversion file created. But in the
>> case of linux-dummy, there's no header files to use and generate the
>> abiversion, so it won't be available for depmod.
>>
>> Which takes me back to one of my original questions, why is depmod
>> running if the kernel isn't being built as part of this image .. and
>> that leads me to think I'm missing some important information.
>>
>> Bruce
>
> Hi Bruce,
>
> Thanks for looking into it.
>
> I have the meta-ti layer included and in the past, it did build a real
> kernel version.  I don't know when (because I don't use the kernel
> built by the system, I use one from outside bitbake) but this release
> (1.8) and last (1.7) has built linux-dummy instead of a real version
> and I didn't tell it to.
>
> Maybe I'm doing something wrong on my end but I built this release the
> same way I've built all of them (and I've been doing it from the start
> of yocto project).
>
> The only other layers I use are meta-openembedded and meta-ti.
>
> Regards,
>
> Brian

After being off this for a while ... today I did a git pull on all my
master based layers, deleted /tmp and rebuilt my am1808 based image
with no problems.  Never saw a post of a formal resolution to this
problem but obviously it was fixed somehow so thanks to whomever that
was.

Kernel was built as uImage--3.14.43-r0-am180x instead of linux-dummy this time.

Regards,

Brian

Re: [yocto] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Tue, May 19, 2015 at 12:42 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
> On Tue, May 19, 2015 at 12:31 PM, Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
>> On 2015-05-19 07:39 AM, Bruce Ashfield wrote:
>>>
>>> On Fri, May 15, 2015 at 4:21 PM, Brian Hutchinson <b.hutchman@gmail.com>
>>> wrote:
>>>>
>>>> On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson <b.hutchman@gmail.com>
>>>> wrote:
>>>>>
>>>>> On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson <b.hutchman@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson
>>>>>> <b.hutchman@gmail.com> wrote:
>>>>>>>
>>>>>>>
>>>>>>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>>>>>>>>
>>>>>>>>> On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>>>>>>>>>
>>>>>>>>>> On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> It is plausible. But in theory, linux-dummy should still provide
>>>>>>>>>>>>> what you need (but since it doesn't build anything, there is
>>>>>>>>>>>>> no abi .. and no modules can be built against it) .. so the
>>>>>>>>>>>>> error isn't graceful.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Bruce
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> I can confirm this same problem is happening to me.  I just
>>>>>>>>>>>> updated
>>>>>>>>>>>> one of my builds from 1.7 to 1.8 and am also getting my rootfs to
>>>>>>>>>>>> fail
>>>>>>>>>>>> due to no abi kernel version:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> We still have a race condition in the 1.8 branch for the
>>>>>>>>>>> population
>>>>>>>>>>> of the build-artifacts directory.
>>>>>>>>>>>
>>>>>>>>>>> If modules start building, they'll race against the population of
>>>>>>>>>>> the
>>>>>>>>>>> abiversion, and you may see that message.
>>>>>>>>>>>
>>>>>>>>>>> There's a proposed patch for master, but I don't think it is in
>>>>>>>>>>> fido yet.
>>>>>>>>>>>
>>>>>>>>>>> Bruce
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi Bruce,
>>>>>>>>>>
>>>>>>>>>> I did some searches and looks like there are a number of 'race'
>>>>>>>>>> condition fixes but it wasn't obvious which one I may need.  Is it
>>>>>>>>>> this one:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> That's the one that should make sure that the shared workdir
>>>>>>>>> (Which has the abiversion) is in place before building any modules.
>>>>>>>>>
>>>>>>>>> I can't say that it is exactly your issue, but it is the change
>>>>>>>>> I was thinking of.
>>>>>>>>
>>>>>>>>
>>>>>>>> Brian,
>>>>>>>>
>>>>>>>> Were you able to try the above mentioned commit against am180x in
>>>>>>>> meta-ti?
>>>>>>>> Did
>>>>>>>> it solve the missing abi kernel version? Thanks.
>>>>>>>>
>>>>>>>> --
>>>>>>>> Denys
>>>>>>>
>>>>>>>
>>>>>>> Hi Denys,
>>>>>>>
>>>>>>> No, I got caught up in something else ... I'll try it tomorrow and
>>>>>>> report
>>>>>>> back after I cherry pick that commit Bruce mentioned.
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Brian
>>>>>>
>>>>>>
>>>>>> Update.  Not sure if I did this right but this is what I did.  I added
>>>>>> master as a remote and cherry picked
>>>>>> 02d0a003d603266114512160b209876199241e98.  Next I just went for it and
>>>>>> tried to bitbake my image again and got the same result as before.
>>>>>> Next I did a bitbake cleanall on virtual/kernel and tried to make my
>>>>>> image again and still got the same result.
>>>>>>
>>>>>> I'm going to leave this build as is and setup a new one using 1.8
>>>>>> master and see if I get the same thing again.  I'll leave this broken
>>>>>> build alone for a while in case someone wants me to try something with
>>>>>> it to fix it.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Brian
>>>>>
>>>>>
>>>>> Yet another update ... I did a fresh checkout of master and tried to
>>>>> build and had the same kernelabiversion error:
>>>>>
>>>>> WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
>>>>> now#######################
>>>>>                                                            | ETA:
>>>>> 00:00:28
>>>>> WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for now
>>>>> WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
>>>>> now########################################
>>>>>
>>>>>   | ETA:  00:00:26
>>>>> Parsing recipes: 100%
>>>>>
>>>>> |##############################################################################################################################################################################|
>>>>> Time: 00:01:02
>>>>> Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
>>>>> targets, 182 skipped, 0 masked, 0 errors.
>>>>> NOTE: Resolving any missing task queue dependencies
>>>>> NOTE: multiple providers are available for u-boot (u-boot,
>>>>> u-boot-glsdk, u-boot-ti-staging)
>>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
>>>>> NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
>>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
>>>>>
>>>>> Build Configuration:
>>>>> BB_VERSION        = "1.27.0"
>>>>> BUILD_SYS         = "x86_64-linux"
>>>>> NATIVELSBSTRING   = "Debian-7.8"
>>>>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>>>>> MACHINE           = "am180x-evm"
>>>>> DISTRO            = "poky"
>>>>> DISTRO_VERSION    = "1.8+snapshot-20150515"
>>>>> TUNE_FEATURES     = "arm armv5 thumb dsp"
>>>>> TARGET_FPU        = "soft"
>>>>> meta
>>>>> meta-yocto
>>>>> meta-yocto-bsp    = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
>>>>> meta-ti           = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
>>>>> meta-oe
>>>>> meta-python
>>>>> meta-networking
>>>>> meta-webserver    = "master:53d55216c8c721d3b66ec8f968737bf081def870"
>>>>>
>>>>> NOTE: Preparing RunQueue
>>>>> NOTE: Executing SetScene Tasks
>>>>> NOTE: Executing RunQueue Tasks
>>>>> WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
>>>>> apache2-dev requires /usr/bin/perl, but no providers found in its
>>>>> RDEPENDS [file-rdeps]
>>>>> ERROR: No kernel-abiversion file found
>>>>>
>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>>>> cannot run depmod, aborting
>>>>> ERROR: Function failed: do_rootfs
>>>>> ERROR: Logfile of failure stored in:
>>>>>
>>>>> /home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
>>>>> ERROR: Task 7
>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>>> do_rootfs) failed with exit code '1'
>>>>> NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to be
>>>>> rerun and 1 failed.
>>>>> Waiting for 0 running tasks to finish:
>>>>>
>>>>> Summary: 1 task failed:
>>>>>
>>>>> /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>>> do_rootfs
>>>>> Summary: There were 4 WARNING messages shown.
>>>>> Summary: There were 2 ERROR messages shown, returning a non-zero exit
>>>>> code.
>>>>
>>>>
>>>> More info for those that care ...
>>>>
>>>> The end of the error log file has:
>>>> DEBUG: Executing python function write_image_manifest
>>>> DEBUG: Python function write_image_manifest finished
>>>> NOTE: Executing: ldconfig
>>>>
>>>> -r/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/rootfs-c
>>>> new -v
>>>> ERROR: No kernel-abiversion file found
>>>>
>>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>>> cannot run depmod, aborting
>>>> DEBUG: Python function do_rootfs finished
>>>> ERROR: Function failed: do_rootfs
>>>>
>>>> I have a linux-dummy director in pkgdata but no kernel-depmod directory
>>>> exists.
>>>>
>>>
>>> Interesting. Looks like we have some sort of bad dependency. I'm poking
>>> around
>>> to see if I can reproduce this locally.
>>
>>
>> Brian,
>>
>> I'm trying to wrap my head around this. Which kernel did you say
>> was building in your configuration ? Was it really linux-dummy, or
>> is there a bootable kernel in play ?
>>
>> Looking at the dependencies, I can see how the depmodwrapper requires
>> that a kernel be built and the abiversion file created. But in the
>> case of linux-dummy, there's no header files to use and generate the
>> abiversion, so it won't be available for depmod.
>>
>> Which takes me back to one of my original questions, why is depmod
>> running if the kernel isn't being built as part of this image .. and
>> that leads me to think I'm missing some important information.
>>
>> Bruce
>
> Hi Bruce,
>
> Thanks for looking into it.
>
> I have the meta-ti layer included and in the past, it did build a real
> kernel version.  I don't know when (because I don't use the kernel
> built by the system, I use one from outside bitbake) but this release
> (1.8) and last (1.7) has built linux-dummy instead of a real version
> and I didn't tell it to.
>
> Maybe I'm doing something wrong on my end but I built this release the
> same way I've built all of them (and I've been doing it from the start
> of yocto project).
>
> The only other layers I use are meta-openembedded and meta-ti.
>
> Regards,
>
> Brian

After being off this for a while ... today I did a git pull on all my
master based layers, deleted /tmp and rebuilt my am1808 based image
with no problems.  Never saw a post of a formal resolution to this
problem but obviously it was fixed somehow so thanks to whomever that
was.

Kernel was built as uImage--3.14.43-r0-am180x instead of linux-dummy this time.

Regards,

Brian

Re: [meta-ti] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Bruce Ashfield]

On 2015-06-09 9:12 PM, Brian Hutchinson wrote:
> On Tue, May 19, 2015 at 12:42 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>> On Tue, May 19, 2015 at 12:31 PM, Bruce Ashfield
>> <bruce.ashfield@windriver.com> wrote:
>>> On 2015-05-19 07:39 AM, Bruce Ashfield wrote:
>>>>
>>>> On Fri, May 15, 2015 at 4:21 PM, Brian Hutchinson <b.hutchman@gmail.com>
>>>> wrote:
>>>>>
>>>>> On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson <b.hutchman@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson <b.hutchman@gmail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson
>>>>>>> <b.hutchman@gmail.com> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>>>>>>>>>
>>>>>>>>>> On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>>>>>>>>>>
>>>>>>>>>>> On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>>>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> It is plausible. But in theory, linux-dummy should still provide
>>>>>>>>>>>>>> what you need (but since it doesn't build anything, there is
>>>>>>>>>>>>>> no abi .. and no modules can be built against it) .. so the
>>>>>>>>>>>>>> error isn't graceful.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Bruce
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I can confirm this same problem is happening to me.  I just
>>>>>>>>>>>>> updated
>>>>>>>>>>>>> one of my builds from 1.7 to 1.8 and am also getting my rootfs to
>>>>>>>>>>>>> fail
>>>>>>>>>>>>> due to no abi kernel version:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> We still have a race condition in the 1.8 branch for the
>>>>>>>>>>>> population
>>>>>>>>>>>> of the build-artifacts directory.
>>>>>>>>>>>>
>>>>>>>>>>>> If modules start building, they'll race against the population of
>>>>>>>>>>>> the
>>>>>>>>>>>> abiversion, and you may see that message.
>>>>>>>>>>>>
>>>>>>>>>>>> There's a proposed patch for master, but I don't think it is in
>>>>>>>>>>>> fido yet.
>>>>>>>>>>>>
>>>>>>>>>>>> Bruce
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hi Bruce,
>>>>>>>>>>>
>>>>>>>>>>> I did some searches and looks like there are a number of 'race'
>>>>>>>>>>> condition fixes but it wasn't obvious which one I may need.  Is it
>>>>>>>>>>> this one:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> That's the one that should make sure that the shared workdir
>>>>>>>>>> (Which has the abiversion) is in place before building any modules.
>>>>>>>>>>
>>>>>>>>>> I can't say that it is exactly your issue, but it is the change
>>>>>>>>>> I was thinking of.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Brian,
>>>>>>>>>
>>>>>>>>> Were you able to try the above mentioned commit against am180x in
>>>>>>>>> meta-ti?
>>>>>>>>> Did
>>>>>>>>> it solve the missing abi kernel version? Thanks.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Denys
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi Denys,
>>>>>>>>
>>>>>>>> No, I got caught up in something else ... I'll try it tomorrow and
>>>>>>>> report
>>>>>>>> back after I cherry pick that commit Bruce mentioned.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Brian
>>>>>>>
>>>>>>>
>>>>>>> Update.  Not sure if I did this right but this is what I did.  I added
>>>>>>> master as a remote and cherry picked
>>>>>>> 02d0a003d603266114512160b209876199241e98.  Next I just went for it and
>>>>>>> tried to bitbake my image again and got the same result as before.
>>>>>>> Next I did a bitbake cleanall on virtual/kernel and tried to make my
>>>>>>> image again and still got the same result.
>>>>>>>
>>>>>>> I'm going to leave this build as is and setup a new one using 1.8
>>>>>>> master and see if I get the same thing again.  I'll leave this broken
>>>>>>> build alone for a while in case someone wants me to try something with
>>>>>>> it to fix it.
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Brian
>>>>>>
>>>>>>
>>>>>> Yet another update ... I did a fresh checkout of master and tried to
>>>>>> build and had the same kernelabiversion error:
>>>>>>
>>>>>> WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
>>>>>> now#######################
>>>>>>                                                             | ETA:
>>>>>> 00:00:28
>>>>>> WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for now
>>>>>> WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
>>>>>> now########################################
>>>>>>
>>>>>>    | ETA:  00:00:26
>>>>>> Parsing recipes: 100%
>>>>>>
>>>>>> |##############################################################################################################################################################################|
>>>>>> Time: 00:01:02
>>>>>> Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
>>>>>> targets, 182 skipped, 0 masked, 0 errors.
>>>>>> NOTE: Resolving any missing task queue dependencies
>>>>>> NOTE: multiple providers are available for u-boot (u-boot,
>>>>>> u-boot-glsdk, u-boot-ti-staging)
>>>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
>>>>>> NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
>>>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
>>>>>>
>>>>>> Build Configuration:
>>>>>> BB_VERSION        = "1.27.0"
>>>>>> BUILD_SYS         = "x86_64-linux"
>>>>>> NATIVELSBSTRING   = "Debian-7.8"
>>>>>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>>>>>> MACHINE           = "am180x-evm"
>>>>>> DISTRO            = "poky"
>>>>>> DISTRO_VERSION    = "1.8+snapshot-20150515"
>>>>>> TUNE_FEATURES     = "arm armv5 thumb dsp"
>>>>>> TARGET_FPU        = "soft"
>>>>>> meta
>>>>>> meta-yocto
>>>>>> meta-yocto-bsp    = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
>>>>>> meta-ti           = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
>>>>>> meta-oe
>>>>>> meta-python
>>>>>> meta-networking
>>>>>> meta-webserver    = "master:53d55216c8c721d3b66ec8f968737bf081def870"
>>>>>>
>>>>>> NOTE: Preparing RunQueue
>>>>>> NOTE: Executing SetScene Tasks
>>>>>> NOTE: Executing RunQueue Tasks
>>>>>> WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
>>>>>> apache2-dev requires /usr/bin/perl, but no providers found in its
>>>>>> RDEPENDS [file-rdeps]
>>>>>> ERROR: No kernel-abiversion file found
>>>>>>
>>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>>>>> cannot run depmod, aborting
>>>>>> ERROR: Function failed: do_rootfs
>>>>>> ERROR: Logfile of failure stored in:
>>>>>>
>>>>>> /home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
>>>>>> ERROR: Task 7
>>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>>>> do_rootfs) failed with exit code '1'
>>>>>> NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to be
>>>>>> rerun and 1 failed.
>>>>>> Waiting for 0 running tasks to finish:
>>>>>>
>>>>>> Summary: 1 task failed:
>>>>>>
>>>>>> /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>>>> do_rootfs
>>>>>> Summary: There were 4 WARNING messages shown.
>>>>>> Summary: There were 2 ERROR messages shown, returning a non-zero exit
>>>>>> code.
>>>>>
>>>>>
>>>>> More info for those that care ...
>>>>>
>>>>> The end of the error log file has:
>>>>> DEBUG: Executing python function write_image_manifest
>>>>> DEBUG: Python function write_image_manifest finished
>>>>> NOTE: Executing: ldconfig
>>>>>
>>>>> -r/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/rootfs-c
>>>>> new -v
>>>>> ERROR: No kernel-abiversion file found
>>>>>
>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>>>> cannot run depmod, aborting
>>>>> DEBUG: Python function do_rootfs finished
>>>>> ERROR: Function failed: do_rootfs
>>>>>
>>>>> I have a linux-dummy director in pkgdata but no kernel-depmod directory
>>>>> exists.
>>>>>
>>>>
>>>> Interesting. Looks like we have some sort of bad dependency. I'm poking
>>>> around
>>>> to see if I can reproduce this locally.
>>>
>>>
>>> Brian,
>>>
>>> I'm trying to wrap my head around this. Which kernel did you say
>>> was building in your configuration ? Was it really linux-dummy, or
>>> is there a bootable kernel in play ?
>>>
>>> Looking at the dependencies, I can see how the depmodwrapper requires
>>> that a kernel be built and the abiversion file created. But in the
>>> case of linux-dummy, there's no header files to use and generate the
>>> abiversion, so it won't be available for depmod.
>>>
>>> Which takes me back to one of my original questions, why is depmod
>>> running if the kernel isn't being built as part of this image .. and
>>> that leads me to think I'm missing some important information.
>>>
>>> Bruce
>>
>> Hi Bruce,
>>
>> Thanks for looking into it.
>>
>> I have the meta-ti layer included and in the past, it did build a real
>> kernel version.  I don't know when (because I don't use the kernel
>> built by the system, I use one from outside bitbake) but this release
>> (1.8) and last (1.7) has built linux-dummy instead of a real version
>> and I didn't tell it to.
>>
>> Maybe I'm doing something wrong on my end but I built this release the
>> same way I've built all of them (and I've been doing it from the start
>> of yocto project).
>>
>> The only other layers I use are meta-openembedded and meta-ti.
>>
>> Regards,
>>
>> Brian
>
> After being off this for a while ... today I did a git pull on all my
> master based layers, deleted /tmp and rebuilt my am1808 based image
> with no problems.  Never saw a post of a formal resolution to this
> problem but obviously it was fixed somehow so thanks to whomever that
> was.

Good news. I was keeping this email around as a reminder, since I never
was able to reproduce the problem here.

I can't say that anything was explicitly targeted as a fix for this ..
but there have been quite a few changes to the dependencies, kernel and
build plumbing .. one of them may have had the right effect.

If this does pop back up, let me know, and we can try and root cause it
again.

Bruce

>
> Kernel was built as uImage--3.14.43-r0-am180x instead of linux-dummy this time.
>
> Regards,
>
> Brian
>

Re: [yocto] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Bruce Ashfield]

On 2015-06-09 9:12 PM, Brian Hutchinson wrote:
> On Tue, May 19, 2015 at 12:42 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>> On Tue, May 19, 2015 at 12:31 PM, Bruce Ashfield
>> <bruce.ashfield@windriver.com> wrote:
>>> On 2015-05-19 07:39 AM, Bruce Ashfield wrote:
>>>>
>>>> On Fri, May 15, 2015 at 4:21 PM, Brian Hutchinson <b.hutchman@gmail.com>
>>>> wrote:
>>>>>
>>>>> On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson <b.hutchman@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson <b.hutchman@gmail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson
>>>>>>> <b.hutchman@gmail.com> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>>>>>>>>>
>>>>>>>>>> On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>>>>>>>>>>
>>>>>>>>>>> On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>>>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> It is plausible. But in theory, linux-dummy should still provide
>>>>>>>>>>>>>> what you need (but since it doesn't build anything, there is
>>>>>>>>>>>>>> no abi .. and no modules can be built against it) .. so the
>>>>>>>>>>>>>> error isn't graceful.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Bruce
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I can confirm this same problem is happening to me.  I just
>>>>>>>>>>>>> updated
>>>>>>>>>>>>> one of my builds from 1.7 to 1.8 and am also getting my rootfs to
>>>>>>>>>>>>> fail
>>>>>>>>>>>>> due to no abi kernel version:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> We still have a race condition in the 1.8 branch for the
>>>>>>>>>>>> population
>>>>>>>>>>>> of the build-artifacts directory.
>>>>>>>>>>>>
>>>>>>>>>>>> If modules start building, they'll race against the population of
>>>>>>>>>>>> the
>>>>>>>>>>>> abiversion, and you may see that message.
>>>>>>>>>>>>
>>>>>>>>>>>> There's a proposed patch for master, but I don't think it is in
>>>>>>>>>>>> fido yet.
>>>>>>>>>>>>
>>>>>>>>>>>> Bruce
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hi Bruce,
>>>>>>>>>>>
>>>>>>>>>>> I did some searches and looks like there are a number of 'race'
>>>>>>>>>>> condition fixes but it wasn't obvious which one I may need.  Is it
>>>>>>>>>>> this one:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> That's the one that should make sure that the shared workdir
>>>>>>>>>> (Which has the abiversion) is in place before building any modules.
>>>>>>>>>>
>>>>>>>>>> I can't say that it is exactly your issue, but it is the change
>>>>>>>>>> I was thinking of.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Brian,
>>>>>>>>>
>>>>>>>>> Were you able to try the above mentioned commit against am180x in
>>>>>>>>> meta-ti?
>>>>>>>>> Did
>>>>>>>>> it solve the missing abi kernel version? Thanks.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Denys
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi Denys,
>>>>>>>>
>>>>>>>> No, I got caught up in something else ... I'll try it tomorrow and
>>>>>>>> report
>>>>>>>> back after I cherry pick that commit Bruce mentioned.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Brian
>>>>>>>
>>>>>>>
>>>>>>> Update.  Not sure if I did this right but this is what I did.  I added
>>>>>>> master as a remote and cherry picked
>>>>>>> 02d0a003d603266114512160b209876199241e98.  Next I just went for it and
>>>>>>> tried to bitbake my image again and got the same result as before.
>>>>>>> Next I did a bitbake cleanall on virtual/kernel and tried to make my
>>>>>>> image again and still got the same result.
>>>>>>>
>>>>>>> I'm going to leave this build as is and setup a new one using 1.8
>>>>>>> master and see if I get the same thing again.  I'll leave this broken
>>>>>>> build alone for a while in case someone wants me to try something with
>>>>>>> it to fix it.
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Brian
>>>>>>
>>>>>>
>>>>>> Yet another update ... I did a fresh checkout of master and tried to
>>>>>> build and had the same kernelabiversion error:
>>>>>>
>>>>>> WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
>>>>>> now#######################
>>>>>>                                                             | ETA:
>>>>>> 00:00:28
>>>>>> WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for now
>>>>>> WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
>>>>>> now########################################
>>>>>>
>>>>>>    | ETA:  00:00:26
>>>>>> Parsing recipes: 100%
>>>>>>
>>>>>> |##############################################################################################################################################################################|
>>>>>> Time: 00:01:02
>>>>>> Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
>>>>>> targets, 182 skipped, 0 masked, 0 errors.
>>>>>> NOTE: Resolving any missing task queue dependencies
>>>>>> NOTE: multiple providers are available for u-boot (u-boot,
>>>>>> u-boot-glsdk, u-boot-ti-staging)
>>>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
>>>>>> NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
>>>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
>>>>>>
>>>>>> Build Configuration:
>>>>>> BB_VERSION        = "1.27.0"
>>>>>> BUILD_SYS         = "x86_64-linux"
>>>>>> NATIVELSBSTRING   = "Debian-7.8"
>>>>>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>>>>>> MACHINE           = "am180x-evm"
>>>>>> DISTRO            = "poky"
>>>>>> DISTRO_VERSION    = "1.8+snapshot-20150515"
>>>>>> TUNE_FEATURES     = "arm armv5 thumb dsp"
>>>>>> TARGET_FPU        = "soft"
>>>>>> meta
>>>>>> meta-yocto
>>>>>> meta-yocto-bsp    = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
>>>>>> meta-ti           = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
>>>>>> meta-oe
>>>>>> meta-python
>>>>>> meta-networking
>>>>>> meta-webserver    = "master:53d55216c8c721d3b66ec8f968737bf081def870"
>>>>>>
>>>>>> NOTE: Preparing RunQueue
>>>>>> NOTE: Executing SetScene Tasks
>>>>>> NOTE: Executing RunQueue Tasks
>>>>>> WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
>>>>>> apache2-dev requires /usr/bin/perl, but no providers found in its
>>>>>> RDEPENDS [file-rdeps]
>>>>>> ERROR: No kernel-abiversion file found
>>>>>>
>>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>>>>> cannot run depmod, aborting
>>>>>> ERROR: Function failed: do_rootfs
>>>>>> ERROR: Logfile of failure stored in:
>>>>>>
>>>>>> /home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
>>>>>> ERROR: Task 7
>>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>>>> do_rootfs) failed with exit code '1'
>>>>>> NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to be
>>>>>> rerun and 1 failed.
>>>>>> Waiting for 0 running tasks to finish:
>>>>>>
>>>>>> Summary: 1 task failed:
>>>>>>
>>>>>> /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>>>> do_rootfs
>>>>>> Summary: There were 4 WARNING messages shown.
>>>>>> Summary: There were 2 ERROR messages shown, returning a non-zero exit
>>>>>> code.
>>>>>
>>>>>
>>>>> More info for those that care ...
>>>>>
>>>>> The end of the error log file has:
>>>>> DEBUG: Executing python function write_image_manifest
>>>>> DEBUG: Python function write_image_manifest finished
>>>>> NOTE: Executing: ldconfig
>>>>>
>>>>> -r/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/rootfs-c
>>>>> new -v
>>>>> ERROR: No kernel-abiversion file found
>>>>>
>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>>>> cannot run depmod, aborting
>>>>> DEBUG: Python function do_rootfs finished
>>>>> ERROR: Function failed: do_rootfs
>>>>>
>>>>> I have a linux-dummy director in pkgdata but no kernel-depmod directory
>>>>> exists.
>>>>>
>>>>
>>>> Interesting. Looks like we have some sort of bad dependency. I'm poking
>>>> around
>>>> to see if I can reproduce this locally.
>>>
>>>
>>> Brian,
>>>
>>> I'm trying to wrap my head around this. Which kernel did you say
>>> was building in your configuration ? Was it really linux-dummy, or
>>> is there a bootable kernel in play ?
>>>
>>> Looking at the dependencies, I can see how the depmodwrapper requires
>>> that a kernel be built and the abiversion file created. But in the
>>> case of linux-dummy, there's no header files to use and generate the
>>> abiversion, so it won't be available for depmod.
>>>
>>> Which takes me back to one of my original questions, why is depmod
>>> running if the kernel isn't being built as part of this image .. and
>>> that leads me to think I'm missing some important information.
>>>
>>> Bruce
>>
>> Hi Bruce,
>>
>> Thanks for looking into it.
>>
>> I have the meta-ti layer included and in the past, it did build a real
>> kernel version.  I don't know when (because I don't use the kernel
>> built by the system, I use one from outside bitbake) but this release
>> (1.8) and last (1.7) has built linux-dummy instead of a real version
>> and I didn't tell it to.
>>
>> Maybe I'm doing something wrong on my end but I built this release the
>> same way I've built all of them (and I've been doing it from the start
>> of yocto project).
>>
>> The only other layers I use are meta-openembedded and meta-ti.
>>
>> Regards,
>>
>> Brian
>
> After being off this for a while ... today I did a git pull on all my
> master based layers, deleted /tmp and rebuilt my am1808 based image
> with no problems.  Never saw a post of a formal resolution to this
> problem but obviously it was fixed somehow so thanks to whomever that
> was.

Good news. I was keeping this email around as a reminder, since I never
was able to reproduce the problem here.

I can't say that anything was explicitly targeted as a fix for this ..
but there have been quite a few changes to the dependencies, kernel and
build plumbing .. one of them may have had the right effect.

If this does pop back up, let me know, and we can try and root cause it
again.

Bruce

>
> Kernel was built as uImage--3.14.43-r0-am180x instead of linux-dummy this time.
>
> Regards,
>
> Brian
>

Re: [meta-ti] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Tue, Jun 9, 2015 at 9:14 PM, Bruce Ashfield
<bruce.ashfield@windriver.com> wrote:
> On 2015-06-09 9:12 PM, Brian Hutchinson wrote:
>>
>> On Tue, May 19, 2015 at 12:42 PM, Brian Hutchinson <b.hutchman@gmail.com>
>> wrote:
>>>
>>> On Tue, May 19, 2015 at 12:31 PM, Bruce Ashfield
>>> <bruce.ashfield@windriver.com> wrote:
>>>>
>>>> On 2015-05-19 07:39 AM, Bruce Ashfield wrote:
>>>>>
>>>>>
>>>>> On Fri, May 15, 2015 at 4:21 PM, Brian Hutchinson
>>>>> <b.hutchman@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>> On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson
>>>>>> <b.hutchman@gmail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>> On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson
>>>>>>> <b.hutchman@gmail.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson
>>>>>>>> <b.hutchman@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>>>>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> It is plausible. But in theory, linux-dummy should still
>>>>>>>>>>>>>>> provide
>>>>>>>>>>>>>>> what you need (but since it doesn't build anything, there is
>>>>>>>>>>>>>>> no abi .. and no modules can be built against it) .. so the
>>>>>>>>>>>>>>> error isn't graceful.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Bruce
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I can confirm this same problem is happening to me.  I just
>>>>>>>>>>>>>> updated
>>>>>>>>>>>>>> one of my builds from 1.7 to 1.8 and am also getting my rootfs
>>>>>>>>>>>>>> to
>>>>>>>>>>>>>> fail
>>>>>>>>>>>>>> due to no abi kernel version:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> We still have a race condition in the 1.8 branch for the
>>>>>>>>>>>>> population
>>>>>>>>>>>>> of the build-artifacts directory.
>>>>>>>>>>>>>
>>>>>>>>>>>>> If modules start building, they'll race against the population
>>>>>>>>>>>>> of
>>>>>>>>>>>>> the
>>>>>>>>>>>>> abiversion, and you may see that message.
>>>>>>>>>>>>>
>>>>>>>>>>>>> There's a proposed patch for master, but I don't think it is in
>>>>>>>>>>>>> fido yet.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Bruce
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Bruce,
>>>>>>>>>>>>
>>>>>>>>>>>> I did some searches and looks like there are a number of 'race'
>>>>>>>>>>>> condition fixes but it wasn't obvious which one I may need.  Is
>>>>>>>>>>>> it
>>>>>>>>>>>> this one:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> That's the one that should make sure that the shared workdir
>>>>>>>>>>> (Which has the abiversion) is in place before building any
>>>>>>>>>>> modules.
>>>>>>>>>>>
>>>>>>>>>>> I can't say that it is exactly your issue, but it is the change
>>>>>>>>>>> I was thinking of.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Brian,
>>>>>>>>>>
>>>>>>>>>> Were you able to try the above mentioned commit against am180x in
>>>>>>>>>> meta-ti?
>>>>>>>>>> Did
>>>>>>>>>> it solve the missing abi kernel version? Thanks.
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Denys
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi Denys,
>>>>>>>>>
>>>>>>>>> No, I got caught up in something else ... I'll try it tomorrow and
>>>>>>>>> report
>>>>>>>>> back after I cherry pick that commit Bruce mentioned.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Brian
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Update.  Not sure if I did this right but this is what I did.  I
>>>>>>>> added
>>>>>>>> master as a remote and cherry picked
>>>>>>>> 02d0a003d603266114512160b209876199241e98.  Next I just went for it
>>>>>>>> and
>>>>>>>> tried to bitbake my image again and got the same result as before.
>>>>>>>> Next I did a bitbake cleanall on virtual/kernel and tried to make my
>>>>>>>> image again and still got the same result.
>>>>>>>>
>>>>>>>> I'm going to leave this build as is and setup a new one using 1.8
>>>>>>>> master and see if I get the same thing again.  I'll leave this
>>>>>>>> broken
>>>>>>>> build alone for a while in case someone wants me to try something
>>>>>>>> with
>>>>>>>> it to fix it.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Brian
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Yet another update ... I did a fresh checkout of master and tried to
>>>>>>> build and had the same kernelabiversion error:
>>>>>>>
>>>>>>> WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
>>>>>>> now#######################
>>>>>>>                                                             | ETA:
>>>>>>> 00:00:28
>>>>>>> WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for
>>>>>>> now
>>>>>>> WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
>>>>>>> now########################################
>>>>>>>
>>>>>>>    | ETA:  00:00:26
>>>>>>> Parsing recipes: 100%
>>>>>>>
>>>>>>>
>>>>>>> |##############################################################################################################################################################################|
>>>>>>> Time: 00:01:02
>>>>>>> Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
>>>>>>> targets, 182 skipped, 0 masked, 0 errors.
>>>>>>> NOTE: Resolving any missing task queue dependencies
>>>>>>> NOTE: multiple providers are available for u-boot (u-boot,
>>>>>>> u-boot-glsdk, u-boot-ti-staging)
>>>>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
>>>>>>> NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
>>>>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
>>>>>>>
>>>>>>> Build Configuration:
>>>>>>> BB_VERSION        = "1.27.0"
>>>>>>> BUILD_SYS         = "x86_64-linux"
>>>>>>> NATIVELSBSTRING   = "Debian-7.8"
>>>>>>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>>>>>>> MACHINE           = "am180x-evm"
>>>>>>> DISTRO            = "poky"
>>>>>>> DISTRO_VERSION    = "1.8+snapshot-20150515"
>>>>>>> TUNE_FEATURES     = "arm armv5 thumb dsp"
>>>>>>> TARGET_FPU        = "soft"
>>>>>>> meta
>>>>>>> meta-yocto
>>>>>>> meta-yocto-bsp    = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
>>>>>>> meta-ti           = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
>>>>>>> meta-oe
>>>>>>> meta-python
>>>>>>> meta-networking
>>>>>>> meta-webserver    = "master:53d55216c8c721d3b66ec8f968737bf081def870"
>>>>>>>
>>>>>>> NOTE: Preparing RunQueue
>>>>>>> NOTE: Executing SetScene Tasks
>>>>>>> NOTE: Executing RunQueue Tasks
>>>>>>> WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
>>>>>>> apache2-dev requires /usr/bin/perl, but no providers found in its
>>>>>>> RDEPENDS [file-rdeps]
>>>>>>> ERROR: No kernel-abiversion file found
>>>>>>>
>>>>>>>
>>>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>>>>>> cannot run depmod, aborting
>>>>>>> ERROR: Function failed: do_rootfs
>>>>>>> ERROR: Logfile of failure stored in:
>>>>>>>
>>>>>>>
>>>>>>> /home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
>>>>>>> ERROR: Task 7
>>>>>>>
>>>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>>>>> do_rootfs) failed with exit code '1'
>>>>>>> NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to
>>>>>>> be
>>>>>>> rerun and 1 failed.
>>>>>>> Waiting for 0 running tasks to finish:
>>>>>>>
>>>>>>> Summary: 1 task failed:
>>>>>>>
>>>>>>>
>>>>>>> /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>>>>> do_rootfs
>>>>>>> Summary: There were 4 WARNING messages shown.
>>>>>>> Summary: There were 2 ERROR messages shown, returning a non-zero exit
>>>>>>> code.
>>>>>>
>>>>>>
>>>>>>
>>>>>> More info for those that care ...
>>>>>>
>>>>>> The end of the error log file has:
>>>>>> DEBUG: Executing python function write_image_manifest
>>>>>> DEBUG: Python function write_image_manifest finished
>>>>>> NOTE: Executing: ldconfig
>>>>>>
>>>>>>
>>>>>> -r/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/rootfs-c
>>>>>> new -v
>>>>>> ERROR: No kernel-abiversion file found
>>>>>>
>>>>>>
>>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>>>>> cannot run depmod, aborting
>>>>>> DEBUG: Python function do_rootfs finished
>>>>>> ERROR: Function failed: do_rootfs
>>>>>>
>>>>>> I have a linux-dummy director in pkgdata but no kernel-depmod
>>>>>> directory
>>>>>> exists.
>>>>>>
>>>>>
>>>>> Interesting. Looks like we have some sort of bad dependency. I'm poking
>>>>> around
>>>>> to see if I can reproduce this locally.
>>>>
>>>>
>>>>
>>>> Brian,
>>>>
>>>> I'm trying to wrap my head around this. Which kernel did you say
>>>> was building in your configuration ? Was it really linux-dummy, or
>>>> is there a bootable kernel in play ?
>>>>
>>>> Looking at the dependencies, I can see how the depmodwrapper requires
>>>> that a kernel be built and the abiversion file created. But in the
>>>> case of linux-dummy, there's no header files to use and generate the
>>>> abiversion, so it won't be available for depmod.
>>>>
>>>> Which takes me back to one of my original questions, why is depmod
>>>> running if the kernel isn't being built as part of this image .. and
>>>> that leads me to think I'm missing some important information.
>>>>
>>>> Bruce
>>>
>>>
>>> Hi Bruce,
>>>
>>> Thanks for looking into it.
>>>
>>> I have the meta-ti layer included and in the past, it did build a real
>>> kernel version.  I don't know when (because I don't use the kernel
>>> built by the system, I use one from outside bitbake) but this release
>>> (1.8) and last (1.7) has built linux-dummy instead of a real version
>>> and I didn't tell it to.
>>>
>>> Maybe I'm doing something wrong on my end but I built this release the
>>> same way I've built all of them (and I've been doing it from the start
>>> of yocto project).
>>>
>>> The only other layers I use are meta-openembedded and meta-ti.
>>>
>>> Regards,
>>>
>>> Brian
>>
>>
>> After being off this for a while ... today I did a git pull on all my
>> master based layers, deleted /tmp and rebuilt my am1808 based image
>> with no problems.  Never saw a post of a formal resolution to this
>> problem but obviously it was fixed somehow so thanks to whomever that
>> was.
>
>
> Good news. I was keeping this email around as a reminder, since I never
> was able to reproduce the problem here.
>
> I can't say that anything was explicitly targeted as a fix for this ..
> but there have been quite a few changes to the dependencies, kernel and
> build plumbing .. one of them may have had the right effect.
>
> If this does pop back up, let me know, and we can try and root cause it
> again.
>
> Bruce

I'll try the same with my 1.8 checkout and see what happens with it.

Regards,

Brian

Re: [yocto] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Tue, Jun 9, 2015 at 9:14 PM, Bruce Ashfield
<bruce.ashfield@windriver.com> wrote:
> On 2015-06-09 9:12 PM, Brian Hutchinson wrote:
>>
>> On Tue, May 19, 2015 at 12:42 PM, Brian Hutchinson <b.hutchman@gmail.com>
>> wrote:
>>>
>>> On Tue, May 19, 2015 at 12:31 PM, Bruce Ashfield
>>> <bruce.ashfield@windriver.com> wrote:
>>>>
>>>> On 2015-05-19 07:39 AM, Bruce Ashfield wrote:
>>>>>
>>>>>
>>>>> On Fri, May 15, 2015 at 4:21 PM, Brian Hutchinson
>>>>> <b.hutchman@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>> On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson
>>>>>> <b.hutchman@gmail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>> On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson
>>>>>>> <b.hutchman@gmail.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson
>>>>>>>> <b.hutchman@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>>>>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> It is plausible. But in theory, linux-dummy should still
>>>>>>>>>>>>>>> provide
>>>>>>>>>>>>>>> what you need (but since it doesn't build anything, there is
>>>>>>>>>>>>>>> no abi .. and no modules can be built against it) .. so the
>>>>>>>>>>>>>>> error isn't graceful.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Bruce
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I can confirm this same problem is happening to me.  I just
>>>>>>>>>>>>>> updated
>>>>>>>>>>>>>> one of my builds from 1.7 to 1.8 and am also getting my rootfs
>>>>>>>>>>>>>> to
>>>>>>>>>>>>>> fail
>>>>>>>>>>>>>> due to no abi kernel version:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> We still have a race condition in the 1.8 branch for the
>>>>>>>>>>>>> population
>>>>>>>>>>>>> of the build-artifacts directory.
>>>>>>>>>>>>>
>>>>>>>>>>>>> If modules start building, they'll race against the population
>>>>>>>>>>>>> of
>>>>>>>>>>>>> the
>>>>>>>>>>>>> abiversion, and you may see that message.
>>>>>>>>>>>>>
>>>>>>>>>>>>> There's a proposed patch for master, but I don't think it is in
>>>>>>>>>>>>> fido yet.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Bruce
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Bruce,
>>>>>>>>>>>>
>>>>>>>>>>>> I did some searches and looks like there are a number of 'race'
>>>>>>>>>>>> condition fixes but it wasn't obvious which one I may need.  Is
>>>>>>>>>>>> it
>>>>>>>>>>>> this one:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> That's the one that should make sure that the shared workdir
>>>>>>>>>>> (Which has the abiversion) is in place before building any
>>>>>>>>>>> modules.
>>>>>>>>>>>
>>>>>>>>>>> I can't say that it is exactly your issue, but it is the change
>>>>>>>>>>> I was thinking of.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Brian,
>>>>>>>>>>
>>>>>>>>>> Were you able to try the above mentioned commit against am180x in
>>>>>>>>>> meta-ti?
>>>>>>>>>> Did
>>>>>>>>>> it solve the missing abi kernel version? Thanks.
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Denys
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi Denys,
>>>>>>>>>
>>>>>>>>> No, I got caught up in something else ... I'll try it tomorrow and
>>>>>>>>> report
>>>>>>>>> back after I cherry pick that commit Bruce mentioned.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Brian
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Update.  Not sure if I did this right but this is what I did.  I
>>>>>>>> added
>>>>>>>> master as a remote and cherry picked
>>>>>>>> 02d0a003d603266114512160b209876199241e98.  Next I just went for it
>>>>>>>> and
>>>>>>>> tried to bitbake my image again and got the same result as before.
>>>>>>>> Next I did a bitbake cleanall on virtual/kernel and tried to make my
>>>>>>>> image again and still got the same result.
>>>>>>>>
>>>>>>>> I'm going to leave this build as is and setup a new one using 1.8
>>>>>>>> master and see if I get the same thing again.  I'll leave this
>>>>>>>> broken
>>>>>>>> build alone for a while in case someone wants me to try something
>>>>>>>> with
>>>>>>>> it to fix it.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Brian
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Yet another update ... I did a fresh checkout of master and tried to
>>>>>>> build and had the same kernelabiversion error:
>>>>>>>
>>>>>>> WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
>>>>>>> now#######################
>>>>>>>                                                             | ETA:
>>>>>>> 00:00:28
>>>>>>> WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for
>>>>>>> now
>>>>>>> WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
>>>>>>> now########################################
>>>>>>>
>>>>>>>    | ETA:  00:00:26
>>>>>>> Parsing recipes: 100%
>>>>>>>
>>>>>>>
>>>>>>> |##############################################################################################################################################################################|
>>>>>>> Time: 00:01:02
>>>>>>> Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
>>>>>>> targets, 182 skipped, 0 masked, 0 errors.
>>>>>>> NOTE: Resolving any missing task queue dependencies
>>>>>>> NOTE: multiple providers are available for u-boot (u-boot,
>>>>>>> u-boot-glsdk, u-boot-ti-staging)
>>>>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
>>>>>>> NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
>>>>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
>>>>>>>
>>>>>>> Build Configuration:
>>>>>>> BB_VERSION        = "1.27.0"
>>>>>>> BUILD_SYS         = "x86_64-linux"
>>>>>>> NATIVELSBSTRING   = "Debian-7.8"
>>>>>>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>>>>>>> MACHINE           = "am180x-evm"
>>>>>>> DISTRO            = "poky"
>>>>>>> DISTRO_VERSION    = "1.8+snapshot-20150515"
>>>>>>> TUNE_FEATURES     = "arm armv5 thumb dsp"
>>>>>>> TARGET_FPU        = "soft"
>>>>>>> meta
>>>>>>> meta-yocto
>>>>>>> meta-yocto-bsp    = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
>>>>>>> meta-ti           = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
>>>>>>> meta-oe
>>>>>>> meta-python
>>>>>>> meta-networking
>>>>>>> meta-webserver    = "master:53d55216c8c721d3b66ec8f968737bf081def870"
>>>>>>>
>>>>>>> NOTE: Preparing RunQueue
>>>>>>> NOTE: Executing SetScene Tasks
>>>>>>> NOTE: Executing RunQueue Tasks
>>>>>>> WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
>>>>>>> apache2-dev requires /usr/bin/perl, but no providers found in its
>>>>>>> RDEPENDS [file-rdeps]
>>>>>>> ERROR: No kernel-abiversion file found
>>>>>>>
>>>>>>>
>>>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>>>>>> cannot run depmod, aborting
>>>>>>> ERROR: Function failed: do_rootfs
>>>>>>> ERROR: Logfile of failure stored in:
>>>>>>>
>>>>>>>
>>>>>>> /home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
>>>>>>> ERROR: Task 7
>>>>>>>
>>>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>>>>> do_rootfs) failed with exit code '1'
>>>>>>> NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to
>>>>>>> be
>>>>>>> rerun and 1 failed.
>>>>>>> Waiting for 0 running tasks to finish:
>>>>>>>
>>>>>>> Summary: 1 task failed:
>>>>>>>
>>>>>>>
>>>>>>> /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>>>>> do_rootfs
>>>>>>> Summary: There were 4 WARNING messages shown.
>>>>>>> Summary: There were 2 ERROR messages shown, returning a non-zero exit
>>>>>>> code.
>>>>>>
>>>>>>
>>>>>>
>>>>>> More info for those that care ...
>>>>>>
>>>>>> The end of the error log file has:
>>>>>> DEBUG: Executing python function write_image_manifest
>>>>>> DEBUG: Python function write_image_manifest finished
>>>>>> NOTE: Executing: ldconfig
>>>>>>
>>>>>>
>>>>>> -r/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/rootfs-c
>>>>>> new -v
>>>>>> ERROR: No kernel-abiversion file found
>>>>>>
>>>>>>
>>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>>>>> cannot run depmod, aborting
>>>>>> DEBUG: Python function do_rootfs finished
>>>>>> ERROR: Function failed: do_rootfs
>>>>>>
>>>>>> I have a linux-dummy director in pkgdata but no kernel-depmod
>>>>>> directory
>>>>>> exists.
>>>>>>
>>>>>
>>>>> Interesting. Looks like we have some sort of bad dependency. I'm poking
>>>>> around
>>>>> to see if I can reproduce this locally.
>>>>
>>>>
>>>>
>>>> Brian,
>>>>
>>>> I'm trying to wrap my head around this. Which kernel did you say
>>>> was building in your configuration ? Was it really linux-dummy, or
>>>> is there a bootable kernel in play ?
>>>>
>>>> Looking at the dependencies, I can see how the depmodwrapper requires
>>>> that a kernel be built and the abiversion file created. But in the
>>>> case of linux-dummy, there's no header files to use and generate the
>>>> abiversion, so it won't be available for depmod.
>>>>
>>>> Which takes me back to one of my original questions, why is depmod
>>>> running if the kernel isn't being built as part of this image .. and
>>>> that leads me to think I'm missing some important information.
>>>>
>>>> Bruce
>>>
>>>
>>> Hi Bruce,
>>>
>>> Thanks for looking into it.
>>>
>>> I have the meta-ti layer included and in the past, it did build a real
>>> kernel version.  I don't know when (because I don't use the kernel
>>> built by the system, I use one from outside bitbake) but this release
>>> (1.8) and last (1.7) has built linux-dummy instead of a real version
>>> and I didn't tell it to.
>>>
>>> Maybe I'm doing something wrong on my end but I built this release the
>>> same way I've built all of them (and I've been doing it from the start
>>> of yocto project).
>>>
>>> The only other layers I use are meta-openembedded and meta-ti.
>>>
>>> Regards,
>>>
>>> Brian
>>
>>
>> After being off this for a while ... today I did a git pull on all my
>> master based layers, deleted /tmp and rebuilt my am1808 based image
>> with no problems.  Never saw a post of a formal resolution to this
>> problem but obviously it was fixed somehow so thanks to whomever that
>> was.
>
>
> Good news. I was keeping this email around as a reminder, since I never
> was able to reproduce the problem here.
>
> I can't say that anything was explicitly targeted as a fix for this ..
> but there have been quite a few changes to the dependencies, kernel and
> build plumbing .. one of them may have had the right effect.
>
> If this does pop back up, let me know, and we can try and root cause it
> again.
>
> Bruce

I'll try the same with my 1.8 checkout and see what happens with it.

Regards,

Brian

Re: [meta-ti] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Tue, Jun 9, 2015 at 9:34 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
> On Tue, Jun 9, 2015 at 9:14 PM, Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
>> On 2015-06-09 9:12 PM, Brian Hutchinson wrote:
>>>
>>> On Tue, May 19, 2015 at 12:42 PM, Brian Hutchinson <b.hutchman@gmail.com>
>>> wrote:
>>>>
>>>> On Tue, May 19, 2015 at 12:31 PM, Bruce Ashfield
>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>
>>>>> On 2015-05-19 07:39 AM, Bruce Ashfield wrote:
>>>>>>
>>>>>>
>>>>>> On Fri, May 15, 2015 at 4:21 PM, Brian Hutchinson
>>>>>> <b.hutchman@gmail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>> On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson
>>>>>>> <b.hutchman@gmail.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson
>>>>>>>> <b.hutchman@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson
>>>>>>>>> <b.hutchman@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org>
>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>>>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>>>>>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> It is plausible. But in theory, linux-dummy should still
>>>>>>>>>>>>>>>> provide
>>>>>>>>>>>>>>>> what you need (but since it doesn't build anything, there is
>>>>>>>>>>>>>>>> no abi .. and no modules can be built against it) .. so the
>>>>>>>>>>>>>>>> error isn't graceful.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Bruce
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I can confirm this same problem is happening to me.  I just
>>>>>>>>>>>>>>> updated
>>>>>>>>>>>>>>> one of my builds from 1.7 to 1.8 and am also getting my rootfs
>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>> fail
>>>>>>>>>>>>>>> due to no abi kernel version:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We still have a race condition in the 1.8 branch for the
>>>>>>>>>>>>>> population
>>>>>>>>>>>>>> of the build-artifacts directory.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> If modules start building, they'll race against the population
>>>>>>>>>>>>>> of
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>> abiversion, and you may see that message.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> There's a proposed patch for master, but I don't think it is in
>>>>>>>>>>>>>> fido yet.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Bruce
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Bruce,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I did some searches and looks like there are a number of 'race'
>>>>>>>>>>>>> condition fixes but it wasn't obvious which one I may need.  Is
>>>>>>>>>>>>> it
>>>>>>>>>>>>> this one:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> That's the one that should make sure that the shared workdir
>>>>>>>>>>>> (Which has the abiversion) is in place before building any
>>>>>>>>>>>> modules.
>>>>>>>>>>>>
>>>>>>>>>>>> I can't say that it is exactly your issue, but it is the change
>>>>>>>>>>>> I was thinking of.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Brian,
>>>>>>>>>>>
>>>>>>>>>>> Were you able to try the above mentioned commit against am180x in
>>>>>>>>>>> meta-ti?
>>>>>>>>>>> Did
>>>>>>>>>>> it solve the missing abi kernel version? Thanks.
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Denys
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi Denys,
>>>>>>>>>>
>>>>>>>>>> No, I got caught up in something else ... I'll try it tomorrow and
>>>>>>>>>> report
>>>>>>>>>> back after I cherry pick that commit Bruce mentioned.
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> Brian
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Update.  Not sure if I did this right but this is what I did.  I
>>>>>>>>> added
>>>>>>>>> master as a remote and cherry picked
>>>>>>>>> 02d0a003d603266114512160b209876199241e98.  Next I just went for it
>>>>>>>>> and
>>>>>>>>> tried to bitbake my image again and got the same result as before.
>>>>>>>>> Next I did a bitbake cleanall on virtual/kernel and tried to make my
>>>>>>>>> image again and still got the same result.
>>>>>>>>>
>>>>>>>>> I'm going to leave this build as is and setup a new one using 1.8
>>>>>>>>> master and see if I get the same thing again.  I'll leave this
>>>>>>>>> broken
>>>>>>>>> build alone for a while in case someone wants me to try something
>>>>>>>>> with
>>>>>>>>> it to fix it.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Brian
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Yet another update ... I did a fresh checkout of master and tried to
>>>>>>>> build and had the same kernelabiversion error:
>>>>>>>>
>>>>>>>> WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
>>>>>>>> now#######################
>>>>>>>>                                                             | ETA:
>>>>>>>> 00:00:28
>>>>>>>> WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for
>>>>>>>> now
>>>>>>>> WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
>>>>>>>> now########################################
>>>>>>>>
>>>>>>>>    | ETA:  00:00:26
>>>>>>>> Parsing recipes: 100%
>>>>>>>>
>>>>>>>>
>>>>>>>> |##############################################################################################################################################################################|
>>>>>>>> Time: 00:01:02
>>>>>>>> Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
>>>>>>>> targets, 182 skipped, 0 masked, 0 errors.
>>>>>>>> NOTE: Resolving any missing task queue dependencies
>>>>>>>> NOTE: multiple providers are available for u-boot (u-boot,
>>>>>>>> u-boot-glsdk, u-boot-ti-staging)
>>>>>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
>>>>>>>> NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
>>>>>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
>>>>>>>>
>>>>>>>> Build Configuration:
>>>>>>>> BB_VERSION        = "1.27.0"
>>>>>>>> BUILD_SYS         = "x86_64-linux"
>>>>>>>> NATIVELSBSTRING   = "Debian-7.8"
>>>>>>>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>>>>>>>> MACHINE           = "am180x-evm"
>>>>>>>> DISTRO            = "poky"
>>>>>>>> DISTRO_VERSION    = "1.8+snapshot-20150515"
>>>>>>>> TUNE_FEATURES     = "arm armv5 thumb dsp"
>>>>>>>> TARGET_FPU        = "soft"
>>>>>>>> meta
>>>>>>>> meta-yocto
>>>>>>>> meta-yocto-bsp    = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
>>>>>>>> meta-ti           = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
>>>>>>>> meta-oe
>>>>>>>> meta-python
>>>>>>>> meta-networking
>>>>>>>> meta-webserver    = "master:53d55216c8c721d3b66ec8f968737bf081def870"
>>>>>>>>
>>>>>>>> NOTE: Preparing RunQueue
>>>>>>>> NOTE: Executing SetScene Tasks
>>>>>>>> NOTE: Executing RunQueue Tasks
>>>>>>>> WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
>>>>>>>> apache2-dev requires /usr/bin/perl, but no providers found in its
>>>>>>>> RDEPENDS [file-rdeps]
>>>>>>>> ERROR: No kernel-abiversion file found
>>>>>>>>
>>>>>>>>
>>>>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>>>>>>> cannot run depmod, aborting
>>>>>>>> ERROR: Function failed: do_rootfs
>>>>>>>> ERROR: Logfile of failure stored in:
>>>>>>>>
>>>>>>>>
>>>>>>>> /home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
>>>>>>>> ERROR: Task 7
>>>>>>>>
>>>>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>>>>>> do_rootfs) failed with exit code '1'
>>>>>>>> NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to
>>>>>>>> be
>>>>>>>> rerun and 1 failed.
>>>>>>>> Waiting for 0 running tasks to finish:
>>>>>>>>
>>>>>>>> Summary: 1 task failed:
>>>>>>>>
>>>>>>>>
>>>>>>>> /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>>>>>> do_rootfs
>>>>>>>> Summary: There were 4 WARNING messages shown.
>>>>>>>> Summary: There were 2 ERROR messages shown, returning a non-zero exit
>>>>>>>> code.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> More info for those that care ...
>>>>>>>
>>>>>>> The end of the error log file has:
>>>>>>> DEBUG: Executing python function write_image_manifest
>>>>>>> DEBUG: Python function write_image_manifest finished
>>>>>>> NOTE: Executing: ldconfig
>>>>>>>
>>>>>>>
>>>>>>> -r/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/rootfs-c
>>>>>>> new -v
>>>>>>> ERROR: No kernel-abiversion file found
>>>>>>>
>>>>>>>
>>>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>>>>>> cannot run depmod, aborting
>>>>>>> DEBUG: Python function do_rootfs finished
>>>>>>> ERROR: Function failed: do_rootfs
>>>>>>>
>>>>>>> I have a linux-dummy director in pkgdata but no kernel-depmod
>>>>>>> directory
>>>>>>> exists.
>>>>>>>
>>>>>>
>>>>>> Interesting. Looks like we have some sort of bad dependency. I'm poking
>>>>>> around
>>>>>> to see if I can reproduce this locally.
>>>>>
>>>>>
>>>>>
>>>>> Brian,
>>>>>
>>>>> I'm trying to wrap my head around this. Which kernel did you say
>>>>> was building in your configuration ? Was it really linux-dummy, or
>>>>> is there a bootable kernel in play ?
>>>>>
>>>>> Looking at the dependencies, I can see how the depmodwrapper requires
>>>>> that a kernel be built and the abiversion file created. But in the
>>>>> case of linux-dummy, there's no header files to use and generate the
>>>>> abiversion, so it won't be available for depmod.
>>>>>
>>>>> Which takes me back to one of my original questions, why is depmod
>>>>> running if the kernel isn't being built as part of this image .. and
>>>>> that leads me to think I'm missing some important information.
>>>>>
>>>>> Bruce
>>>>
>>>>
>>>> Hi Bruce,
>>>>
>>>> Thanks for looking into it.
>>>>
>>>> I have the meta-ti layer included and in the past, it did build a real
>>>> kernel version.  I don't know when (because I don't use the kernel
>>>> built by the system, I use one from outside bitbake) but this release
>>>> (1.8) and last (1.7) has built linux-dummy instead of a real version
>>>> and I didn't tell it to.
>>>>
>>>> Maybe I'm doing something wrong on my end but I built this release the
>>>> same way I've built all of them (and I've been doing it from the start
>>>> of yocto project).
>>>>
>>>> The only other layers I use are meta-openembedded and meta-ti.
>>>>
>>>> Regards,
>>>>
>>>> Brian
>>>
>>>
>>> After being off this for a while ... today I did a git pull on all my
>>> master based layers, deleted /tmp and rebuilt my am1808 based image
>>> with no problems.  Never saw a post of a formal resolution to this
>>> problem but obviously it was fixed somehow so thanks to whomever that
>>> was.
>>
>>
>> Good news. I was keeping this email around as a reminder, since I never
>> was able to reproduce the problem here.
>>
>> I can't say that anything was explicitly targeted as a fix for this ..
>> but there have been quite a few changes to the dependencies, kernel and
>> build plumbing .. one of them may have had the right effect.
>>
>> If this does pop back up, let me know, and we can try and root cause it
>> again.
>>
>> Bruce
>
> I'll try the same with my 1.8 checkout and see what happens with it.
>
> Regards,
>
> Brian

Rebased my 1.8 yocto and oe layers.  Meta-ti was still master as there
was no 1.8 tag when I did my initial checkout.  Smoked tmp dir and
rebuilt my image and it worked there too now.

Don't know where the problem is but 1.8 and master both work for me now.

Regards,

Brian

Re: [yocto] Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Brian Hutchinson]

On Tue, Jun 9, 2015 at 9:34 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
> On Tue, Jun 9, 2015 at 9:14 PM, Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
>> On 2015-06-09 9:12 PM, Brian Hutchinson wrote:
>>>
>>> On Tue, May 19, 2015 at 12:42 PM, Brian Hutchinson <b.hutchman@gmail.com>
>>> wrote:
>>>>
>>>> On Tue, May 19, 2015 at 12:31 PM, Bruce Ashfield
>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>
>>>>> On 2015-05-19 07:39 AM, Bruce Ashfield wrote:
>>>>>>
>>>>>>
>>>>>> On Fri, May 15, 2015 at 4:21 PM, Brian Hutchinson
>>>>>> <b.hutchman@gmail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>> On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson
>>>>>>> <b.hutchman@gmail.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson
>>>>>>>> <b.hutchman@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson
>>>>>>>>> <b.hutchman@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org>
>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>>>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>>>>>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> It is plausible. But in theory, linux-dummy should still
>>>>>>>>>>>>>>>> provide
>>>>>>>>>>>>>>>> what you need (but since it doesn't build anything, there is
>>>>>>>>>>>>>>>> no abi .. and no modules can be built against it) .. so the
>>>>>>>>>>>>>>>> error isn't graceful.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Bruce
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I can confirm this same problem is happening to me.  I just
>>>>>>>>>>>>>>> updated
>>>>>>>>>>>>>>> one of my builds from 1.7 to 1.8 and am also getting my rootfs
>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>> fail
>>>>>>>>>>>>>>> due to no abi kernel version:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We still have a race condition in the 1.8 branch for the
>>>>>>>>>>>>>> population
>>>>>>>>>>>>>> of the build-artifacts directory.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> If modules start building, they'll race against the population
>>>>>>>>>>>>>> of
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>> abiversion, and you may see that message.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> There's a proposed patch for master, but I don't think it is in
>>>>>>>>>>>>>> fido yet.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Bruce
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Bruce,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I did some searches and looks like there are a number of 'race'
>>>>>>>>>>>>> condition fixes but it wasn't obvious which one I may need.  Is
>>>>>>>>>>>>> it
>>>>>>>>>>>>> this one:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> That's the one that should make sure that the shared workdir
>>>>>>>>>>>> (Which has the abiversion) is in place before building any
>>>>>>>>>>>> modules.
>>>>>>>>>>>>
>>>>>>>>>>>> I can't say that it is exactly your issue, but it is the change
>>>>>>>>>>>> I was thinking of.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Brian,
>>>>>>>>>>>
>>>>>>>>>>> Were you able to try the above mentioned commit against am180x in
>>>>>>>>>>> meta-ti?
>>>>>>>>>>> Did
>>>>>>>>>>> it solve the missing abi kernel version? Thanks.
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Denys
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi Denys,
>>>>>>>>>>
>>>>>>>>>> No, I got caught up in something else ... I'll try it tomorrow and
>>>>>>>>>> report
>>>>>>>>>> back after I cherry pick that commit Bruce mentioned.
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> Brian
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Update.  Not sure if I did this right but this is what I did.  I
>>>>>>>>> added
>>>>>>>>> master as a remote and cherry picked
>>>>>>>>> 02d0a003d603266114512160b209876199241e98.  Next I just went for it
>>>>>>>>> and
>>>>>>>>> tried to bitbake my image again and got the same result as before.
>>>>>>>>> Next I did a bitbake cleanall on virtual/kernel and tried to make my
>>>>>>>>> image again and still got the same result.
>>>>>>>>>
>>>>>>>>> I'm going to leave this build as is and setup a new one using 1.8
>>>>>>>>> master and see if I get the same thing again.  I'll leave this
>>>>>>>>> broken
>>>>>>>>> build alone for a while in case someone wants me to try something
>>>>>>>>> with
>>>>>>>>> it to fix it.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Brian
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Yet another update ... I did a fresh checkout of master and tried to
>>>>>>>> build and had the same kernelabiversion error:
>>>>>>>>
>>>>>>>> WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
>>>>>>>> now#######################
>>>>>>>>                                                             | ETA:
>>>>>>>> 00:00:28
>>>>>>>> WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for
>>>>>>>> now
>>>>>>>> WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
>>>>>>>> now########################################
>>>>>>>>
>>>>>>>>    | ETA:  00:00:26
>>>>>>>> Parsing recipes: 100%
>>>>>>>>
>>>>>>>>
>>>>>>>> |##############################################################################################################################################################################|
>>>>>>>> Time: 00:01:02
>>>>>>>> Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
>>>>>>>> targets, 182 skipped, 0 masked, 0 errors.
>>>>>>>> NOTE: Resolving any missing task queue dependencies
>>>>>>>> NOTE: multiple providers are available for u-boot (u-boot,
>>>>>>>> u-boot-glsdk, u-boot-ti-staging)
>>>>>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
>>>>>>>> NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
>>>>>>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
>>>>>>>>
>>>>>>>> Build Configuration:
>>>>>>>> BB_VERSION        = "1.27.0"
>>>>>>>> BUILD_SYS         = "x86_64-linux"
>>>>>>>> NATIVELSBSTRING   = "Debian-7.8"
>>>>>>>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>>>>>>>> MACHINE           = "am180x-evm"
>>>>>>>> DISTRO            = "poky"
>>>>>>>> DISTRO_VERSION    = "1.8+snapshot-20150515"
>>>>>>>> TUNE_FEATURES     = "arm armv5 thumb dsp"
>>>>>>>> TARGET_FPU        = "soft"
>>>>>>>> meta
>>>>>>>> meta-yocto
>>>>>>>> meta-yocto-bsp    = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
>>>>>>>> meta-ti           = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
>>>>>>>> meta-oe
>>>>>>>> meta-python
>>>>>>>> meta-networking
>>>>>>>> meta-webserver    = "master:53d55216c8c721d3b66ec8f968737bf081def870"
>>>>>>>>
>>>>>>>> NOTE: Preparing RunQueue
>>>>>>>> NOTE: Executing SetScene Tasks
>>>>>>>> NOTE: Executing RunQueue Tasks
>>>>>>>> WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
>>>>>>>> apache2-dev requires /usr/bin/perl, but no providers found in its
>>>>>>>> RDEPENDS [file-rdeps]
>>>>>>>> ERROR: No kernel-abiversion file found
>>>>>>>>
>>>>>>>>
>>>>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>>>>>>> cannot run depmod, aborting
>>>>>>>> ERROR: Function failed: do_rootfs
>>>>>>>> ERROR: Logfile of failure stored in:
>>>>>>>>
>>>>>>>>
>>>>>>>> /home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
>>>>>>>> ERROR: Task 7
>>>>>>>>
>>>>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>>>>>> do_rootfs) failed with exit code '1'
>>>>>>>> NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to
>>>>>>>> be
>>>>>>>> rerun and 1 failed.
>>>>>>>> Waiting for 0 running tasks to finish:
>>>>>>>>
>>>>>>>> Summary: 1 task failed:
>>>>>>>>
>>>>>>>>
>>>>>>>> /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>>>>>>> do_rootfs
>>>>>>>> Summary: There were 4 WARNING messages shown.
>>>>>>>> Summary: There were 2 ERROR messages shown, returning a non-zero exit
>>>>>>>> code.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> More info for those that care ...
>>>>>>>
>>>>>>> The end of the error log file has:
>>>>>>> DEBUG: Executing python function write_image_manifest
>>>>>>> DEBUG: Python function write_image_manifest finished
>>>>>>> NOTE: Executing: ldconfig
>>>>>>>
>>>>>>>
>>>>>>> -r/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/rootfs-c
>>>>>>> new -v
>>>>>>> ERROR: No kernel-abiversion file found
>>>>>>>
>>>>>>>
>>>>>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>>>>>> cannot run depmod, aborting
>>>>>>> DEBUG: Python function do_rootfs finished
>>>>>>> ERROR: Function failed: do_rootfs
>>>>>>>
>>>>>>> I have a linux-dummy director in pkgdata but no kernel-depmod
>>>>>>> directory
>>>>>>> exists.
>>>>>>>
>>>>>>
>>>>>> Interesting. Looks like we have some sort of bad dependency. I'm poking
>>>>>> around
>>>>>> to see if I can reproduce this locally.
>>>>>
>>>>>
>>>>>
>>>>> Brian,
>>>>>
>>>>> I'm trying to wrap my head around this. Which kernel did you say
>>>>> was building in your configuration ? Was it really linux-dummy, or
>>>>> is there a bootable kernel in play ?
>>>>>
>>>>> Looking at the dependencies, I can see how the depmodwrapper requires
>>>>> that a kernel be built and the abiversion file created. But in the
>>>>> case of linux-dummy, there's no header files to use and generate the
>>>>> abiversion, so it won't be available for depmod.
>>>>>
>>>>> Which takes me back to one of my original questions, why is depmod
>>>>> running if the kernel isn't being built as part of this image .. and
>>>>> that leads me to think I'm missing some important information.
>>>>>
>>>>> Bruce
>>>>
>>>>
>>>> Hi Bruce,
>>>>
>>>> Thanks for looking into it.
>>>>
>>>> I have the meta-ti layer included and in the past, it did build a real
>>>> kernel version.  I don't know when (because I don't use the kernel
>>>> built by the system, I use one from outside bitbake) but this release
>>>> (1.8) and last (1.7) has built linux-dummy instead of a real version
>>>> and I didn't tell it to.
>>>>
>>>> Maybe I'm doing something wrong on my end but I built this release the
>>>> same way I've built all of them (and I've been doing it from the start
>>>> of yocto project).
>>>>
>>>> The only other layers I use are meta-openembedded and meta-ti.
>>>>
>>>> Regards,
>>>>
>>>> Brian
>>>
>>>
>>> After being off this for a while ... today I did a git pull on all my
>>> master based layers, deleted /tmp and rebuilt my am1808 based image
>>> with no problems.  Never saw a post of a formal resolution to this
>>> problem but obviously it was fixed somehow so thanks to whomever that
>>> was.
>>
>>
>> Good news. I was keeping this email around as a reminder, since I never
>> was able to reproduce the problem here.
>>
>> I can't say that anything was explicitly targeted as a fix for this ..
>> but there have been quite a few changes to the dependencies, kernel and
>> build plumbing .. one of them may have had the right effect.
>>
>> If this does pop back up, let me know, and we can try and root cause it
>> again.
>>
>> Bruce
>
> I'll try the same with my 1.8 checkout and see what happens with it.
>
> Regards,
>
> Brian

Rebased my 1.8 yocto and oe layers.  Meta-ti was still master as there
was no 1.8 tag when I did my initial checkout.  Smoked tmp dir and
rebuilt my image and it worked there too now.

Don't know where the problem is but 1.8 and master both work for me now.

Regards,

Brian

Re: Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Robert Calhoun]

On 4/30/15 10:06 AM, "Bruce Ashfield" <bruce.ashfield@windriver.com> wrote:

>On 2015-04-30 08:27 AM, Schaumlöffel, Jan wrote:
>>> What kernel recipe is used when your machine is set to 'astro' ?
>>> Something custom ? Or have you added machine compatibility to another
>>> known kernel recipe ?
>>
>> How would I see which kernel recipe is used?
>
>This is where my brute force techniques probably break down. I just
>do a 'bitbake virtual/kernel' and you'll see it display which
>recipe is being built.
>
>If you haven't added compatibility for your new machine to any
>recipe, I'm betting that linux-dummy is used.
>
>>
>> I did not customize anything except for aforementioned steps, simply
>>copied beaglebone.conf to astro.conf in the same directory. Also I did
>>not touch any kernel recipes (kernel is built externally), maybe that's
>>what's missing?
>
>It is plausible. But in theory, linux-dummy should still provide
>what you need (but since it doesn't build anything, there is
>no abi .. and no modules can be built against it) .. so the
>error isn't graceful.
>
>Bruce
>
>>
>> Jan
>>

I encountered the same error ("ERROR: No kernel-abiversion file found
(build/tmp/sysroots/{machinename}/pkgdata/kernel-depmod/kernel-abiversion),
 cannot run depmod, aborting") after porting my system from poky-daisy to
poky-fido. My machine config sets PREFERRED_PROVIDER_virtual/kernel =
"linux-dummy", as we currently use a monolithic out-of-tree 2.6 kernel.
It's a clean fido checkout, and I tried trashing tmp and rebuilding
everything to no effect.

Based on 
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/image.bbcl
ass I have worked around this by setting:

USE_DEPMOD = "0"

in my image configuration. This works, and allows the root file system to
be built.

Is it a bug that depmod is not skipped automatically when linux-dummy is
specified? Am I risking death and destruction by overriding it? (We don't
have any kernel modules.)

Thanks,

Rob Calhoun

Re: Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Bruce Ashfield]

On 2015-06-23 3:15 PM, Robert Calhoun wrote:
>
>
> On 4/30/15 10:06 AM, "Bruce Ashfield" <bruce.ashfield@windriver.com> wrote:
>
>> On 2015-04-30 08:27 AM, Schaumlöffel, Jan wrote:
>>>> What kernel recipe is used when your machine is set to 'astro' ?
>>>> Something custom ? Or have you added machine compatibility to another
>>>> known kernel recipe ?
>>>
>>> How would I see which kernel recipe is used?
>>
>> This is where my brute force techniques probably break down. I just
>> do a 'bitbake virtual/kernel' and you'll see it display which
>> recipe is being built.
>>
>> If you haven't added compatibility for your new machine to any
>> recipe, I'm betting that linux-dummy is used.
>>
>>>
>>> I did not customize anything except for aforementioned steps, simply
>>> copied beaglebone.conf to astro.conf in the same directory. Also I did
>>> not touch any kernel recipes (kernel is built externally), maybe that's
>>> what's missing?
>>
>> It is plausible. But in theory, linux-dummy should still provide
>> what you need (but since it doesn't build anything, there is
>> no abi .. and no modules can be built against it) .. so the
>> error isn't graceful.
>>
>> Bruce
>>
>>>
>>> Jan
>>>
>
> I encountered the same error ("ERROR: No kernel-abiversion file found
> (build/tmp/sysroots/{machinename}/pkgdata/kernel-depmod/kernel-abiversion),
>   cannot run depmod, aborting") after porting my system from poky-daisy to
> poky-fido. My machine config sets PREFERRED_PROVIDER_virtual/kernel =
> "linux-dummy", as we currently use a monolithic out-of-tree 2.6 kernel.
> It's a clean fido checkout, and I tried trashing tmp and rebuilding
> everything to no effect.
>
> Based on
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/image.bbcl
> ass I have worked around this by setting:
>
> USE_DEPMOD = "0"
>
> in my image configuration. This works, and allows the root file system to
> be built.
>
> Is it a bug that depmod is not skipped automatically when linux-dummy is
> specified? Am I risking death and destruction by overriding it? (We don't
> have any kernel modules.)

See Saul's patch from about 33 minutes ago:

[OE-core] [PATCH][master&fido] image.bbclass: Disable USE_DEPMOD for the 
dummy kernel

:)

Bruce

>
> Thanks,
>
> Rob Calhoun
>

Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Carl van Schaik]

[-- Attachment #1: Type: text/plain, Size: 381 bytes --]

I've just encountered the exact same issue upgrading. 

> Have you tried setting linux-dummy as the preferred provider for the kernel ? >That would skip the build processing doing anything more than satisfying the various kernel dependencies.

We do explicitly set preferred provider to linux-dummy, in our layer.

STAGING_KERNEL_builddir=...../armv7/kernel-build-artifacts

[-- Attachment #2: Type: text/html, Size: 415 bytes --]

Re: Migration from 1.7.1 to 1.8 - kernel-abiversion missing

[Carl van Schaik]

[-- Attachment #1: Type: text/plain, Size: 381 bytes --]

I've just encountered the exact same issue upgrading. 

> Have you tried setting linux-dummy as the preferred provider for the kernel ? >That would skip the build processing doing anything more than satisfying the various kernel dependencies.

We do explicitly set preferred provider to linux-dummy, in our layer.

STAGING_KERNEL_builddir=...../armv7/kernel-build-artifacts

[-- Attachment #2: Type: text/html, Size: 415 bytes --]