hello-mod: Ensure the produced package name begins with kernel-module-
PATCH 1/1 hello-mod: Ensure the produced package name begins with kernel-module-
The special key kernel-module- is necessary for the system to avoid a package rename when installing a multilib image. For example:
local.conf: IMAGE_INSTALL_append = " hello-mod"
bitbake lib32-core-image-minimal
The system will translate names and prepend 'lib32-', unless the package begins with kernel-module-.
--- meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb | 8 ++++++++ 1 file changed, 8 insertions(+)
meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb +8 -0
@@ -13,3 +13,11 @@ SRC_URI = "file://Makefile \ " S = "${WORKDIR}" + +# Kernel module packages MUST begin with 'kernel-module-', otherwise +# multilib image generation can fail. +# +# The following line is only necessary if the recipe name does not begin +# with kernel-module-. +# +PKG_${PN} = "kernel-module-${PN}"
Signature · 1 line
1.8.1.2.545.g2f19ada
Quoted 9 lines · Mark Hatle
The special key kernel-module- is necessary for the system to avoid a package rename when installing a multilib image. For example:
local.conf:
IMAGE_INSTALL_append= " hello-mod"bitbake lib32-core-image-minimal
The system will translate names and prepend 'lib32-', unless the package begins with kernel-module-.
Mark and I were talking about this, and since this is something that is required in a multlib system, and an external module has gone to the trouble of inheriting
module.bbclass, and we have the kernel-module-split.bbclass, that this is something
we should be able to programatically do and generate the package names that meet the expectations of the system.
I suggested a bugzilla and we can tackle this at the front end of the upcoming dev cycle.
I think that's reasonable, if anyone knows of a reason why this absolutely can't be done automatically .. or I'm out to lunch, I'm happy to have my redirect, NAK'd :)
Cheers,
Bruce
Quoted 26 lines
Signed-off-by Mark Hatle <[email protected]>--- meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb | 8 ++++++++ 1 file changed, 8 insertions(+)meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb +8
-1@@ -13,3 +13,11 @@ SRC_URI = "file://Makefile \ " S = "${WORKDIR}" + +# Kernel module packages MUST begin with 'kernel-module-', otherwise +# multilib image generation can fail. +# +# The following line is only necessary if the recipe name does not begin +# with kernel-module-. +# +PKG_${PN} = "kernel-module-${PN}" --1.8.1.2.545.g2f19ada
Quoted 4 lines
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"
Quoted 19 lines · Bruce Ashfield
Quoted 9 lines · Mark Hatle
The special key kernel-module- is necessary for the system to avoid a package rename when installing a multilib image. For example:
local.conf:
IMAGE_INSTALL_append= " hello-mod"bitbake lib32-core-image-minimal
The system will translate names and prepend 'lib32-', unless the package begins with kernel-module-.
Mark and I were talking about this, and since this is something that is required in a multlib system, and an external module has gone to the trouble of inheriting
module.bbclass, and we have the kernel-module-split.bbclass, that this is something
we should be able to programatically do and generate the package names that meet the expectations of the system.
Quoted 2 lines
I suggested a bugzilla and we can tackle this at the front end of the upcoming dev cycle.
YP bugzilla # 4286
Quoted 46 lines
I think that's reasonable, if anyone knows of a reason why this absolutely can't be done automatically .. or I'm out to lunch, I'm happy to have my redirect, NAK'd :)
Cheers,
Bruce
Quoted 26 lines
Signed-off-by Mark Hatle <[email protected]>--- meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb | 8 ++++++++ 1 file changed, 8 insertions(+)meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb +8
-1@@ -13,3 +13,11 @@ SRC_URI = "file://Makefile \ " S = "${WORKDIR}" + +# Kernel module packages MUST begin with 'kernel-module-', otherwise +# multilib image generation can fail. +# +# The following line is only necessary if the recipe name does not begin +# with kernel-module-. +# +PKG_${PN} = "kernel-module-${PN}" --1.8.1.2.545.g2f19ada
Quoted 4 lines
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"
Quoted 19 lines · Bruce Ashfield
Quoted 9 lines · Mark Hatle
The special key kernel-module- is necessary for the system to avoid a package rename when installing a multilib image. For example:
local.conf:
IMAGE_INSTALL_append= " hello-mod"bitbake lib32-core-image-minimal
The system will translate names and prepend 'lib32-', unless the package begins with kernel-module-.
Mark and I were talking about this, and since this is something that is required in a multlib system, and an external module has gone to the trouble of inheriting
module.bbclass, and we have the kernel-module-split.bbclass, that this is something
we should be able to programatically do and generate the package names that meet the expectations of the system.
Quoted 6 lines
I suggested a bugzilla and we can tackle this at the front end of the upcoming dev cycle.
I think that's reasonable, if anyone knows of a reason why this absolutely can't be done automatically .. or I'm out to lunch, I'm happy to have my redirect, NAK'd :)
Agreed, hello-mod should give good example and
inherit kernel-module-split
if it does not work as-is now then we should improve kernel-module-split and hello-mod.
Quoted 38 lines
Quoted 23 lines
meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb | 8 ++++++++ 1 file changed, 8 insertions(+)meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb +8
-1@@ -13,3 +13,11 @@ SRC_URI = "file://Makefile \ " S = "${WORKDIR}" + +# Kernel module packages MUST begin with 'kernel-module-', otherwise +# multilib image generation can fail. +# +# The following line is only necessary if the recipe name does not begin +# with kernel-module-. +# +PKG_${PN} = "kernel-module-${PN}" --1.8.1.2.545.g2f19ada
Quoted 4 lines
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]