Can we then keep meta-agl for LTS and master only ? as it seems that’s what it
is going to support

Hello

IIRC you can prepare configuration for Zeus and run build, lots of things probable will need to be rebuild

as there will be in different versions but if only U-Boot is a problem then maybe you could stay on Hardknott

version and only change the U-Boot version? Could you please share some more information about your build?

Which layers are you using? Do you have some custom layer?

Greetings

--

Tomasz Żyjewski
Embedded Systems Engineer
GPG: 5C495EA3EBEECA59
https://3mdeb.com | @3mdeb_com

Hello everyone,

Say I built Yocto for the latest build for instance Hardknott. Let’s say I need to build for Zeus instead (and hopefully keep everything I built [that doesn’t need to be updated]).

Has anyone done this?

Outside of building a whole new Yocto distribution from scratch… What else can I do?

I have to rebuild Yocto with an older version because apparently there is some issue with Uboot that is not able to be built correctly.

On 10. Feb 2022, at 10:29, rayaan@... wrote:
I am new to yocto and in need of assistance please.

Could someone please assist me with getting DKMS included in my build.

my platform is: stm32mp1

On 2/9/2022 1:41 PM, Richard Purdie wrote:

There are lots of levels it could be implemented at but it is something someone
would need to pick up and drive forward with a long term view to helping with
issues etc.

What would be the minimum acceptable solution with the least investment?
in other words, do we have a list of requirements?

You're after our LTS to maintain ABI. In order to do that we need help, not just
with patches generating some output, but in day to day running of the project,
i.e. help comparing output before and after changes. Whenever a patch is
submitted which breaks this, it will need attention and help some someone to
explain to that submitter what the issue, why it is important and hints on how
to fix it.

That's true, this will require engagement from the community. Tool could
take few iterations to perfect. Until then, I expect tool owner to be
responsible for fixing these bugs. Once stability is reached, it becomes
community maintained.

If the tool owner doesn't maintain and community has no interest, tool
dies and gets reverted. It is as simple as any open source engagement.

When stability is established, each code contributor to LTS would be
subject to addressing issues found before they get merged.

The idea of "least investment" sends shivers down my spine since it sounds like
you want to do the absolute bare minimum to have this happen, rather than a more
community oriented approach.

It depends on your taste. I believe in smaller improvements
as opposed to throwing a big project to you that no-one will use it.

Everyone has different needs. We need to find the common ones.
That's why, I'm asking if there is an existing tool that works for
large part of the community accepting that there will be some folks
that won't have their needs addressed.

I'm interested in revisiting the tooling discussion and have these gaps
addressed for the biggest audience so that we can have something to
build upon.

Anyway, my point is there is more to this than just a patch. We have various
kinds of build output already and reports on test regressions - nobody helps
with them. I need some kind of a sign that ABI would be different and there are
people able to help with review on an ongoing basis, else it will just be
something else I and a small number of others become overloaded with.

Noted. Hopefully, things will be not that volatile for the LTS branch
and tool would actually help the maintainer.

In an ideal world, change needs to be stopped before that happens and
have the patch author address it similar to how you monitor build
pipelines.

Our team has posted a solution. BMW folks posted a solution.
None of them got merged.

Can you remind me of your team's please?

https://lists.yoctoproject.org/g/yocto/topic/85279259?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,160,85279259

This was an intern project from last summer that we are interested
in expanding coverage.

I have to admit I can't remember what the conclusion was on your team's version
but if you remind me of the patches I can try and remember. This is a bigger
problem than just patches though sadly.

Sure, let's find out what everyone is doing.

Richard,

-----Original Message-----
From: Richard Purdie <richard.purdie@...>
Sent: Wednesday, February 9, 2022 2:47 PM
To: Bryan Evenson <bevenson@...>;
yocto@...
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@...>
Sent: Wednesday, February 9, 2022 1:51 PM
To: Bryan Evenson <bevenson@...>;
yocto@...
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@...>
Sent: Wednesday, February 9, 2022 12:25 PM
To: Bryan Evenson <bevenson@...>;
yocto@...
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?

Richard,

-----Original Message-----
From: Richard Purdie <richard.purdie@...>
Sent: Wednesday, February 9, 2022 1:51 PM
To: Bryan Evenson <bevenson@...>;
yocto@...
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@...>
Sent: Wednesday, February 9, 2022 12:25 PM
To: Bryan Evenson <bevenson@...>;
yocto@...
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.

The BMW one is about hash equivalence so wouldn't help your ABI output problem
with the LTS. From what I remember, it predates hash equivalence and the project
needed a generic equivalance mechanism complete with server done at the runqueue
level in bitbake. This has now happened so we could revisit the idea of what is
in that layer but translating it to a hash equivalence plugin.

I'd also add that even with hash equivalence done well like we ended up with, we
have only two people interested/able to work on bugs with it, the author and
myself. For a key component of the system, this worries me a lot. Adding more
complexity without maintainer support isn't going to help anyone.

There are lots of levels it could be implemented at but it is something someone
would need to pick up and drive forward with a long term view to helping with
issues etc.

What would be the minimum acceptable solution with the least investment?
in other words, do we have a list of requirements?

You're after our LTS to maintain ABI. In order to do that we need help, not just
with patches generating some output, but in day to day running of the project,
i.e. help comparing output before and after changes. Whenever a patch is
submitted which breaks this, it will need attention and help some someone to
explain to that submitter what the issue, why it is important and hints on how
to fix it.

The idea of "least investment" sends shivers down my spine since it sounds like
you want to do the absolute bare minimum to have this happen, rather than a more
community oriented approach.

Anyway, my point is there is more to this than just a patch. We have various
kinds of build output already and reports on test regressions - nobody helps
with them. I need some kind of a sign that ABI would be different and there are
people able to help with review on an ongoing basis, else it will just be
something else I and a small number of others become overloaded with.

Our team has posted a solution. BMW folks posted a solution.
None of them got merged.

Can you remind me of your team's please?

The BMW one is about hash equivalence so wouldn't help your ABI output problem
with the LTS. From what I remember, it predates hash equivalence and the project
needed a generic equivalance mechanism complete with server done at the runqueue
level in bitbake. This has now happened so we could revisit the idea of what is
in that layer but translating it to a hash equivalence plugin.
I'd also add that even with hash equivalence done well like we ended up with, we
have only two people interested/able to work on bugs with it, the author and
myself. For a key component of the system, this worries me a lot. Adding more
complexity without maintainer support isn't going to help anyone.

Could we take the version from BMW folks, merge and have the next person
add new features where it doesn't satisfy requirements?

See above on the BMW version. I'm a little worried you're suggesting merging
something which doesn't actually do what you need/want:(.

or vice versa? or as Ross said some other work?
or none of the solutions are acceptable?

I have to admit I can't remember what the conclusion was on your team's version
but if you remind me of the patches I can try and remember. This is a bigger
problem than just patches though sadly.

Richard,

-----Original Message-----
From: Richard Purdie <richard.purdie@...>
Sent: Wednesday, February 9, 2022 12:25 PM
To: Bryan Evenson <bevenson@...>;
yocto@...
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.