If, by accident, the user has omitted oe-core from bblayers.conf but other layers are present in bblayers.conf, then the error message will flag the first such layer in bblayers (e.g. mylayer) and report:

ERROR: Layer mylayer is not compatible with the core layer which only supports these series:  (layer is compatible with hardknott)

Maybe this situation can be detected and a better error message emitted?

Apparently (according to JaMa and kergoth) this is an issue with no LAYERSERIES_CORENAMES being defined (?)








NOTE: if no layers are present in bblayers.conf then one get the error message:

ERROR: Traceback (most recent call last):
  File "/z/build-master/corenames/layers/bitbake/lib/bb/cookerdata.py", line 162, in wrapped
    return func(fn, *args)
  File "/z/build-master/corenames/layers/bitbake/lib/bb/cookerdata.py", line 187, in parse_config_file
    return bb.parse.handle(fn, data, include)
  File "/z/build-master/corenames/layers/bitbake/lib/bb/parse/__init__.py", line 107, in handle
    return h['handle'](fn, data, include)
  File "/z/build-master/corenames/layers/bitbake/lib/bb/parse/parse_py/ConfHandler.py", line 121, in handle
    abs_fn = resolve_file(fn, data)
  File "/z/build-master/corenames/layers/bitbake/lib/bb/parse/__init__.py", line 125, in resolve_file
    raise IOError(errno.ENOENT, "file %s not found in %s" % (fn, bbpath))
FileNotFoundError: [Errno 2] file conf/bitbake.conf not found in /z/build-master/corenames/build

ERROR: Unable to parse conf/bitbake.conf: [Errno 2] file conf/bitbake.conf not found in /z/build-master/corenames/build