All of lore.kernel.org
 help / color / mirror / Atom feed
* Problems building eSDK: Exception: variable BBFILES references itself!
@ 2022-02-09 16:51 Bryan Evenson
       [not found] ` <650b02092ecfc1579ac9f2763e4c3fc70e54601a.camel@linuxfoundation.org>
  0 siblings, 1 reply; 6+ messages in thread
From: Bryan Evenson @ 2022-02-09 16:51 UTC (permalink / raw)
  To: yocto

All,

I've used the SDK in the past and want to start using the eSDK for my project.  I'm on the dunfell branch.  I'm trying to build the eSDK for my image by calling:

bitbake <my_image_name> -c populate_sdk_ext

The sdk generation fails with the error in the subject.  I haven't been able to find any documentation on what this means or how to fix it.  I've tried deleting my tmp directory and running cleansstate on my image and I still get the same error.  I've also tried generating the eSDK for core-image-minimal and I have the same error.  I can generate the SDK successfully, just not the eSDK.  I have copied more of the build output below if it helps.  Note that I have replaced some text that I'm paranoid about publishing on the internet; the modified text is enclosed with <>.

Does anyone have any insight as to why the eSDK build is failing?

Thanks,
Bryan

NOTE: Running intercept scripts:
NOTE: Executing buildhistory_list_installed_sdk_host ...
DEBUG: Executing python function buildhistory_list_installed_sdk_host
DEBUG: Python function buildhistory_list_installed_sdk_host finished
NOTE: Executing buildhistory_get_sdk_installed_host ...
DEBUG: Executing shell function buildhistory_get_sdk_installed_host
DEBUG: Shell function buildhistory_get_sdk_installed_host finished
NOTE: Executing copy_buildsystem ...
DEBUG: Executing python function copy_buildsystem
NOTE: Excluding local workspace layer <my_home_dir>/poky/poky-build/workspace from extensible SDK
NOTE: Generating sstate task list...
ERROR: Failed to generate filtered task list for extensible SDK:

### Shell environment set up for builds. ###

You can now run 'bitbake <target>'

Common targets are:
    core-image-minimal
    core-image-sato
    meta-toolchain
    meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86'

Other commonly useful commands are:
 - 'devtool' and 'recipetool' handle common recipe tasks
 - 'bitbake-layers' handles common layer tasks
 - 'oe-pkgdata-util' handles common target package tasks
ERROR: bitbake failed:
ERROR: Command execution failed: Traceback (most recent call last):
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/data_smart.py", line 401, in expandWithRefs
    s = __expand_var_regexp__.sub(varparse.var_sub, s)
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/data_smart.py", line 96, in var_sub
    raise Exception("variable %s references itself!" % self.varname)
Exception: variable BBFILES references itself!

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/command.py", line 107, in runAsyncCommand
    self.cooker.updateCache()
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/cooker.py", line 1558, in updateCache
    (filelist, masked, searchdirs) = self.collection.collect_bbfiles(self.data, self.data)
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/cooker.py", line 1729, in collect_bbfiles
    files = (config.getVar( "BBFILES") or "").split()
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/data_smart.py", line 589, in getVar
    return self.getVarFlag(var, "_content", expand, noweakdefault, parsing)
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/data_smart.py", line 780, in getVarFlag
    parser = self.expandWithRefs(value, cachename)
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/data_smart.py", line 418, in expandWithRefs
    raise ExpansionError(varname, s, exc).with_traceback(tb) from exc
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/data_smart.py", line 401, in expandWithRefs
    s = __expand_var_regexp__.sub(varparse.var_sub, s)
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/data_smart.py", line 96, in var_sub
    raise Exception("variable %s references itself!" % self.varname)
bb.data_smart.ExpansionError: Failure expanding variable BBFILES, expression was ${BBFILES} <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/<my_custom_layer1>/recipes-*/*/*.bb 	<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/<my_custom_layer1>/recipes-*/*/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/<my_custom_layer2>/recipes*/*/*.bb <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/<my_custom_layer2>/recipes*/*/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-bacnet/recipes-*/*/*.bb 	<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-bacnet/recipes-*/*/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-atmel/recipes*/*/*.bb <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-atmel/recipes*/*/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta/recipes-*/*/*.bb <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-poky/recipes-*/*/*.bb             <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-poky/recipes-*/*/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-yocto-bsp/recipes-*/*/*.bb             <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-yocto-bsp/recipes-*/*/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-openembedded/meta-oe/recipes-*/*/*.bb <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-openembedded/meta-oe/recipes-*/*/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-openembedded/meta-networking/recipes-*/*/*.bb             <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-openembedded/meta-networking/recipes-*/*/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-openembedded/meta-python/recipes*/*/*.bb <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-openembedded/meta-python/recipes*/*/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/workspace/recipes/*/*.bb             <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/workspace/appends/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-*/*/*.bb which triggered exception Exception: variable BBFILES references itself!


Summary: There was 1 ERROR message shown, returning a non-zero exit code.
Execution of '. layers/poky/oe-init-build-env .; PYTHONDONTWRITEBYTECODE=1 BB_SETSCENE_ENFORCE=1 PSEUDO_DISABLED=1 oe-check-sstate <my_image_name> meta-extsdk-toolchain:do_populate_sysroot -s -o <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/tasklist.txt -l <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/tasklist_bb_log.txt' failed with exit code 1:

### Shell environment set up for builds. ###

You can now run 'bitbake <target>'

Common targets are:
    core-image-minimal
    core-image-sato
    meta-toolchain
    meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86'

Other commonly useful commands are:
 - 'devtool' and 'recipetool' handle common recipe tasks
 - 'bitbake-layers' handles common layer tasks
 - 'oe-pkgdata-util' handles common target package tasks
ERROR: bitbake failed:
ERROR: Command execution failed: Traceback (most recent call last):
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/data_smart.py", line 401, in expandWithRefs
    s = __expand_var_regexp__.sub(varparse.var_sub, s)
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/data_smart.py", line 96, in var_sub
    raise Exception("variable %s references itself!" % self.varname)
Exception: variable BBFILES references itself!

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/command.py", line 107, in runAsyncCommand
    self.cooker.updateCache()
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/cooker.py", line 1558, in updateCache
    (filelist, masked, searchdirs) = self.collection.collect_bbfiles(self.data, self.data)
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/cooker.py", line 1729, in collect_bbfiles
    files = (config.getVar( "BBFILES") or "").split()
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/data_smart.py", line 589, in getVar
    return self.getVarFlag(var, "_content", expand, noweakdefault, parsing)
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/data_smart.py", line 780, in getVarFlag
    parser = self.expandWithRefs(value, cachename)
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/data_smart.py", line 418, in expandWithRefs
    raise ExpansionError(varname, s, exc).with_traceback(tb) from exc
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/data_smart.py", line 401, in expandWithRefs
    s = __expand_var_regexp__.sub(varparse.var_sub, s)
  File "<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/bitbake/lib/bb/data_smart.py", line 96, in var_sub
    raise Exception("variable %s references itself!" % self.varname)
bb.data_smart.ExpansionError: Failure expanding variable BBFILES, expression was ${BBFILES} <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/<my_custom_layer1>/recipes-*/*/*.bb 	<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/<my_custom_layer1>/recipes-*/*/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/<my_custom_layer2>/recipes*/*/*.bb <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/<my_custom_layer2>/recipes*/*/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-bacnet/recipes-*/*/*.bb 	<my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-bacnet/recipes-*/*/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-atmel/recipes*/*/*.bb <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-atmel/recipes*/*/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta/recipes-*/*/*.bb <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-poky/recipes-*/*/*.bb             <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-poky/recipes-*/*/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-yocto-bsp/recipes-*/*/*.bb             <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-yocto-bsp/recipes-*/*/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-openembedded/meta-oe/recipes-*/*/*.bb <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-openembedded/meta-oe/recipes-*/*/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-openembedded/meta-networking/recipes-*/*/*.bb             <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-openembedded/meta-networking/recipes-*/*/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-openembedded/meta-python/recipes*/*/*.bb <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-openembedded/meta-python/recipes*/*/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/workspace/recipes/*/*.bb             <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/workspace/appends/*.bbappend <my_home_dir>/poky/poky-build/tmp/work/at91sam9x5ek-poky-linux-gnueabi/<my_image_name>/1.0-r0/sdk-ext/image/tmp-renamed-sdk/layers/poky/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-*/*/*.bb which triggered exception Exception: variable BBFILES references itself!


Summary: There was 1 ERROR message shown, returning a non-zero exit code.


DEBUG: Python function copy_buildsystem finished
DEBUG: Python function do_populate_sdk_ext finished


^ permalink raw reply	[flat|nested] 6+ messages in thread
* RE: [yocto] Problems building eSDK: Exception: variable BBFILES references itself!
       [not found] ` <650b02092ecfc1579ac9f2763e4c3fc70e54601a.camel@linuxfoundation.org>
