On Tue, 2021-05-25 at 12:13 +0000, Peter Kjellerstedt wrote:

It seems the ”hardknott-25.0.1” tag is missing for meta-gplv2. 
The “yoccto-3.3.1” tag is present.

This was deliberate since we've been trying to step away from the 
"poky" version numbers, I'm not sure they add much to anything.

Is there a particular reason you were looking for those?

Cheers,

Richard

Adding Richard and Guillaume.

Op 24-05-2021 om 14:39 schreef Ferry Toth:

I just tried with other versions of Ubuntu: with 18.04.5 and 20.10,
they have the same issue as 20.04.2.
With 21.04, it can't compile pseudo_git.bb, I believe it's because of
the new version of GCC.

How can it work perfectly with Debian but not Ubuntu?

Le mar. 18 mai 2021 à 22:49, Aymeric Dumaz via lists.yoctoproject.org
<aymericdumaz=gmail.com@...> a écrit :

Hello,

I have created a recipe to call multiple makefile and set a variable
if it's not defined inside them, meaning I set it before "oe_runmake".
It works as expected on a Debian testing, but with a Ubuntu base
chroot it does not.

I have written a simple recipe and the steps I used to configure the
Ubuntu chroot; on Debian I can see "var -bar-" inside log.do_compile,
but on Ubuntu it will only be "var --".
I'm not sure where the bug is located; I'm using Dunfell but I always
thought the host running Yocto was not relevant during the
compilation.
Thanks.

### Ubuntu chroot: download the image [0], extract it and start the
chroot, update it [1], add the en_US.UTF-8 locale [2], install Yocto
dependencies [3], then add an user.

### testvar.bb
SRC_URI = "file://Makefile"
LICENSE = "CLOSED"
S = "${WORKDIR}"

do_compile() {
FOO=bar oe_runmake
}

### Makefile
all:
@echo "var -$(FOO)-"

clean:


[0] http://cdimage.ubuntu.com/ubuntu-base/releases/20.04/release/ubuntu-base-20.04.2-base-amd64.tar.gz
[1] apt update && apt upgrade
[2] apt install locales && dpkg-reconfigure locales - select "159" then "3"
[3] apt install python3 python3-distutils binutils chrpath cpio cpp
diffstat g++ gawk gcc git make patch wget xxd

Hello,

gstreamer1.0-plugins-bad-1.16.3-r0 do_configure fails with the error: 

    gstreamer1.0-dev
    gstreamer1.0 \

Error log:
Exception: TypeError: __init__() got an unexpected keyword argument 'testimage_dump_monitor'

Ref:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=3acbec85b00d693d2d731bc2b09cc40be1cc68e9

Signed-off-by: Naveen Saini <naveen.kumar.saini@...>
---
lib/oeqa/controllers/zephyrtargetcontrol.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/oeqa/controllers/zephyrtargetcontrol.py b/lib/oeqa/controllers/zephyrtargetcontrol.py
index 1dd7fd2..d342314 100644
--- a/lib/oeqa/controllers/zephyrtargetcontrol.py
+++ b/lib/oeqa/controllers/zephyrtargetcontrol.py
@@ -15,7 +15,7 @@ class QemuTargetZephyr(OETarget):
machine='', rootfs='', tmpdir ='',dir_image ='',display=None,
kernel='',boottime=60,bootlog='',kvm=False,slirp=False,
dump_dir='',serial_ports=0,ovmf=None,tmpfsdir='' ,target_modules_path='',powercontrol_cmd='',powercontrol_extra_args='',
- serialcontrol_cmd=None,serialcontrol_extra_args='',testimage_dump_target=''):
+ serialcontrol_cmd=None,serialcontrol_extra_args='',testimage_dump_target='',testimage_dump_monitor=''):

timeout = 300
user = 'root'
--
2.17.1

IIRC, dhcp-server has been replaced by kea, check on that side maybe.
Read the migration notes, pretty sure the kea thing is listed there.

Done. All fixed according to Quentin's recommendations.

