Regression caused by new multiconfig dependency

[Jan Kiszka <jan.kiszka@web.de>]

Hi all,

since da8cb8633504 ("bitbake: Add support for multiconfig dependencies"), it's 
no longer possible to write recipes that have multiconfig-dependent names:


mc1.conf:
MACHINE = "a"

mc2.conf:
MACHINE = "b"

some-target.bb:
PN = "some-target-${MACHINE}"

local.conf:
BBMULTICONFIG = "mc1 mc2"


# bitbake multiconfig:mc1:some-target-a
[...]
ERROR: Nothing PROVIDES 'some-target-a'. Close matches:
   some-target-b

# bitbake multiconfig:mc2:some-target-b
ERROR: Nothing PROVIDES 'some-target-b'. Close matches:
   some-target-a


That works fine when going back to da8cb8633504^ or when only having the 
selected multiconfig in BBMULTICONFIG. Seems the parser stumbles while 
processing the unselected multiconfig paths.

Jan