@ 2022-02-09 18:10   ` Bryan Evenson
  2022-02-09 18:50     ` Richard Purdie
  0 siblings, 1 reply; 6+ messages in thread
From: Bryan Evenson @ 2022-02-09 18:10 UTC (permalink / raw)
  To: Richard Purdie, yocto

Richard,

> -----Original Message-----
> From: Richard Purdie <richard.purdie@linuxfoundation.org>
> Sent: Wednesday, February 9, 2022 12:25 PM
> To: Bryan Evenson <bevenson@melinkcorp.com>;
> yocto@lists.yoctoproject.org
> Subject: Re: [yocto] Problems building eSDK: Exception: variable BBFILES
> references itself!
> 
> On Wed, 2022-02-09 at 16:51 +0000, Bryan Evenson wrote:
> > All,
> >
> > I've used the SDK in the past and want to start using the eSDK for my
> project.
> > I'm on the dunfell branch.  I'm trying to build the eSDK for my image
> > by
> > calling:
> >
> > bitbake <my_image_name> -c populate_sdk_ext
> >
> > The sdk generation fails with the error in the subject.  I haven't
> > been able to find any documentation on what this means or how to fix
> > it.  I've tried deleting my tmp directory and running cleansstate on
> > my image and I still get the same error.  I've also tried generating
> > the eSDK for core-image-minimal and I have the same error.  I can
> > generate the SDK successfully, just not the eSDK.  I have copied more
> > of the build output below if it helps.  Note that I have replaced some
> > text that I'm paranoid about publishing on the internet; the modified text is
> enclosed with <>.
> >
> > Does anyone have any insight as to why the eSDK build is failing?
> 
> Could you share what bitbake -e shows BBFILES as being set to? The variable
> history from that command for the variable may also be helpful.
> 
> There has to be something different to how you're setting it compared to
> what we test on the autobuilder.
> 
> Cheers,
> 
> Richard

Here's what I was able to pull from bitbake -e.  I've included details for both BBFILES and BBFILES_DYNAMIC.  Let me know if anything else would be helpful.

Thanks,
Bryan