https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/yocto-setup.sh#L114
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-gatesgarth/local.conf#L18
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-gatesgarth/local.conf_kernel#L26

Added to README.md .
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/README.md

Thank you,
Zoran
_______

On Mon, May 24, 2021 at 9:27 PM Quentin Schulz <foss@...> wrote:

On May 24, 2021 2:13:57 PM UTC, Zoran <zoran.stojsavljevic@...> wrote:

Or, maybe, now the DHCP is included in the releases by default?

Thank you,
Zoran
_______

On Mon, May 24, 2021 at 4:09 PM Zoran Stojsavljevic
<zoran.stojsavljevic@...> wrote:

Hello Quentin,

Thank you for finding the bug. It was in front of my eyes (I print all
the layers at the end of setup, but I missed to compare bb-layers from
dunfell with bb-layers from gatesgarth).

I should do better. With regards to testing thinking. ;-)
_______

Now, there are other bugs (I should say, new features introduced).

Loading cache: 100%
|################################################################################################|
Time: 0:00:00
Loaded 3533 entries from dependency cache.
Parsing recipes: 100%
|##############################################################################################|
Time: 0:00:00
Parsing of 2311 .bb files complete (2309 cached, 2 parsed). 3535
targets, 121 skipped, 1 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'dhcp-libs' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-libs' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-libs']
ERROR: Nothing RPROVIDES 'dhcp-server' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-server' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-server']
ERROR: Nothing RPROVIDES 'dhcp-server-config' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-server-config' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-server-config']
ERROR: Nothing RPROVIDES 'dhcp-client' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-client' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-client']
ERROR: Nothing RPROVIDES 'dhcp-relay' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-relay' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-relay']
ERROR: Nothing RPROVIDES 'dhcp-omshell' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-omshell' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-omshell']

Seems that this line in local.conf got severely changed, or most
likely the DHCP package version/handling got changed:

CORE_IMAGE_EXTRA_INSTALL_append = "openssh dhcp-libs dhcp-server
dhcp-server-config dhcp-client dhcp-relay dhcp-omshell cmake
libsocketcan nfs-utils rt-tests strace procps
packagegroup-core-buildessential "

The question is: what should I include in the
CORE_IMAGE_EXTRA_INSTALL_append for the DHCP package for gatesgarth
and later releases???

If I remember correctly, dhcp-server has been replaced by kea, check on that side maybe. Read the migration notes, pretty sure the kea thing is listed there.

Cheers,
Quentin

Thank you,
Zoran
_______

On Mon, May 24, 2021 at 2:24 PM Quentin Schulz <foss@...> wrote:

Hi Zoran,

On May 24, 2021 8:27:58 AM UTC, Zoran <zoran.stojsavljevic@...> wrote:

Hello again to YOCTO Folks,

Here is another blunder I ran into while fixing a yocto-setup.sh script:
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/yocto-setup.sh

While executing $ . ./yocto-setup.sh dunfell, everything ran smoothly.

I did the same routine with the $ . ./yocto-setup.sh gatesgarth, and
approximately after:
Parsing recipes: 9% |##########

The following message pops up!
Loading cache: 100% |
| ETA: --:--:--
Loaded 0 entries from dependency cache.
ERROR: ParseError at
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4:
Could not include required file images/basic-dev-image.bb

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

The layer is not included. Check in your bblayers.conf. see https://github.com/ZoranStojsavljevic/bbb-yocto/blob/a6e8e8ce491705816d02df58fa0ef9378b18ef83/yocto-setup.sh#L114 where you are missing the gatesgarth check.

Cheers,
Quentin

If you peek into the following github repos:
https://github.com/jumpnow/meta-bbb
https://github.com/jumpnow/meta-jumpnow

You'll see that in later images/basic-dev-image.bb does exist, as
well as in the dunfell branch:
https://github.com/jumpnow/meta-jumpnow/blob/zeus/images/basic-dev-image.bb

As well as in gatesgarth branch:
https://github.com/jumpnow/meta-jumpnow/blob/gatesgarth/images/basic-dev-image.bb

