I’m trying to build a new image following the instructions here;
When I get to issuing the bitbake command, I get the following error;
zygo@zygo-OptiPlex-7040:~/work/i.MX8X/Toradex_iMX8QXP/bin/imx-yocto-bsp/build$ bitbake -k fsl-image-validation-imx
NOTE: Your conf/bblayers.conf has been automatically updated.
NOTE: Your conf/bblayers.conf has been automatically updated.
WARNING: Host distribution "Ubuntu-16.04" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
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 valid MACHINE in your local.conf or environment
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
I’m not concerned so much with the Ubuntu warning, but instead with the MACHINE error. Here is the local.conf file;
Had a similar issue: did the setup and build for Apalis iMX8 without issues (using Apalis iMX8 manifest-branch and manifest-file) and when I used the same setup for building the image for Colibri iMX8X I got this error. Only then I have noticed that for Colibri iMX8X those are different values and the build setup is not shared.
Same Issue for me, Could you please some help me with this
~/imx-yocto-bsp/build1$ bitbake -k fsl-image-validation-imx
WARNING: /home/vagrant/imx-yocto-bsp/sources/poky/meta/lib/oe/maketype.py:99: DeprecationWarning: Using or importing the ABCs from ‘collections’ instead of from ‘collections.abc’ is deprecated since Python 3.3, and in 3.9 it will stop working
if not isinstance(obj, collections.Callable):
NOTE: Your conf/bblayers.conf has been automatically updated.
WARNING: Host distribution “ubuntu-20.04” has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
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:
Fetcher failure for URL: 'https://www.example.com/'. URL https://www.example.com/ doesn't work.
Please ensure your host's network is configured correctly,
or set BB_NO_NETWORK = "1" to disable network access if
all required sources are on local disk.
Summary: There were 2 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.