# $BBFILES [24 operations]
#   set? <my_home_dir>/poky/poky-build/conf/bblayers.conf:6
#     ""
#   immediate <my_home_dir>/poky/<my_custom_layer1>/conf/layer.conf:6
#     "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb 	${LAYERDIR}/recipes-*/*/*.bbappend"
#   append <my_home_dir>/poky/<my_custom_layer2>/conf/layer.conf:5
#     "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
#   set data_smart.py:945 [expandVarref]
#     " <my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bb 	<my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bbappend <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bb <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bbappend"
#   append <my_home_dir>/poky/meta-bacnet/conf/layer.conf:6
#     "${LAYERDIR}/recipes-*/*/*.bb 	${LAYERDIR}/recipes-*/*/*.bbappend"
#   set data_smart.py:945 [expandVarref]
#     " <my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bb 	<my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bbappend <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bb <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bbappend <my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bb 	<my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bbappend"
#   append <my_home_dir>/poky/meta-atmel/conf/layer.conf:5
#     "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
#   set data_smart.py:945 [expandVarref]
#     " <my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bb 	<my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bbappend <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bb <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bbappend <my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bb 	<my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-atmel/recipes*/*/*.bb <my_home_dir>/poky/meta-atmel/recipes*/*/*.bbappend"
#   append <my_home_dir>/poky/meta/conf/layer.conf:4
#     "${LAYERDIR}/recipes-*/*/*.bb"
#   set data_smart.py:945 [expandVarref]
#     " <my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bb 	<my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bbappend <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bb <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bbappend <my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bb 	<my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-atmel/recipes*/*/*.bb <my_home_dir>/poky/meta-atmel/recipes*/*/*.bbappend <my_home_dir>/poky/meta/recipes-*/*/*.bb"
#   append <my_home_dir>/poky/meta-poky/conf/layer.conf:6
#     "${LAYERDIR}/recipes-*/*/*.bb             ${LAYERDIR}/recipes-*/*/*.bbappend"
#   set data_smart.py:945 [expandVarref]
#     " <my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bb 	<my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bbappend <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bb <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bbappend <my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bb 	<my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-atmel/recipes*/*/*.bb <my_home_dir>/poky/meta-atmel/recipes*/*/*.bbappend <my_home_dir>/poky/meta/recipes-*/*/*.bb <my_home_dir>/poky/meta-poky/recipes-*/*/*.bb             <my_home_dir>/poky/meta-poky/recipes-*/*/*.bbappend"
#   append <my_home_dir>/poky/meta-yocto-bsp/conf/layer.conf:6
#     "${LAYERDIR}/recipes-*/*/*.bb             ${LAYERDIR}/recipes-*/*/*.bbappend"
#   set data_smart.py:945 [expandVarref]
#     " <my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bb 	<my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bbappend <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bb <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bbappend <my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bb 	<my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-atmel/recipes*/*/*.bb <my_home_dir>/poky/meta-atmel/recipes*/*/*.bbappend <my_home_dir>/poky/meta/recipes-*/*/*.bb <my_home_dir>/poky/meta-poky/recipes-*/*/*.bb             <my_home_dir>/poky/meta-poky/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-yocto-bsp/recipes-*/*/*.bb             <my_home_dir>/poky/meta-yocto-bsp/recipes-*/*/*.bbappend"
#   append <my_home_dir>/poky/meta-openembedded/meta-oe/conf/layer.conf:15
#     "${LAYERDIR}/recipes-*/*/*.bb ${LAYERDIR}/recipes-*/*/*.bbappend"
#   set data_smart.py:945 [expandVarref]
#     " <my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bb 	<my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bbappend <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bb <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bbappend <my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bb 	<my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-atmel/recipes*/*/*.bb <my_home_dir>/poky/meta-atmel/recipes*/*/*.bbappend <my_home_dir>/poky/meta/recipes-*/*/*.bb <my_home_dir>/poky/meta-poky/recipes-*/*/*.bb             <my_home_dir>/poky/meta-poky/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-yocto-bsp/recipes-*/*/*.bb             <my_home_dir>/poky/meta-yocto-bsp/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-openembedded/meta-oe/recipes-*/*/*.bb <my_home_dir>/poky/meta-openembedded/meta-oe/recipes-*/*/*.bbappend"
#   append <my_home_dir>/poky/meta-openembedded/meta-networking/conf/layer.conf:6
#     "${LAYERDIR}/recipes-*/*/*.bb             ${LAYERDIR}/recipes-*/*/*.bbappend"
#   set data_smart.py:945 [expandVarref]
#     " <my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bb 	<my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bbappend <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bb <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bbappend <my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bb 	<my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-atmel/recipes*/*/*.bb <my_home_dir>/poky/meta-atmel/recipes*/*/*.bbappend <my_home_dir>/poky/meta/recipes-*/*/*.bb <my_home_dir>/poky/meta-poky/recipes-*/*/*.bb             <my_home_dir>/poky/meta-poky/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-yocto-bsp/recipes-*/*/*.bb             <my_home_dir>/poky/meta-yocto-bsp/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-openembedded/meta-oe/recipes-*/*/*.bb <my_home_dir>/poky/meta-openembedded/meta-oe/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-openembedded/meta-networking/recipes-*/*/*.bb             <my_home_dir>/poky/meta-openembedded/meta-networking/recipes-*/*/*.bbappend"
#   append <my_home_dir>/poky/meta-openembedded/meta-python/conf/layer.conf:5
#     "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
#   set data_smart.py:945 [expandVarref]
#     " <my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bb 	<my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bbappend <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bb <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bbappend <my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bb 	<my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-atmel/recipes*/*/*.bb <my_home_dir>/poky/meta-atmel/recipes*/*/*.bbappend <my_home_dir>/poky/meta/recipes-*/*/*.bb <my_home_dir>/poky/meta-poky/recipes-*/*/*.bb             <my_home_dir>/poky/meta-poky/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-yocto-bsp/recipes-*/*/*.bb             <my_home_dir>/poky/meta-yocto-bsp/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-openembedded/meta-oe/recipes-*/*/*.bb <my_home_dir>/poky/meta-openembedded/meta-oe/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-openembedded/meta-networking/recipes-*/*/*.bb             <my_home_dir>/poky/meta-openembedded/meta-networking/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-openembedded/meta-python/recipes*/*/*.bb <my_home_dir>/poky/meta-openembedded/meta-python/recipes*/*/*.bbappend"
#   append <my_home_dir>/poky/poky-build/workspace/conf/layer.conf:4
#     "${LAYERDIR}/recipes/*/*.bb             ${LAYERDIR}/appends/*.bbappend"
#   set data_smart.py:945 [expandVarref]
#     " <my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bb 	<my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bbappend <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bb <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bbappend <my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bb 	<my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-atmel/recipes*/*/*.bb <my_home_dir>/poky/meta-atmel/recipes*/*/*.bbappend <my_home_dir>/poky/meta/recipes-*/*/*.bb <my_home_dir>/poky/meta-poky/recipes-*/*/*.bb             <my_home_dir>/poky/meta-poky/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-yocto-bsp/recipes-*/*/*.bb             <my_home_dir>/poky/meta-yocto-bsp/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-openembedded/meta-oe/recipes-*/*/*.bb <my_home_dir>/poky/meta-openembedded/meta-oe/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-openembedded/meta-networking/recipes-*/*/*.bb             <my_home_dir>/poky/meta-openembedded/meta-networking/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-openembedded/meta-python/recipes*/*/*.bb <my_home_dir>/poky/meta-openembedded/meta-python/recipes*/*/*.bbappend <my_home_dir>/poky/poky-build/workspace/recipes/*/*.bb             <my_home_dir>/poky/poky-build/workspace/appends/*.bbappend"
#   append cookerdata.py:401 [parseConfigurationFiles]
#     " <my_home_dir>/poky/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-*/*/*.bb"
#   set <my_home_dir>/poky/meta/conf/documentation.conf:90
#     [doc] "List of recipe files used by BitBake to build software."
# pre-expansion value:
#   " <my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bb 	<my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bbappend <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bb <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bbappend <my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bb 	<my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-atmel/recipes*/*/*.bb <my_home_dir>/poky/meta-atmel/recipes*/*/*.bbappend <my_home_dir>/poky/meta/recipes-*/*/*.bb <my_home_dir>/poky/meta-poky/recipes-*/*/*.bb             <my_home_dir>/poky/meta-poky/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-yocto-bsp/recipes-*/*/*.bb             <my_home_dir>/poky/meta-yocto-bsp/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-openembedded/meta-oe/recipes-*/*/*.bb <my_home_dir>/poky/meta-openembedded/meta-oe/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-openembedded/meta-networking/recipes-*/*/*.bb             <my_home_dir>/poky/meta-openembedded/meta-networking/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-openembedded/meta-python/recipes*/*/*.bb <my_home_dir>/poky/meta-openembedded/meta-python/recipes*/*/*.bbappend <my_home_dir>/poky/poky-build/workspace/recipes/*/*.bb             <my_home_dir>/poky/poky-build/workspace/appends/*.bbappend <my_home_dir>/poky/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-*/*/*.bb"
BBFILES=" <my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bb 	<my_home_dir>/poky/<my_custom_layer1>/recipes-*/*/*.bbappend <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bb <my_home_dir>/poky/<my_custom_layer2>/recipes*/*/*.bbappend <my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bb 	<my_home_dir>/poky/meta-bacnet/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-atmel/recipes*/*/*.bb <my_home_dir>/poky/meta-atmel/recipes*/*/*.bbappend <my_home_dir>/poky/meta/recipes-*/*/*.bb <my_home_dir>/poky/meta-poky/recipes-*/*/*.bb             <my_home_dir>/poky/meta-poky/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-yocto-bsp/recipes-*/*/*.bb             <my_home_dir>/poky/meta-yocto-bsp/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-openembedded/meta-oe/recipes-*/*/*.bb <my_home_dir>/poky/meta-openembedded/meta-oe/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-openembedded/meta-networking/recipes-*/*/*.bb             <my_home_dir>/poky/meta-openembedded/meta-networking/recipes-*/*/*.bbappend <my_home_dir>/poky/meta-openembedded/meta-python/recipes*/*/*.bb <my_home_dir>/poky/meta-openembedded/meta-python/recipes*/*/*.bbappend <my_home_dir>/poky/poky-build/workspace/recipes/*/*.bb             <my_home_dir>/poky/poky-build/workspace/appends/*.bbappend <my_home_dir>/poky/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-*/*/*.bb"
#
# $BBFILES_DYNAMIC [4 operations]
#   append <my_home_dir>/poky/meta-atmel/conf/layer.conf:21
#     "   meta-aws:${LAYERDIR}/dynamic-layers/aws-layer/*/*/*.bb   meta-aws:${LAYERDIR}/dynamic-layers/aws-layer/*/*/*.bbappend "
#   set data_smart.py:945 [expandVarref]
#     "    meta-aws:<my_home_dir>/poky/meta-atmel/dynamic-layers/aws-layer/*/*/*.bb   meta-aws:<my_home_dir>/poky/meta-atmel/dynamic-layers/aws-layer/*/*/*.bbappend "
#   append <my_home_dir>/poky/meta-openembedded/meta-oe/conf/layer.conf:31
#     " meta-python:${LAYERDIR}/dynamic-layers/meta-python/recipes-*/*/*.bb perl-layer:${LAYERDIR}/dynamic-layers/perl-layer/recipes-*/*/*.bb "
#   set data_smart.py:945 [expandVarref]
#     "    meta-aws:<my_home_dir>/poky/meta-atmel/dynamic-layers/aws-layer/*/*/*.bb   meta-aws:<my_home_dir>/poky/meta-atmel/dynamic-layers/aws-layer/*/*/*.bbappend   meta-python:<my_home_dir>/poky/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-*/*/*.bb perl-layer:<my_home_dir>/poky/meta-openembedded/meta-oe/dynamic-layers/perl-layer/recipes-*/*/*.bb "
# pre-expansion value:
#   "    meta-aws:<my_home_dir>/poky/meta-atmel/dynamic-layers/aws-layer/*/*/*.bb   meta-aws:<my_home_dir>/poky/meta-atmel/dynamic-layers/aws-layer/*/*/*.bbappend   meta-python:<my_home_dir>/poky/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-*/*/*.bb perl-layer:<my_home_dir>/poky/meta-openembedded/meta-oe/dynamic-layers/perl-layer/recipes-*/*/*.bb "
BBFILES_DYNAMIC="    meta-aws:<my_home_dir>/poky/meta-atmel/dynamic-layers/aws-layer/*/*/*.bb   meta-aws:<my_home_dir>/poky/meta-atmel/dynamic-layers/aws-layer/*/*/*.bbappend   meta-python:<my_home_dir>/poky/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-*/*/*.bb perl-layer:<my_home_dir>/poky/meta-openembedded/meta-oe/dynamic-layers/perl-layer/recipes-*/*/*.bb "


