As a "normal" recipe, mulitlib would try and extend it for multilibs. By inheriting module-base, we can avoid this since we now look more 'kernel' like.
Signed-off-by: Richard Purdie <[email protected]> diff --git a/meta/recipes-kernel/linux/kernel-devsrc.bb b/meta/recipes-kernel/linux/kernel-devsrc.bb index facc235..2872f17 100644 --- a/meta/recipes-kernel/linux/kernel-devsrc.bb +++ b/meta/recipes-kernel/linux/kernel-devsrc.bb @@ -10,6 +10,9 @@ LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425 inherit linux-kernel-base +# Whilst not a module, this ensures we don't get multilib extended (which would make no sense) +inherit module-base + # We need the kernel to be staged (unpacked, patched and configured) before # we can grab the source and make the kernel-devsrc package do_install[depends] += "virtual/kernel:do_populate_sysroot" -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
