summaryrefslogtreecommitdiff
path: root/meta/recipes-extended/pigz
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2015-01-20 13:01:29 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-01-23 14:31:56 +0000
commitb851504dcf5e147c9efb1c7b6a4d22c1a1a87cd7 (patch)
tree0e98dbc147d2f0b56fa1472dbadc565099d157c9 /meta/recipes-extended/pigz
parent872342fa3d08edede4a0105ac3ddb0f2ae3224b4 (diff)
downloadopenembedded-core-b851504dcf5e147c9efb1c7b6a4d22c1a1a87cd7.tar.gz
openembedded-core-b851504dcf5e147c9efb1c7b6a4d22c1a1a87cd7.tar.bz2
openembedded-core-b851504dcf5e147c9efb1c7b6a4d22c1a1a87cd7.zip
kernel/image/depmodwrapper: Fixups for depmod
With the rpm package backend enabled, running: bitbake <image> bitbake virtual/kernel -c clean bitbake <image> -c rootfs -f results in an image with incorrect kernel module dependency information. The problem is that the System.map and kernel-abiversion files are needed for depmod and after the recent kernel changes, these are no longer in sstate. Its reasonable to require the kernel to unpack/build if you're about to build a module against it. It is not reasonable to require this just to build a rootfs. Therefore stash the needed files specifically for depmod. Also fix some STAGING_KERNEL_DIR references which were incorrect, found whilst sorting through his change. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-extended/pigz')
0 files changed, 0 insertions, 0 deletions