^ permalink raw reply	[flat|nested] 6+ messages in thread
* Re: [yocto] Problems building eSDK: Exception: variable BBFILES references itself!
  2022-02-09 18:10   ` [yocto] " Bryan Evenson
@ 2022-02-09 18:50     ` Richard Purdie
  2022-02-09 19:36       ` Bryan Evenson
  0 siblings, 1 reply; 6+ messages in thread
From: Richard Purdie @ 2022-02-09 18:50 UTC (permalink / raw)
  To: Bryan Evenson, yocto

On Wed, 2022-02-09 at 18:10 +0000, Bryan Evenson wrote:
> Richard,
> 
> > -----Original Message-----
> > From: Richard Purdie <richard.purdie@linuxfoundation.org>
> > Sent: Wednesday, February 9, 2022 12:25 PM
> > To: Bryan Evenson <bevenson@melinkcorp.com>;
> > yocto@lists.yoctoproject.org
> > Subject: Re: [yocto] Problems building eSDK: Exception: variable BBFILES
> > references itself!
> > 
> > On Wed, 2022-02-09 at 16:51 +0000, Bryan Evenson wrote:
> > > All,
> > > 
> > > I've used the SDK in the past and want to start using the eSDK for my
> > project.
> > > I'm on the dunfell branch.  I'm trying to build the eSDK for my image
> > > by
> > > calling:
> > > 
> > > bitbake <my_image_name> -c populate_sdk_ext
> > > 
> > > The sdk generation fails with the error in the subject.  I haven't
> > > been able to find any documentation on what this means or how to fix
> > > it.  I've tried deleting my tmp directory and running cleansstate on
> > > my image and I still get the same error.  I've also tried generating
> > > the eSDK for core-image-minimal and I have the same error.  I can
> > > generate the SDK successfully, just not the eSDK.  I have copied more
> > > of the build output below if it helps.  Note that I have replaced some
> > > text that I'm paranoid about publishing on the internet; the modified text is
> > enclosed with <>.
> > > 
> > > Does anyone have any insight as to why the eSDK build is failing?
> > 
> > Could you share what bitbake -e shows BBFILES as being set to? The variable
> > history from that command for the variable may also be helpful.
> > 
> > There has to be something different to how you're setting it compared to
> > what we test on the autobuilder.
> > 
> > Cheers,
> > 
> > Richard
> 
> Here's what I was able to pull from bitbake -e.  I've included details for
> both BBFILES and BBFILES_DYNAMIC.  Let me know if anything else would be
> helpful.

Thanks, I'm not seeing anything too odd there. I guess next we need to see the
bblayers.conf that the code is building into the eSDK and compare it to your
original conf/bblayer.conf.

The generated file should be in the eSDK image directory somewhere, I'm not able
to look up the exact path right now. Let me know if you can't find it. Lets see
if the two bblayers.conf files look different and introduce some issue.

Cheers,

Richard





^ permalink raw reply	[flat|nested] 6+ messages in thread
* RE: [yocto] Problems building eSDK: Exception: variable BBFILES references itself!
  2022-02-09 18:50     ` Richard Purdie
