Hi all,

Well, I don't even know where to start debugging this, so that isn't very good.

I had working OE-RPB builds for the WaRP7 board (MACHINE=imx7s-warp), then repo locked out the relative symlinks. Nico fixed that in OE-RPB, and I rebased to his fix.

But it didn't fix my builds.

My manifest repo is here:

https://git.linaro.org/people/ryan.harkin/oe-rpb-manifest.git/log/?h=warrior

My meta-layer is here:

https://git.linaro.org/people/ryan.harkin/meta-warp7.git/log/?h=warrior

As you can see, they're both simple, just to get the board added to OE-RPB.

I now have two environments: my original warrior workspace that still builds, so long as I don't try to "repo sync", and my new workspace from a fresh clone that gives me this error:

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:

    MACHINE=imx7s-warp is invalid. Please set a valid MACHINE in your local.conf, environment or other configuration file.

I'm guessing the problem is in meta-freescale-3rdparty where imx7s-warp is defined, not my simple layers, but I have no clue where to start debugging this.

Any advice on where to start??

Here's a CI job that builds and fails as described above:

https://ci.linaro.org/job/warp7-openembedded-warrior/161/DISTRO=rpb,label=docker-stretch-amd64/consoleText

Here's the previous job from before the changes that succeeded:

https://ci.linaro.org/job/warp7-openembedded-warrior/160/DISTRO=rpb,label=docker-stretch-amd64/consoleText

Thanks,

Ryan.

_______________________________________________
OpenEmbedded mailing list
OpenEmbedded@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/openembedded