What I see upon the logic, something changes in poky/ setup, while
transitioning from dunfell to gatesgarth.

I also have created an issue in bbb-yocto repo:
https://github.com/ZoranStojsavljevic/bbb-yocto/issues/3

I would appreciate any ideas or hints... Maybe some changes required
in local.conf ?

You can all try it yourselves, and see the same!

Thank you,
Zoran
_______

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

On May 24, 2021 2:13:57 PM UTC, Zoran <zoran.stojsavljevic@...> wrote:

Or, maybe, now the DHCP is included in the releases by default?

Thank you,
Zoran
_______

On Mon, May 24, 2021 at 4:09 PM Zoran Stojsavljevic
<zoran.stojsavljevic@...> wrote:

Hello Quentin,

Thank you for finding the bug. It was in front of my eyes (I print all
the layers at the end of setup, but I missed to compare bb-layers from
dunfell with bb-layers from gatesgarth).

I should do better. With regards to testing thinking. ;-)
_______

Now, there are other bugs (I should say, new features introduced).

Loading cache: 100%
|################################################################################################|
Time: 0:00:00
Loaded 3533 entries from dependency cache.
Parsing recipes: 100%
|##############################################################################################|
Time: 0:00:00
Parsing of 2311 .bb files complete (2309 cached, 2 parsed). 3535
targets, 121 skipped, 1 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'dhcp-libs' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-libs' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-libs']
ERROR: Nothing RPROVIDES 'dhcp-server' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-server' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-server']
ERROR: Nothing RPROVIDES 'dhcp-server-config' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-server-config' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-server-config']
ERROR: Nothing RPROVIDES 'dhcp-client' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-client' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-client']
ERROR: Nothing RPROVIDES 'dhcp-relay' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-relay' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-relay']
ERROR: Nothing RPROVIDES 'dhcp-omshell' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-omshell' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-omshell']

Seems that this line in local.conf got severely changed, or most
likely the DHCP package version/handling got changed:

CORE_IMAGE_EXTRA_INSTALL_append = "openssh dhcp-libs dhcp-server
dhcp-server-config dhcp-client dhcp-relay dhcp-omshell cmake
libsocketcan nfs-utils rt-tests strace procps
packagegroup-core-buildessential "

The question is: what should I include in the
CORE_IMAGE_EXTRA_INSTALL_append for the DHCP package for gatesgarth
and later releases???

If I remember correctly, dhcp-server has been replaced by kea, check on that side maybe. Read the migration notes, pretty sure the kea thing is listed there.

Cheers,
Quentin

Thank you,
Zoran
_______

On Mon, May 24, 2021 at 2:24 PM Quentin Schulz <foss@...> wrote:

Hi Zoran,

On May 24, 2021 8:27:58 AM UTC, Zoran <zoran.stojsavljevic@...> wrote:

Hello again to YOCTO Folks,

Here is another blunder I ran into while fixing a yocto-setup.sh script:
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/yocto-setup.sh

While executing $ . ./yocto-setup.sh dunfell, everything ran smoothly.

I did the same routine with the $ . ./yocto-setup.sh gatesgarth, and
approximately after:
Parsing recipes: 9% |##########

The following message pops up!
Loading cache: 100% |
| ETA: --:--:--
Loaded 0 entries from dependency cache.
ERROR: ParseError at
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4:
Could not include required file images/basic-dev-image.bb

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

The layer is not included. Check in your bblayers.conf. see https://github.com/ZoranStojsavljevic/bbb-yocto/blob/a6e8e8ce491705816d02df58fa0ef9378b18ef83/yocto-setup.sh#L114 where you are missing the gatesgarth check.

Cheers,
Quentin

If you peek into the following github repos:
https://github.com/jumpnow/meta-bbb
https://github.com/jumpnow/meta-jumpnow

You'll see that in later images/basic-dev-image.bb does exist, as
well as in the dunfell branch:
https://github.com/jumpnow/meta-jumpnow/blob/zeus/images/basic-dev-image.bb

As well as in gatesgarth branch:
https://github.com/jumpnow/meta-jumpnow/blob/gatesgarth/images/basic-dev-image.bb