@ 2022-02-09 19:36       ` Bryan Evenson
       [not found]         ` <675b3c7015dc7d66bc4e0dac0d3e06796fbc7418.camel@linuxfoundation.org>
  0 siblings, 1 reply; 6+ messages in thread
From: Bryan Evenson @ 2022-02-09 19:36 UTC (permalink / raw)
  To: Richard Purdie, yocto

Richard,

> -----Original Message-----
> From: Richard Purdie <richard.purdie@linuxfoundation.org>
> Sent: Wednesday, February 9, 2022 1:51 PM
> To: Bryan Evenson <bevenson@melinkcorp.com>;
> yocto@lists.yoctoproject.org
> Subject: Re: [yocto] Problems building eSDK: Exception: variable BBFILES
> references itself!
> 
> On Wed, 2022-02-09 at 18:10 +0000, Bryan Evenson wrote:
> > Richard,
> >
> > > -----Original Message-----
> > > From: Richard Purdie <richard.purdie@linuxfoundation.org>
> > > Sent: Wednesday, February 9, 2022 12:25 PM
> > > To: Bryan Evenson <bevenson@melinkcorp.com>;
> > > yocto@lists.yoctoproject.org
> > > Subject: Re: [yocto] Problems building eSDK: Exception: variable
> > > BBFILES references itself!
> > >
> > > On Wed, 2022-02-09 at 16:51 +0000, Bryan Evenson wrote:
> > > > All,
> > > >
> > > > I've used the SDK in the past and want to start using the eSDK for
> > > > my
> > > project.
> > > > I'm on the dunfell branch.  I'm trying to build the eSDK for my
> > > > image by
> > > > calling:
> > > >
> > > > bitbake <my_image_name> -c populate_sdk_ext
> > > >
> > > > The sdk generation fails with the error in the subject.  I haven't
> > > > been able to find any documentation on what this means or how to
> > > > fix it.  I've tried deleting my tmp directory and running
> > > > cleansstate on my image and I still get the same error.  I've also
> > > > tried generating the eSDK for core-image-minimal and I have the
> > > > same error.  I can generate the SDK successfully, just not the
> > > > eSDK.  I have copied more of the build output below if it helps.
> > > > Note that I have replaced some text that I'm paranoid about
> > > > publishing on the internet; the modified text is
> > > enclosed with <>.
> > > >
> > > > Does anyone have any insight as to why the eSDK build is failing?
> > >
> > > Could you share what bitbake -e shows BBFILES as being set to? The
> > > variable history from that command for the variable may also be helpful.
> > >
> > > There has to be something different to how you're setting it
> > > compared to what we test on the autobuilder.
> > >
> > > Cheers,
> > >
> > > Richard
> >
> > Here's what I was able to pull from bitbake -e.  I've included details
> > for both BBFILES and BBFILES_DYNAMIC.  Let me know if anything else
> > would be helpful.
> 
> Thanks, I'm not seeing anything too odd there. I guess next we need to see
> the bblayers.conf that the code is building into the eSDK and compare it to
> your original conf/bblayer.conf.
> 
> The generated file should be in the eSDK image directory somewhere, I'm
> not able to look up the exact path right now. Let me know if you can't find it.
> Lets see if the two bblayers.conf files look different and introduce some
> issue.
> 

I think I found what you were looking for under the image tmp working directory at sdk-ext/image/temp-renamed-sdk/conf/bblayers.conf.  Here's a comparison of my original bblayers.conf in my tmp directory and the generated bblayers.conf for the eSDK.  I confirmed that the layers directory is present and contains all the layers as listed in the generated bblayers.conf.

#########################################################################
#
# Contents of my original bblayers.conf
#
#########################################################################
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
POKY_BBLAYERS_CONF_VERSION = "2"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
  <my_home_dir>/poky/<my_custom_layer1> \
  <my_home_dir>/poky/<my_custom_layer2> \
  <my_home_dir>/poky/meta-bacnet \
  <my_home_dir>/poky/meta-atmel \
  <my_home_dir>/poky/meta \
  <my_home_dir>/poky/meta-poky \
  <my_home_dir>/poky/meta-yocto-bsp \
  <my_home_dir>/poky/meta-openembedded/meta-oe \
  <my_home_dir>/poky/meta-openembedded/meta-networking \
  <my_home_dir>/poky/meta-openembedded/meta-python \
  <my_home_dir>/poky/poky-build/workspace \
  "
BBLAYERS_NON_REMOVABLE ?= " \
  <my_home_dir>/poky/meta \
  <my_home_dir>/poky/meta-poky \
  "

#########################################################################
#
# Contents of my <img_tmp_work_dir>/sdk-ext/image/tmp-renamed-sdk/conf/bblayers.conf
#
#########################################################################
# WARNING: this configuration has been automatically generated and in
# most cases should not be edited. If you need more flexibility than
# this configuration provides, it is strongly suggested that you set
# up a proper instance of the full build system and use that instead.

BBPATH = "${TOPDIR}"
SDKBASEMETAPATH = "${TOPDIR}"
BBLAYERS := " \
    ${SDKBASEMETAPATH}/layers/poky/<my_custom_layer1> \
    ${SDKBASEMETAPATH}/layers/poky/<my_custom_layer2> \
    ${SDKBASEMETAPATH}/layers/poky/meta-bacnet \
    ${SDKBASEMETAPATH}/layers/poky/meta-atmel \
    ${SDKBASEMETAPATH}/layers/poky/meta \
    ${SDKBASEMETAPATH}/layers/poky/meta-poky \
    ${SDKBASEMETAPATH}/layers/poky/meta-yocto-bsp \
    ${SDKBASEMETAPATH}/layers/poky/meta-openembedded/meta-oe \
    ${SDKBASEMETAPATH}/layers/poky/meta-openembedded/meta-networking \
    ${SDKBASEMETAPATH}/layers/poky/meta-openembedded/meta-python \
    ${SDKBASEMETAPATH}/workspace \
    "

Let me know if anything else would be helpful for diagnosing this issue.

Thanks,
Bryan

> Cheers,
> 
> Richard
> 
> 


