4286 2013-04-12 20:07:07 +0000 recipes that provide kernel modules need to provide packages that begin with 'kernel-module-' 2013-08-20 18:26:08 +0000 1 1 7 Build System, Metadata & Runtime OE-Core kernel 1.4 x86 Multiple RESOLVED FIXED Medium normal 1.5 1 mark.hatle yang.shi bruce.ashfield dvhart tom.zanussi yang.shi --- --- No (bug/feature does not impact docs) oldest_to_newest 32092 0 mark.hatle 2013-04-12 20:07:07 +0000 Recipes that provide kernel modules, such as compat-wireless (from meta-oe), hello-mod (from meta-skeleton), etc are producing packages that do NOT start with 'kernel-module-'. This causes a number of subtle problems, as the system keys various checks against the package name begining with 'kernel-module-'. See package.bbclass and insane.bbclass. In addition, if multilib support is enabled and the user attempts to build a multilib image, i.e. bitbake lib32-core-image-minimal, the recipes will be incorrectly renamed if they occur in IMAGE_INSTALL. There is a check in the remapping code of meta/lib/oe/classextend.py. This specifically checks for 'kernel-'. Recipes that inherit the module.bbclass (and related) should automatically get their produced packages prefixed with 'kernel-module-'. I.e. PKG_${PN} = "kernel-module-${PN}" A sanity check should be added that the package name of modules will startwith 'kernel-module-' or an error should be generated. 35784 1 yang.shi 2013-08-20 18:26:08 +0000 Fixed by below commits: 0bc564af07c1bae8112f834a60aea3b72af7de13 0e78c2931397f5a6811119ad33c9f95975aef8b7 8b075050e4889e0a06d6d7d01b28b8645d2f2af5