15228 2023-10-09 13:18:16 +0000 Build issue with poky-tiny and genericx86-64 set 2023-10-30 11:44:04 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake unspecified x86 x86_64 RESOLVED NOTABUG Medium normal 5.0 1 johnpaulgoogl bruce.ashfield poky.bs.watcher poky.watcher randy.macleod --- --- Don't know oldest_to_newest 96666 0 johnpaulgoogl 2023-10-09 13:18:16 +0000 Facing build issue with combination 'poky-tiny' and 'genericx86-64' which looks related to kernel configuration. Since am new to yocto build system, would like to know this mention scenario validity and inputs / suggestions to make this build happen. Requirements: Minimal build which to support laptop type x86-64. Build sizes preferable less than 10Mb which together bzImage+rootfs. For this, changes made to local.conf at dunfell branch: MACHINE ?= "genericx86-64" DISTRO ?= "poky-tiny" PACKAGE_CLASSES ?= "package_ipk" Then, build failed with mention error logs: $ bitbake core-image-minimal Loading cache: 100% | | ETA: --:--:-- Loaded 0 entries from dependency cache. Parsing recipes: 100% |#####################################################################################################################################################################| Time: 0:00:13 Parsing of 914 .bb files complete (0 cached, 914 parsed). 1849 targets, 311 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'virtual/kernel' linux-yocto-tiny PROVIDES virtual/kernel but was skipped: incompatible with machine genericx86-64 (not in COMPATIBLE_MACHINE) linux-yocto-tiny PROVIDES virtual/kernel but was skipped: incompatible with machine genericx86-64 (not in COMPATIBLE_MACHINE) linux-yocto-tiny PROVIDES virtual/kernel but was skipped: incompatible with machine genericx86-64 (not in COMPATIBLE_MACHINE) linux-yocto-upstream PROVIDES virtual/kernel but was skipped: Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-upstream to enable it linux-yocto PROVIDES virtual/kernel but was skipped: Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto to enable it linux-yocto-rt PROVIDES virtual/kernel but was skipped: incompatible with machine genericx86-64 (not in COMPATIBLE_MACHINE) linux-yocto-rt PROVIDES virtual/kernel but was skipped: incompatible with machine genericx86-64 (not in COMPATIBLE_MACHINE) linux-yocto-dev PROVIDES virtual/kernel but was skipped: Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-dev to enable it linux-yocto-rt PROVIDES virtual/kernel but was skipped: incompatible with machine genericx86-64 (not in COMPATIBLE_MACHINE) linux-yocto-upstream PROVIDES virtual/kernel but was skipped: incompatible with machine genericx86-64 (not in COMPATIBLE_MACHINE) linux-yocto PROVIDES virtual/kernel but was skipped: incompatible with machine genericx86-64 (not in COMPATIBLE_MACHINE) linux-dummy PROVIDES virtual/kernel but was skipped: PREFERRED_PROVIDER_virtual/kernel set to linux-yocto-tiny, not linux-dummy linux-yocto-upstream PROVIDES virtual/kernel but was skipped: incompatible with machine genericx86-64 (not in COMPATIBLE_MACHINE) linux-yocto PROVIDES virtual/kernel but was skipped: incompatible with machine genericx86-64 (not in COMPATIBLE_MACHINE) ERROR: Required build target 'core-image-minimal' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-minimal', 'virtual/kernel'] Summary: There were 2 ERROR messages, returning a non-zero exit code. $ Thanks in advance! BR, John 96702 1 bruce.ashfield 2023-10-13 12:35:48 +0000 Hi John, What you are running into is the standard bitbake compatibility checking for recipes (the kernel and this case) and machines (MACHINE in OE terms). Similar checks exist for recipes and architectures (i.e. mips or ARM may not be compatible with an application, etc). The details around the variables are here: https://docs.yoctoproject.org/ref-manual/variables.html?highlight=compatible_machine#term-COMPATIBLE_MACHINE And for BSPs, here: https://docs.yoctoproject.org/bsp-guide/bsp.html?highlight=compatible_machine To answer the specific question, we only test and support -tiny against specific machines. You can see them in the linux-yocto-tiny* recipes in oe-core. It is currently this: COMPATIBLE_MACHINE = "^(qemux86|qemux86-64|qemuarm64|qemuarm|qemuarmv5)$" -tiny for the kernel is largely a set of configuration changes (it used to carry patches as well), so we do need to validate a board. When the -tiny kernel is configured ALL options are disabled, and then only what is needed is enabled. The standard and preempt-rt kernel types allow Kconfig defaults and then customize from there. It is that all off starting point that requires the effort to support a machine as we can't rely on defaults to understand what is really needed for a board. Adding genericx86-64 is possible, since it is close to the qemux86-64, and it is something you could do in a layer for testing. But I would suggest looking at the size of things using poky-tiny and qemux86-64 as a start, and comparing it to the default 'poky' distro with the same machine. The saving may not be significant enough to warrant the effort at adding the support for -tiny. If you do want to add the support, then the documentation / guides and some tutorials go over the steps to accomplish that. 97038 2 johnpaulgoogl 2023-10-30 11:44:04 +0000 Hi Bruce, Thanks for the update and explanation with reference links, appreciated! Will try with qemu_x86_64 for compare fallowed by required updates per setup. BR, John