^ permalink raw reply	[flat|nested] 6+ messages in thread
* RE: [yocto] Problems building eSDK: Exception: variable BBFILES references itself!
       [not found]         ` <675b3c7015dc7d66bc4e0dac0d3e06796fbc7418.camel@linuxfoundation.org>
@ 2022-02-09 20:19           ` Bryan Evenson
       [not found]             ` <687ce75a0c2ed354ae0fa399c7f450d528bb4d4a.camel@linuxfoundation.org>
  0 siblings, 1 reply; 6+ messages in thread
From: Bryan Evenson @ 2022-02-09 20:19 UTC (permalink / raw)
  To: Richard Purdie, yocto

Richard,

> -----Original Message-----
> From: Richard Purdie <richard.purdie@linuxfoundation.org>
> Sent: Wednesday, February 9, 2022 2:47 PM
> To: Bryan Evenson <bevenson@melinkcorp.com>;
> yocto@lists.yoctoproject.org
> Subject: Re: [yocto] Problems building eSDK: Exception: variable BBFILES
> references itself!
> 
> On Wed, 2022-02-09 at 19:36 +0000, Bryan Evenson wrote:
> > Richard,
> >
> > > -----Original Message-----
> > > From: Richard Purdie <richard.purdie@linuxfoundation.org>
> > > Sent: Wednesday, February 9, 2022 1:51 PM
> > > To: Bryan Evenson <bevenson@melinkcorp.com>;
> > > yocto@lists.yoctoproject.org
> > > Subject: Re: [yocto] Problems building eSDK: Exception: variable
> > > BBFILES references itself!
> > >
> > > On Wed, 2022-02-09 at 18:10 +0000, Bryan Evenson wrote:
> > > > Richard,
> > > >
> > > > > -----Original Message-----
> > > > > From: Richard Purdie <richard.purdie@linuxfoundation.org>
> > > > > Sent: Wednesday, February 9, 2022 12:25 PM
> > > > > To: Bryan Evenson <bevenson@melinkcorp.com>;
> > > > > yocto@lists.yoctoproject.org
> > > > > Subject: Re: [yocto] Problems building eSDK: Exception: variable
> > > > > BBFILES references itself!
> > > > >
> > > > > On Wed, 2022-02-09 at 16:51 +0000, Bryan Evenson wrote:
> > > > > > All,
> > > > > >
> > > > > > I've used the SDK in the past and want to start using the eSDK
> > > > > > for my
> > > > > project.
> > > > > > I'm on the dunfell branch.  I'm trying to build the eSDK for
> > > > > > my image by
> > > > > > calling:
> > > > > >
> > > > > > bitbake <my_image_name> -c populate_sdk_ext
> > > > > >
> > > > > > The sdk generation fails with the error in the subject.  I
> > > > > > haven't been able to find any documentation on what this means
> > > > > > or how to fix it.  I've tried deleting my tmp directory and
> > > > > > running cleansstate on my image and I still get the same
> > > > > > error.  I've also tried generating the eSDK for
> > > > > > core-image-minimal and I have the same error.  I can generate
> > > > > > the SDK successfully, just not the eSDK.  I have copied more of the
> build output below if it helps.
> > > > > > Note that I have replaced some text that I'm paranoid about
> > > > > > publishing on the internet; the modified text is
> > > > > enclosed with <>.
> > > > > >
> > > > > > Does anyone have any insight as to why the eSDK build is failing?
> > > > >
> > > > > Could you share what bitbake -e shows BBFILES as being set to?
> > > > > The variable history from that command for the variable may also be
> helpful.
> > > > >
> > > > > There has to be something different to how you're setting it
> > > > > compared to what we test on the autobuilder.
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Richard
> > > >
> > > > Here's what I was able to pull from bitbake -e.  I've included
> > > > details for both BBFILES and BBFILES_DYNAMIC.  Let me know if
> > > > anything else would be helpful.
> > >
> > > Thanks, I'm not seeing anything too odd there. I guess next we need
> > > to see the bblayers.conf that the code is building into the eSDK and
> > > compare it to your original conf/bblayer.conf.
> > >
> > > The generated file should be in the eSDK image directory somewhere,
> > > I'm not able to look up the exact path right now. Let me know if you can't
> find it.
> > > Lets see if the two bblayers.conf files look different and introduce
> > > some issue.
> > >
> >
> > I think I found what you were looking for under the image tmp working
> directory at sdk-ext/image/temp-renamed-sdk/conf/bblayers.conf.  Here's a
> comparison of my original bblayers.conf in my tmp directory and the
> generated bblayers.conf for the eSDK.  I confirmed that the layers directory
> is present and contains all the layers as listed in the generated bblayers.conf.
> >
> >
> ##########################################################
> ############
> > ###
> > #
> > # Contents of my original bblayers.conf #
> >
> ##########################################################
> ############
> > ### # LAYER_CONF_VERSION is increased each time
> > build/conf/bblayers.conf # changes incompatibly
> > POKY_BBLAYERS_CONF_VERSION = "2"
> >
> > BBPATH = "${TOPDIR}"
> > BBFILES ?= ""
> >
> > BBLAYERS ?= " \
> >   <my_home_dir>/poky/<my_custom_layer1> \
> >   <my_home_dir>/poky/<my_custom_layer2> \
> >   <my_home_dir>/poky/meta-bacnet \
> >   <my_home_dir>/poky/meta-atmel \
> >   <my_home_dir>/poky/meta \
> >   <my_home_dir>/poky/meta-poky \
> >   <my_home_dir>/poky/meta-yocto-bsp \
> >   <my_home_dir>/poky/meta-openembedded/meta-oe \
> >   <my_home_dir>/poky/meta-openembedded/meta-networking \
> >   <my_home_dir>/poky/meta-openembedded/meta-python \
> >   <my_home_dir>/poky/poky-build/workspace \
> >   "
> > BBLAYERS_NON_REMOVABLE ?= " \
> >   <my_home_dir>/poky/meta \
> >   <my_home_dir>/poky/meta-poky \
> >   "
> >
> >
> ##########################################################
> ############
> > ###
> > #
> > # Contents of my
> > <img_tmp_work_dir>/sdk-ext/image/tmp-renamed-
> sdk/conf/bblayers.conf
> > #
> >
> ##########################################################
> ############
> > ### # WARNING: this configuration has been automatically generated and
> > in # most cases should not be edited. If you need more flexibility
> > than # this configuration provides, it is strongly suggested that you
> > set # up a proper instance of the full build system and use that
> > instead.
> >
> > BBPATH = "${TOPDIR}"
> > SDKBASEMETAPATH = "${TOPDIR}"
> > BBLAYERS := " \
> >     ${SDKBASEMETAPATH}/layers/poky/<my_custom_layer1> \
> >     ${SDKBASEMETAPATH}/layers/poky/<my_custom_layer2> \
> >     ${SDKBASEMETAPATH}/layers/poky/meta-bacnet \
> >     ${SDKBASEMETAPATH}/layers/poky/meta-atmel \
> >     ${SDKBASEMETAPATH}/layers/poky/meta \
> >     ${SDKBASEMETAPATH}/layers/poky/meta-poky \
> >     ${SDKBASEMETAPATH}/layers/poky/meta-yocto-bsp \
> >     ${SDKBASEMETAPATH}/layers/poky/meta-openembedded/meta-oe \
> >     ${SDKBASEMETAPATH}/layers/poky/meta-openembedded/meta-
> networking \
> >     ${SDKBASEMETAPATH}/layers/poky/meta-openembedded/meta-
> python \
> >     ${SDKBASEMETAPATH}/workspace \
> >     "
> >
> > Let me know if anything else would be helpful for diagnosing this issue.
> 
> I'm now wondering what happens if you remove
> 
> <my_home_dir>/poky/poky-build/workspace \
> 
> since I suspect your local workspace probably doesn't make sense in the
> eSDK?
> Could you try temporarily removing that and see if that helps?
> 
> The BBFILES entry in one of these layer.conf files is probably causing some
> issue but I can't easily know which one. You could remove some of the other
> layers to try and see if you identify where the issue is from too?
> 

This is odd.  I removed the workspace from my local bblayers.conf.  I executed:
bitbake -c cleansstate image
bitbake  image
bitbake image -c populate_sdk_ext

I got the same error message as before.  Also, the bblayers.conf in the tmp-sdk-ext directory still contains the workspace directory in the BBLAYERS list.  I then switched and built core-image-minimal the same way, and I'm getting the same error.  I checked BBLAYERS in bitbake -e for core-image-minimal, and the workspace directory is not listed.  I don’t know how populate_sdk_ext is pulling the workspace directory into BBLAYERS.  Any ideas?

Thanks,
Bryan


^ permalink raw reply	[flat|nested] 6+ messages in thread
* RE: [yocto] Problems building eSDK: Exception: variable BBFILES references itself!
       [not found]             ` <687ce75a0c2ed354ae0fa399c7f450d528bb4d4a.camel@linuxfoundation.org>
