Cannot get bitbake multiconfig to work

Cannot get bitbake multiconfig to work

[Mike Looijmans]

I think I've done everything, but cannot figure out what step I missed.

I am using yesterday's "thud" branches:

BB_VERSION           = "1.40.0"
BUILD_SYS            = "x86_64-linux"
meta                 = "HEAD:fbb688ab3eeca1bbfbaaaaffd8c81fd8052bcc68"
meta-oe
meta-multimedia
meta-networking
meta-python          = "HEAD:6ef9657068492d4644079c88f2adee9c3cac9543"


I created a conf/multiconf directory with a "pmu.conf" file (and others)

$ cat conf/multiconfig/pmu.conf
MACHINE="zynqmp-pmu"
DISTRO="xilinx-standalone"
GCCVERSION="7.%"
TMPDIR="${TOPDIR}/pmutmp"

I added to my local.conf (and removed the MACHINE setting there):

BBMULTICONFIG = "pmu ..."

Now when I invoke bitbake with the multiconfig syntax, it completely ignores that:

$ bitbake multiconfig:pmu:pmu-firmware
ERROR:  OE-core's config sanity checker detected a potential misconfiguration.
     Either fix the cause of this error or at your own risk disable the 
checker (see sanity.conf).
     Following is the list of potential problems / advisories:

     Please set a MACHINE in your local.conf or environment


Apparently, bitbake doesn't even care about the "multiconfig:" syntax, I get 
the same response when I type:
$ bitbake multiconfig:blah:pmu-firmware
$ bitbake multiconfig:blah:blah
$ bitbake blah:blah:blah

I can add a "MACHINE?=" to local.conf, which results in a build for that 
machine and nothing from the pmu.conf gets ever used at all.

So what step did I miss?

Re: Cannot get bitbake multiconfig to work

[Richard Purdie]

On Wed, 2019-03-13 at 10:03 +0000, Mike Looijmans wrote:
> I think I've done everything, but cannot figure out what step I
> missed.
> 
> I am using yesterday's "thud" branches:
> 
> BB_VERSION           = "1.40.0"
> BUILD_SYS            = "x86_64-linux"
> meta                 =
> "HEAD:fbb688ab3eeca1bbfbaaaaffd8c81fd8052bcc68"
> meta-oe
> meta-multimedia
> meta-networking
> meta-python          =
> "HEAD:6ef9657068492d4644079c88f2adee9c3cac9543"
> 
> 
> I created a conf/multiconf directory with a "pmu.conf" file (and
> others)
> 
> $ cat conf/multiconfig/pmu.conf
> MACHINE="zynqmp-pmu"
> DISTRO="xilinx-standalone"
> GCCVERSION="7.%"
> TMPDIR="${TOPDIR}/pmutmp"
> 
> I added to my local.conf (and removed the MACHINE setting there):
> 
> BBMULTICONFIG = "pmu ..."
> 
> Now when I invoke bitbake with the multiconfig syntax, it completely
> ignores that:
> 
> $ bitbake multiconfig:pmu:pmu-firmware
> ERROR:  OE-core's config sanity checker detected a potential
> misconfiguration.
>      Either fix the cause of this error or at your own risk disable
> the 
> checker (see sanity.conf).
>      Following is the list of potential problems / advisories:
> 
>      Please set a MACHINE in your local.conf or environment
> 
> 
> Apparently, bitbake doesn't even care about the "multiconfig:"
> syntax, I get 
> the same response when I type:
> $ bitbake multiconfig:blah:pmu-firmware
> $ bitbake multiconfig:blah:blah
> $ bitbake blah:blah:blah
> 
> I can add a "MACHINE?=" to local.conf, which results in a build for
> that 
> machine and nothing from the pmu.conf gets ever used at all.
> 
> So what step did I miss?


The piece most people miss when thinking about multiconfig is that
local.conf still needs to be valid as one of the configurations. Did
you try setting MACHINE to something valid in local.conf and then
building the pmu multiconfig?

Cheers,

Richard

Re: Cannot get bitbake multiconfig to work

[richard.purdie]

On Wed, 2019-03-20 at 13:44 +0000, Mike Looijmans wrote:
> I tried providing MACHINE in local.conf, which just resulted in a
> build for that machine, and whatever multiconfig I passed on the
> commandline still got completely ignored. I even put "garbage" into
> the pmu.conf file and it was happy with that too.

Its hard for me to know what to say to that.

We have a test for multiconfig now:

http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=d9018a3d9c828551c465b68b27920ec4681524ae

If you configure a multiconfig and then try and build it with something
like "bitbake multiconfig:pmu:XXX" then it should build XXX for the
MACHINE set in the pmu multiconfig. You are hard setting things like
the MACHINE in the pmu.conf?

Does:

bitbake -e -b multiconfig:pmu:bash | grep MACHINE=

show what you'd expect?

If its still not working we need to be able to replicate the
configuration that isn't working or at least see the local.conf and
pmu.conf that don't work. We simply don't have enough info other than
to speculate on what might be wrong.

Cheers,

Richard