What I see upon the logic, something changes in poky/ setup, while
transitioning from dunfell to gatesgarth.

I also have created an issue in bbb-yocto repo:
https://github.com/ZoranStojsavljevic/bbb-yocto/issues/3

I would appreciate any ideas or hints... Maybe some changes required
in local.conf ?

You can all try it yourselves, and see the same!

Thank you,
Zoran
_______

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

On 5/24/21 12:37 AM, Juergen Landwehr wrote:

Hi all,
I am developing a C++ library that is using gRPC.
To be able to use protoc for generating the stubs I added the following dependencies:
DEPENDS += "\
grpc-native \
protobuf-native \
...
"
and to link my library with cross-compiled libraries:
RDEPENDS += "\
   grpc \
   protobuf \
   ...
   "
However, linking the library fails with the following error:
ld: /data/jenkins/workspace/e0_mbient_yocto_mbient_manifests_master_downstream/build/tmp/work/cortexa72-mbient-linux/tokenmaster-client/git-r0/recipe-sysroot-native/usr/lib/libgrpc++.so.1.24.3: error adding symbols: file in wrong format
I guess the problem is, that native grpc++ library is used from the "recipe-sysroot-native" directory and thus not the cross-compiled version.
What am I doing wrong? How can I tell Yocto to use the cross-compiled versions?

this is upto your component's build system, so perhaps you should look into that and ensure that its using right options. Second place to look is recipe for your package and ensure right vars and options are passed to build. you might want to look at sysdig package build system and see how they are doing it and perhaps mimic that for your package too.

Thanks,
Jürgen

Or, maybe, now the DHCP is included in the releases by default?

Thank you,
Zoran
_______

On Mon, May 24, 2021 at 4:09 PM Zoran Stojsavljevic
<zoran.stojsavljevic@...> wrote:

Hello Quentin,

Thank you for finding the bug. It was in front of my eyes (I print all
the layers at the end of setup, but I missed to compare bb-layers from
dunfell with bb-layers from gatesgarth).

I should do better. With regards to testing thinking. ;-)
_______

Now, there are other bugs (I should say, new features introduced).

Loading cache: 100%
|################################################################################################|
Time: 0:00:00
Loaded 3533 entries from dependency cache.
Parsing recipes: 100%
|##############################################################################################|
Time: 0:00:00
Parsing of 2311 .bb files complete (2309 cached, 2 parsed). 3535
targets, 121 skipped, 1 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'dhcp-libs' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-libs' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-libs']
ERROR: Nothing RPROVIDES 'dhcp-server' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-server' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-server']
ERROR: Nothing RPROVIDES 'dhcp-server-config' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-server-config' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-server-config']
ERROR: Nothing RPROVIDES 'dhcp-client' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-client' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-client']
ERROR: Nothing RPROVIDES 'dhcp-relay' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-relay' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-relay']
ERROR: Nothing RPROVIDES 'dhcp-omshell' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-omshell' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-omshell']

Seems that this line in local.conf got severely changed, or most
likely the DHCP package version/handling got changed:

CORE_IMAGE_EXTRA_INSTALL_append = "openssh dhcp-libs dhcp-server
dhcp-server-config dhcp-client dhcp-relay dhcp-omshell cmake
libsocketcan nfs-utils rt-tests strace procps
packagegroup-core-buildessential "

The question is: what should I include in the
CORE_IMAGE_EXTRA_INSTALL_append for the DHCP package for gatesgarth
and later releases???

Thank you,
Zoran
_______

On Mon, May 24, 2021 at 2:24 PM Quentin Schulz <foss@...> wrote:

Hi Zoran,

On May 24, 2021 8:27:58 AM UTC, Zoran <zoran.stojsavljevic@...> wrote:

Hello again to YOCTO Folks,

Here is another blunder I ran into while fixing a yocto-setup.sh script:
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/yocto-setup.sh

While executing $ . ./yocto-setup.sh dunfell, everything ran smoothly.

