15326 2023-12-15 13:15:09 +0000 Resolving RPROVIDER for dynamic kernel modules always match the kernel recipe 2024-08-06 14:23:27 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake unspecified x86 Multiple RESOLVED NOTABUG Medium normal Future 1 ola.x.nilsson richard.purdie poky.bs.watcher poky.watcher randy.macleod --- --- Don't know oldest_to_newest 97577 0 ola.x.nilsson 2023-12-15 13:15:09 +0000 When two (or more) recipes provide regexps in PACKAGES_DYNAMIC that match a package mentioned in RDEPENDS or PACKAGE_INSTALL, bitbake chooses one of them as the potential RPROVIDER of that package. The selection is based on things like PREFERRED_PROVIDER. This is problematic for external kernel modules. The kernel recipe provides a regex ${KERNEL_PACKAGE_NAME}-module-.* that will match ANY kernel module provided by external module recipes. And since the kernel recipe is likely to be a PREFERRED_PROVIDER, it is likely that the kernel will be chosen as RPROVIDER over the external module even if the external modules dynamic package regex matches more of the package name. It's probably hard to find a method that always picks the correct RPROVIDER, maybe all potential RPROVIDERS should be added to the build graph? 97633 1 randy.macleod 2023-12-21 15:39:08 +0000 This is a valid problem but it's not clear how to fix it. Adding *all* potential RPROVIDERs would not be the place to start. - Richard Purdie && YP bug review team 97635 2 JPEWhacker 2023-12-21 15:42:25 +0000 PACKAGES_DYNAMIC matching in two recipes is not really supported by bitbake, and it would be really hard to make it figure out how to correctly resolve that without some really hard and expensive logic. The recommended fix is not to use PACKAGES_DYANMIC in your external modules recipe; in most cases this isn't necessary anyway since you should know which modules the recipe is building and can explicitly list them out instead of relying on the regex matching. PACKAGES_DYNAMIC is really only intended for the case where it's impossible to know what packages a recipe will produce beforehand, as is the case with the kernel as the modules will depend on the kernel config. If you can at all possibly know what packages your recipe produces, you should explicitly list them instead of using PACKAGES_DYNAMIC. 97701 3 ola.x.nilsson 2023-12-22 07:39:25 +0000 You're right, in most cases you probably do know which packages are provided even if dynamic splitting is used. I'm sure it's possible to come up with a scenario where you don't know until the build has been configured which packages will be provided, but at least you will get some kind of indication when the recipe fails to provide a package someone else RDEPENDS on. 97702 4 ola.x.nilsson 2023-12-22 08:42:35 +0000 For posterity; you should add the (potential) names of any dynamic packages to PACKAGES. Prepend or append according to the do_split_packages' prepend argument used. 99501 5 richard.purdie 2024-08-06 14:23:27 +0000 Resolving this as we have an agree solution which sounds like the right thing to do to me.