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
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