I did the same routine with the $ . ./yocto-setup.sh gatesgarth, and
approximately after:
Parsing recipes: 9% |##########

The following message pops up!
Loading cache: 100% |
| ETA: --:--:--
Loaded 0 entries from dependency cache.
ERROR: ParseError at
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4:
Could not include required file images/basic-dev-image.bb

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

The layer is not included. Check in your bblayers.conf. see https://github.com/ZoranStojsavljevic/bbb-yocto/blob/a6e8e8ce491705816d02df58fa0ef9378b18ef83/yocto-setup.sh#L114 where you are missing the gatesgarth check.

Cheers,
Quentin

If you peek into the following github repos:
https://github.com/jumpnow/meta-bbb
https://github.com/jumpnow/meta-jumpnow

You'll see that in later images/basic-dev-image.bb does exist, as
well as in the dunfell branch:
https://github.com/jumpnow/meta-jumpnow/blob/zeus/images/basic-dev-image.bb

As well as in gatesgarth branch:
https://github.com/jumpnow/meta-jumpnow/blob/gatesgarth/images/basic-dev-image.bb

What I see upon the logic, something changes in poky/ setup, while
transitioning from dunfell to gatesgarth.

I also have created an issue in bbb-yocto repo:
https://github.com/ZoranStojsavljevic/bbb-yocto/issues/3

I would appreciate any ideas or hints... Maybe some changes required
in local.conf ?

You can all try it yourselves, and see the same!

Thank you,
Zoran
_______

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Hello Quentin,

Thank you for finding the bug. It was in front of my eyes (I print all
the layers at the end of setup, but I missed to compare bb-layers from
dunfell with bb-layers from gatesgarth).

I should do better. With regards to testing thinking. ;-)
_______

Now, there are other bugs (I should say, new features introduced).

Loading cache: 100%
|################################################################################################|
Time: 0:00:00
Loaded 3533 entries from dependency cache.
Parsing recipes: 100%
|##############################################################################################|
Time: 0:00:00
Parsing of 2311 .bb files complete (2309 cached, 2 parsed). 3535
targets, 121 skipped, 1 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'dhcp-libs' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-libs' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-libs']
ERROR: Nothing RPROVIDES 'dhcp-server' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-server' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-server']
ERROR: Nothing RPROVIDES 'dhcp-server-config' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-server-config' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-server-config']
ERROR: Nothing RPROVIDES 'dhcp-client' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-client' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-client']
ERROR: Nothing RPROVIDES 'dhcp-relay' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-relay' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-relay']
ERROR: Nothing RPROVIDES 'dhcp-omshell' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-omshell' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-omshell']

Seems that this line in local.conf got severely changed, or most
likely the DHCP package version/handling got changed:

CORE_IMAGE_EXTRA_INSTALL_append = "openssh dhcp-libs dhcp-server
dhcp-server-config dhcp-client dhcp-relay dhcp-omshell cmake
libsocketcan nfs-utils rt-tests strace procps
packagegroup-core-buildessential "

The question is: what should I include in the
CORE_IMAGE_EXTRA_INSTALL_append for the DHCP package for gatesgarth
and later releases???

Thank you,
Zoran
_______

Wow, that got messed up, let me retry.

Op 24-05-2021 om 14:19 schreef Ferry Toth:

Accidentally I refreshed poky and rebuilt. The image-live (do_bootimg) fails when building hddimg with the following:

ERROR: edison-image-1.0-r0 do_bootimg: Error executing a python function in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: <module>
     0001:
 *** 0002:do_bootimg(d)
     0003:
File: '/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/poky/meta/classes/image-live.bbclass', lineno: 258, function: do_bootimg
     0254:    if d.getVar("PCBIOS") == "1":
     0255:        bb.build.exec_func('build_syslinux_cfg', d)
     0256:    if d.getVar("EFI") == "1":
     0257:        bb.build.exec_func('build_efi_cfg', d)
 *** 0258:    bb.build.exec_func('build_hddimg', d)
     0259:    bb.build.exec_func('build_iso', d)
     0260:    bb.build.exec_func('create_symlinks', d)
     0261:}
     0262:do_bootimg[subimages] = "hddimg iso"
