With the following git revisions: bitbake - bef724057f1ea81571dd3ac5a9cf862f818434b5 openembedded-core - 27d068d05239c26a3848eb101571acab54635e37 Running the following commands: git clone git://git.openembedded.org/openembedded-core cd openembedded-core git clone git://git.openembedded.org/bitbake . oe-init-build-env sed -i "s|invalid PACKAGECONFIG: %s\" % (pn,|invalid PACKAGECONFIG: %s\" % (d.getVar('FILE', True),|" ../meta/classes/base.bbclass echo 'PACKAGECONFIG_append_pn-busybox = " invalid"' >> conf/local.conf bitbake -c fetch busybox Shows the following warnings while parsing recipes: WARNING: /home/net147/git/openembedded-core/meta/recipes-core/busybox/busybox_git.bb: invalid PACKAGECONFIG: invalid WARNING: /home/net147/git/openembedded-core/meta/recipes-core/busybox/busybox_1.23.2.bb: invalid PACKAGECONFIG: invalid This indicates that the PACKAGECONFIG is checked against all versions of a recipe regardless of the recipe that is actually used. This is an issue if different versions of recipes support different sets of PACKAGECONFIG values which may result in bogus warnings.
This issue was introduced by the following commit: From be085657bbab34bb8a822682897f96871bb2d8f4 Mon Sep 17 00:00:00 2001 From: Robert Yang <liezhi.yang@windriver.com> Date: Thu, 11 Jun 2015 02:08:41 -0700 Subject: base.class: warn for invalid PACKAGECONFIG There may be typos or out of date values in PACKAGECONFIG, check and warn them. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Whilst checking the recipes that are actually used is an arguable optimisation, I don't understand why it would be fine for some versions of recipes to have incorrect PACKAGECONFIG lines.
My issue is that I have an older version of a recipe in my own layer that takes precedence over the version in openembedded-core. The newer version in openembedded-core removed a PACKAGECONFIG that I use in the older version so I get a warning about the PACKAGECONFIG not existing in the newer version.
(In reply to comment #3) > My issue is that I have an older version of a recipe in my own layer that > takes precedence over the version in openembedded-core. The newer version in > openembedded-core removed a PACKAGECONFIG that I use in the older version so > I get a warning about the PACKAGECONFIG not existing in the newer version. Maybe you need adjust the location of your PACKAGECONFIG ? How can the newer version get the older version's PACKAGECONFIG ?
I'm guessing the situation is that oe-core has one version of a recipe, a private layer has another version of a recipe, and a distro sets PACKAGECONFIG_pn-recipe. At this point both recipes have the same PACKAGECONFIG set, but the flags supported may be different. We could fix this by moving the sanity check further down the build so that it doesn't happen at parse time but when the recipe is actually built.
(In reply to comment #5) > I'm guessing the situation is that oe-core has one version of a recipe, a > private layer has another version of a recipe, and a distro sets > PACKAGECONFIG_pn-recipe. At this point both recipes have the same > PACKAGECONFIG set, but the flags supported may be different. > > We could fix this by moving the sanity check further down the build so that > it doesn't happen at parse time but when the recipe is actually built. Thanks, sounds good.
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=1df8af4248250b9bdbde3b15a00933cf49dd1356
Verified on master: commit 524c590fb44d0ef9711accf2db1a21e4a3cbcfc2