@ 2022-02-10 12:49               ` Bryan Evenson
  0 siblings, 0 replies; 6+ messages in thread
From: Bryan Evenson @ 2022-02-10 12:49 UTC (permalink / raw)
  To: Richard Purdie, yocto

Richard,

> -----Original Message-----
> From: Richard Purdie <richard.purdie@linuxfoundation.org>
> Sent: Wednesday, February 9, 2022 3:59 PM
> To: Bryan Evenson <bevenson@melinkcorp.com>;
> yocto@lists.yoctoproject.org
> Subject: Re: [yocto] Problems building eSDK: Exception: variable BBFILES
> references itself!
> 
> On Wed, 2022-02-09 at 20:19 +0000, Bryan Evenson wrote:
> > Richard,
> >
> > > -----Original Message-----
> > > From: Richard Purdie <richard.purdie@linuxfoundation.org>
> > > Sent: Wednesday, February 9, 2022 2:47 PM
> > > To: Bryan Evenson <bevenson@melinkcorp.com>;
> > > yocto@lists.yoctoproject.org
> > > Subject: Re: [yocto] Problems building eSDK: Exception: variable
> > > BBFILES references itself!
> > >
> > > On Wed, 2022-02-09 at 19:36 +0000, Bryan Evenson wrote:
> > > > Richard,
> > > >
> > > > > -----Original Message-----
> > > > > From: Richard Purdie <richard.purdie@linuxfoundation.org>
> > > > > Sent: Wednesday, February 9, 2022 1:51 PM
> > > > > To: Bryan Evenson <bevenson@melinkcorp.com>;
> > > > > yocto@lists.yoctoproject.org
> > > > > Subject: Re: [yocto] Problems building eSDK: Exception: variable
> > > > > BBFILES references itself!
> > > > >
> > > > > On Wed, 2022-02-09 at 18:10 +0000, Bryan Evenson wrote:
> > > > > > Richard,
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Richard Purdie <richard.purdie@linuxfoundation.org>
> > > > > > > Sent: Wednesday, February 9, 2022 12:25 PM
> > > > > > > To: Bryan Evenson <bevenson@melinkcorp.com>;
> > > > > > > yocto@lists.yoctoproject.org
> > > > > > > Subject: Re: [yocto] Problems building eSDK: Exception:
> > > > > > > variable BBFILES references itself!
> > > > > > >
> > > > > > > On Wed, 2022-02-09 at 16:51 +0000, Bryan Evenson wrote:
> > > > > > > > All,
> > > > > > > >
> > > > > > > > I've used the SDK in the past and want to start using the
> > > > > > > > eSDK for my
> > > > > > > project.
> > > > > > > > I'm on the dunfell branch.  I'm trying to build the eSDK
> > > > > > > > for my image by
> > > > > > > > calling:
> > > > > > > >
> > > > > > > > bitbake <my_image_name> -c populate_sdk_ext
> > > > > > > >
> > > > > > > > The sdk generation fails with the error in the subject.  I
> > > > > > > > haven't been able to find any documentation on what this
> > > > > > > > means or how to fix it.  I've tried deleting my tmp
> > > > > > > > directory and running cleansstate on my image and I still
> > > > > > > > get the same error.  I've also tried generating the eSDK
> > > > > > > > for core-image-minimal and I have the same error.  I can
> > > > > > > > generate the SDK successfully, just not the eSDK.  I have
> > > > > > > > copied more of the
> > > build output below if it helps.
> > > > > > > > Note that I have replaced some text that I'm paranoid
> > > > > > > > about publishing on the internet; the modified text is
> > > > > > > enclosed with <>.
> > > > > > > >
> > > > > > > > Does anyone have any insight as to why the eSDK build is failing?
> > > > > > >
> > > > > > > Could you share what bitbake -e shows BBFILES as being set to?
> > > > > > > The variable history from that command for the variable may
> > > > > > > also be
> > > helpful.
> > > > > > >
> > > > > > > There has to be something different to how you're setting it
> > > > > > > compared to what we test on the autobuilder.
> > > > > > >
> > > > > > > Cheers,
> > > > > > >
> > > > > > > Richard
> > > > > >
> > > > > > Here's what I was able to pull from bitbake -e.  I've included
> > > > > > details for both BBFILES and BBFILES_DYNAMIC.  Let me know if
> > > > > > anything else would be helpful.
> > > > >
> > > > > Thanks, I'm not seeing anything too odd there. I guess next we
> > > > > need to see the bblayers.conf that the code is building into the
> > > > > eSDK and compare it to your original conf/bblayer.conf.
> > > > >
> > > > > The generated file should be in the eSDK image directory
> > > > > somewhere, I'm not able to look up the exact path right now. Let
> > > > > me know if you can't
> > > find it.
> > > > > Lets see if the two bblayers.conf files look different and
> > > > > introduce some issue.
> > > > >
> > > >
> > > > I think I found what you were looking for under the image tmp
> > > > working
> > > directory at sdk-ext/image/temp-renamed-sdk/conf/bblayers.conf.
> > > Here's a comparison of my original bblayers.conf in my tmp directory
> > > and the generated bblayers.conf for the eSDK.  I confirmed that the
> > > layers directory is present and contains all the layers as listed in the
> generated bblayers.conf.
> > > >
> > > >
> > >
> ##########################################################
> > > ############
> > > > ###
> > > > #
> > > > # Contents of my original bblayers.conf #
> > > >
> > >
> ##########################################################
> > > ############
> > > > ### # LAYER_CONF_VERSION is increased each time
> > > > build/conf/bblayers.conf # changes incompatibly
> > > > POKY_BBLAYERS_CONF_VERSION = "2"
> > > >
> > > > BBPATH = "${TOPDIR}"
> > > > BBFILES ?= ""
> > > >
> > > > BBLAYERS ?= " \
> > > >   <my_home_dir>/poky/<my_custom_layer1> \
> > > >   <my_home_dir>/poky/<my_custom_layer2> \
> > > >   <my_home_dir>/poky/meta-bacnet \
> > > >   <my_home_dir>/poky/meta-atmel \
> > > >   <my_home_dir>/poky/meta \
> > > >   <my_home_dir>/poky/meta-poky \
> > > >   <my_home_dir>/poky/meta-yocto-bsp \
> > > >   <my_home_dir>/poky/meta-openembedded/meta-oe \
> > > >   <my_home_dir>/poky/meta-openembedded/meta-networking \
> > > >   <my_home_dir>/poky/meta-openembedded/meta-python \
> > > >   <my_home_dir>/poky/poky-build/workspace \
> > > >   "
> > > > BBLAYERS_NON_REMOVABLE ?= " \
> > > >   <my_home_dir>/poky/meta \
> > > >   <my_home_dir>/poky/meta-poky \
> > > >   "
> > > >
> > > >
> > >
> ##########################################################
> > > ############
> > > > ###
> > > > #
> > > > # Contents of my
> > > > <img_tmp_work_dir>/sdk-ext/image/tmp-renamed-
> > > sdk/conf/bblayers.conf
> > > > #
> > > >
> > >
> ##########################################################
> > > ############
> > > > ### # WARNING: this configuration has been automatically generated
> > > > and in # most cases should not be edited. If you need more
> > > > flexibility than # this configuration provides, it is strongly
> > > > suggested that you set # up a proper instance of the full build
> > > > system and use that instead.
> > > >
> > > > BBPATH = "${TOPDIR}"
> > > > SDKBASEMETAPATH = "${TOPDIR}"
> > > > BBLAYERS := " \
> > > >     ${SDKBASEMETAPATH}/layers/poky/<my_custom_layer1> \
> > > >     ${SDKBASEMETAPATH}/layers/poky/<my_custom_layer2> \
> > > >     ${SDKBASEMETAPATH}/layers/poky/meta-bacnet \
> > > >     ${SDKBASEMETAPATH}/layers/poky/meta-atmel \
> > > >     ${SDKBASEMETAPATH}/layers/poky/meta \
> > > >     ${SDKBASEMETAPATH}/layers/poky/meta-poky \
> > > >     ${SDKBASEMETAPATH}/layers/poky/meta-yocto-bsp \
> > > >     ${SDKBASEMETAPATH}/layers/poky/meta-openembedded/meta-oe
> \
> > > >     ${SDKBASEMETAPATH}/layers/poky/meta-openembedded/meta-
> > > networking \
> > > >     ${SDKBASEMETAPATH}/layers/poky/meta-openembedded/meta-
> > > python \
> > > >     ${SDKBASEMETAPATH}/workspace \
> > > >     "
> > > >
> > > > Let me know if anything else would be helpful for diagnosing this issue.
> > >
> > > I'm now wondering what happens if you remove
> > >
> > > <my_home_dir>/poky/poky-build/workspace \
> > >
> > > since I suspect your local workspace probably doesn't make sense in
> > > the eSDK?
> > > Could you try temporarily removing that and see if that helps?
> > >
> > > The BBFILES entry in one of these layer.conf files is probably
> > > causing some issue but I can't easily know which one. You could
> > > remove some of the other layers to try and see if you identify where the
> issue is from too?
> > >
> >
> > This is odd.  I removed the workspace from my local bblayers.conf.  I
> executed:
> > bitbake -c cleansstate image
> > bitbake  image
> > bitbake image -c populate_sdk_ext
> >
> > I got the same error message as before.  Also, the bblayers.conf in
> > the tmp- sdk-ext directory still contains the workspace directory in the
> BBLAYERS list.
> > I then switched and built core-image-minimal the same way, and I'm
> > getting the same error.  I checked BBLAYERS in bitbake -e for
> > core-image-minimal, and the workspace directory is not listed.  I
> > don’t know how populate_sdk_ext is pulling the workspace directory into
> BBLAYERS.  Any ideas?
> 
> I suspect the eSDK adds a workspace for the devtool and similar workflows
> so that piece may be normal and perhaps it was conflicting with your existing
> workspace? I have to admit I don't remember if it does that or not offhand
> but it could.
> 
> If that were the case, it is sounding like the conflict may be with some other
> layer instead.
> 
> Cheers,
> 
> Richard

I found it.  In one of my layers, instead of:

BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"

I had:

BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
       ${LAYERDIR}/recipes-*/*/*.bbappend"

I know I looked at that line a few times in the last day and never noticed the problem.  This has been like this on my layer for a long time.  Not sure how this has built without issue for the last eight years.  Thanks for the assistance.

Thanks,
Bryan

^ permalink raw reply	[flat|nested] 6+ messages in thread
end of thread, other threads:[~2022-02-10 12:49 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-09 16:51 Problems building eSDK: Exception: variable BBFILES references itself! Bryan Evenson
     [not found] ` <650b02092ecfc1579ac9f2763e4c3fc70e54601a.camel@linuxfoundation.org>
2022-02-09 18:10   ` [yocto] " Bryan Evenson
2022-02-09 18:50     ` Richard Purdie
2022-02-09 19:36       ` Bryan Evenson
     [not found]         ` <675b3c7015dc7d66bc4e0dac0d3e06796fbc7418.camel@linuxfoundation.org>
2022-02-09 20:19           ` Bryan Evenson
     [not found]             ` <687ce75a0c2ed354ae0fa399c7f450d528bb4d4a.camel@linuxfoundation.org>
2022-02-10 12:49               ` Bryan Evenson

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.