File: '/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/poky/bitbake/lib/bb/build.py', lineno: 256, function: exec_func
     0252:    with bb.utils.fileslocked(lockfiles):
     0253:        if ispython:
     0254:            exec_func_python(func, d, runfile, cwd=adir)
     0255:        else:
 *** 0256:            exec_func_shell(func, d, runfile, cwd=adir)
     0257:
     0258:    try:
     0259:        curcwd = os.getcwd()
     0260:    except:
File: '/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/poky/bitbake/lib/bb/build.py', lineno: 503, function: exec_func_shell
     0499:    with open(fifopath, 'r+b', buffering=0) as fifo:
     0500:        try:
     0501:            bb.debug(2, "Executing shell function %s" % func)
     0502:            with open(os.devnull, 'r+') as stdin, logfile:
 *** 0503:                bb.process.run(cmd, shell=False, stdin=stdin, log=logfile, extrafiles=[(fifo,readfifo)])
     0504:        except bb.process.ExecutionError as exe:
     0505:            # Find the backtrace that the shell trap generated
     0506:            backtrace_marker_regex = re.compile(r"WARNING: Backtrace \(BB generated script\)")
     0507:            stdout_lines = (exe.stdout or "").split("\n")
File: '/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/poky/bitbake/lib/bb/process.py', lineno: 184, function: run
     0180:        if not stderr is None:
     0181:            stderr = stderr.decode("utf-8")
     0182:
     0183:    if pipe.returncode != 0:
 *** 0184:        raise ExecutionError(cmd, pipe.returncode, stdout, stderr)
     0185:    return stdout, stderr
Exception: bb.process.ExecutionError: Execution of '/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/build/tmp/work/edison-poky-linux/edison-image/1.0-r0/temp/run.build_hddimg.256530' failed with exit code 1:
mkdosfs: unable to create /home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/build/tmp/work/edison-poky-linux/edison-image/1.0-r0/deploy-edison-image-image-complete/edison-image-edison-20210524113748.hddimg
mkfs.fat 4.1 (2017-01-24)
WARNING: exit code 1 from a shell command.

The reason is that the directory deploy-edison-image-image-complete doesn't exist at the time mkdosfs want to write. However after completing the remainder of image live the directory does exists. Consequently, running bitbake a second time image-live succeeds.

I've tried various thing including expressly creating the directory before mkdosfs, but nothing worked. It seems I don't understand how it is supposed to work in the first place.

However, I managed to trace back the issue to this commit 91e4a1c1 "image-live.bbclass: optional depends when ROOTFS empty".

Reverting this resolves the issue.

Any idea what could be wrong?

Hi Zoran,

On May 24, 2021 8:27:58 AM UTC, Zoran <zoran.stojsavljevic@...> wrote:

Hello again to YOCTO Folks,

Here is another blunder I ran into while fixing a yocto-setup.sh script:
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/yocto-setup.sh

While executing $ . ./yocto-setup.sh dunfell, everything ran smoothly.

I did the same routine with the $ . ./yocto-setup.sh gatesgarth, and
approximately after:
Parsing recipes: 9% |##########

The following message pops up!
Loading cache: 100% |
| ETA: --:--:--
Loaded 0 entries from dependency cache.
ERROR: ParseError at
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4:
Could not include required file images/basic-dev-image.bb

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

The layer is not included. Check in your bblayers.conf. see https://github.com/ZoranStojsavljevic/bbb-yocto/blob/a6e8e8ce491705816d02df58fa0ef9378b18ef83/yocto-setup.sh#L114 where you are missing the gatesgarth check.

Cheers,
Quentin

If you peek into the following github repos:
https://github.com/jumpnow/meta-bbb
https://github.com/jumpnow/meta-jumpnow

You'll see that in later images/basic-dev-image.bb does exist, as
well as in the dunfell branch:
https://github.com/jumpnow/meta-jumpnow/blob/zeus/images/basic-dev-image.bb

