Bug 13607 - can't run bitbake on multiple multiconfig recipes
Summary: can't run bitbake on multiple multiconfig recipes
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 2.7.2
Hardware: x86 x86_64
: Medium+ normal
Target Milestone: 3.2 M2
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard: backport?
Depends on:
Blocks:
 
Reported: 2019-10-21 19:01 UTC by Jonathan Richardson
Modified: 2020-07-27 09:07 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Richardson 2019-10-21 19:01:47 UTC 
When using multiconfig I have 2 images that I want to run bitbake on. When not using multiconfig this worked fine:
bitbake image-one image-two

Now I've switched to multiconfig and I run it as:
bitbake multiconfig:target:image-one multiconfig:target:image-two

I get this error:
ERROR: Nothing PROVIDES 'multiconfig:target:image-two'. Close matches:
  image-two

It doesn't look like multiconfig applies to the second image if I don't specify the full multiconfig syntax. The local.conf has EXTRA_IMAGEDEPENDS on other recipes which have multiconfig dependencies on 'crmu'. The multiconfig conf files themselves are simple:

target:
MACHINE = "bcm957604k"

crmu:
MACHINE = "cortexm0"

Running individual bitbake commands works fine. I'm using this version:
version: 2.7+snapshot-20191021
Comment 1 Richard Purdie 2019-10-24 14:49:04 UTC 
Can you test with "mc:" rather than "multiconfig:" and see if that helps?
Comment 2 Jonathan Richardson 2019-11-05 22:07:50 UTC 
I'm going to upgrade all our layers to zeus and will let you know.
Comment 3 Jonathan Richardson 2019-11-06 00:34:40 UTC 
This isn't an issue in zeus. It works fine, thanks.
Comment 4 Robert Yang 2020-01-21 03:25:25 UTC 
There is no such an issue on master branch.
Comment 5 Ricardo Ribalda 2020-06-08 08:38:24 UTC 
Hi
This is exists on current master

56e211d0f3c6cb84f5982e5de00faeeed69c1912


ricardo@neopili:/tmp/openembedded-core/build$ bitbake multiconfig:arm:bash multiconfig:arm:busybox
Loading cache: 100% |####################################################################| Time: 0:00:00
Loaded 2643 entries from dependency cache.
Parsing recipes: 100% |##################################################################| Time: 0:00:00
Parsing of 773 .bb files complete (772 cached, 1 parsed). 2644 targets, 163 skipped, 0 masked, 0 errors.
ERROR: Nothing PROVIDES 'multiconfig:arm:busybox'

Summary: There was 1 ERROR message shown, returning a non-zero exit code.

ricardo@neopili:/tmp/openembedded-core/build$ cat conf/multiconfig/arm.conf 
MACHINE = "qemuarm"
Comment 6 Ricardo Ribalda 2020-06-08 08:39:19 UTC 
$ bitbake mc:arm:bash mc:arm:busybox 

works fine
Comment 7 Richard Purdie 2020-07-22 13:26:41 UTC 
Turns out to be a really simple problem, patch on the bitbake mailing list.