| Summary: |
recipes that provide kernel modules need to provide packages that begin with 'kernel-module-' |
| Product: |
[Build System, Metadata & Runtime] OE-Core
|
Reporter: |
Mark Hatle <mark.hatle> |
| Component: |
kernel | Assignee: |
Yang Shi <yang.shi> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
Medium
|
CC: |
bruce.ashfield, dvhart, tom.zanussi, yang.shi
|
| Version: |
1.4 | |
|
| Target Milestone: |
1.5 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
|---|
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.