As well as in gatesgarth branch:
https://github.com/jumpnow/meta-jumpnow/blob/gatesgarth/images/basic-dev-image.bb

What I see upon the logic, something changes in poky/ setup, while
transitioning from dunfell to gatesgarth.

I also have created an issue in bbb-yocto repo:
https://github.com/ZoranStojsavljevic/bbb-yocto/issues/3

I would appreciate any ideas or hints... Maybe some changes required
in local.conf ?

You can all try it yourselves, and see the same!

Thank you,
Zoran
_______

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Accidentally I refreshed poky and rebuilt. The image-live (do_bootimg) fails when building hddimg with the following:

ERROR: edison-image-1.0-r0 do_bootimg: Error executing a python function in exec_python_func() autogenerated: The stack trace of python calls that resulted in this exception/failure was: File: 'exec_python_func() autogenerated', lineno: 2, function: <module>      0001:  *** 0002:do_bootimg(d)      0003: File: '/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/poky/meta/classes/image-live.bbclass', lineno: 258, function: do_bootimg      0254:    if d.getVar("PCBIOS") == "1":      0255:        bb.build.exec_func('build_syslinux_cfg', d)      0256:    if d.getVar("EFI") == "1":      0257:        bb.build.exec_func('build_efi_cfg', d)  *** 0258:    bb.build.exec_func('build_hddimg', d)      0259:    bb.build.exec_func('build_iso', d)      0260:    bb.build.exec_func('create_symlinks', d)      0261:}      0262:do_bootimg[subimages] = "hddimg iso" File: '/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/poky/bitbake/lib/bb/build.py', lineno: 256, function: exec_func      0252:    with bb.utils.fileslocked(lockfiles):      0253:        if ispython:      0254:            exec_func_python(func, d, runfile, cwd=adir)      0255:        else:  *** 0256:            exec_func_shell(func, d, runfile, cwd=adir)      0257:      0258:    try:      0259:        curcwd = os.getcwd()      0260:    except: File: '/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/poky/bitbake/lib/bb/build.py', lineno: 503, function: exec_func_shell      0499:    with open(fifopath, 'r+b', buffering=0) as fifo:      0500:        try:      0501:            bb.debug(2, "Executing shell function %s" % func)      0502:            with open(os.devnull, 'r+') as stdin, logfile:  *** 0503:                bb.process.run(cmd, shell=False, stdin=stdin, log=logfile, extrafiles=[(fifo,readfifo)])      0504:        except bb.process.ExecutionError as exe:      0505:            # Find the backtrace that the shell trap generated      0506:            backtrace_marker_regex = re.compile(r"WARNING: Backtrace \(BB generated script\)")      0507:            stdout_lines = (exe.stdout or "").split("\n") File: '/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/poky/bitbake/lib/bb/process.py', lineno: 184, function: run      0180:        if not stderr is None:      0181:            stderr = stderr.decode("utf-8")      0182:      0183:    if pipe.returncode != 0:  *** 0184:        raise ExecutionError(cmd, pipe.returncode, stdout, stderr)      0185:    return stdout, stderr Exception: bb.process.ExecutionError: Execution of '/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/build/tmp/work/edison-poky-linux/edison-image/1.0-r0/temp/run.build_hddimg.256530' failed with exit code 1: mkdosfs: unable to create /home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/build/tmp/work/edison-poky-linux/edison-image/1.0-r0/deploy-edison-image-image-complete/edison-image-edison-20210524113748.hddimg mkfs.fat 4.1 (2017-01-24) WARNING: exit code 1 from a shell command.

The reason is that the directory deploy-edison-image-image-complete doesn't exist at the time mkdosfs want to write. However after completing the remainder of image live the directory does exists. Consequently, running bitbake a second time image-live succeeds.

I've tried various thing including expressly creating the directory before mkdosfs, but nothing worked. It seems I don't understand how it is supposed to work in the first place.

However, I managed to trace back the issue to this commit 91e4a1c1 "image-live.bbclass: optional depends when ROOTFS empty".

Reverting this resolves the issue.

Any idea what could be wrong?