Date   

Current high bug count owners for Yocto Project 3.4

Stephen Jolley
 

All,

Below is the list as of top 50 bug owners as of the end of WW21 of who have open medium or higher bugs and enhancements against YP 3.4.   There are 110 possible work days left until the final release candidates for YP 3.4 needs to be released.

Who

Count

ross@...

31

richard.purdie@...

29

david.reyna@...

22

bruce.ashfield@...

20

michael.opdenacker@...

19

trevor.gamblin@...

12

bluelightning@...

12

timothy.t.orling@...

11

akuster808@...

11

JPEWhacker@...

11

randy.macleod@...

10

sakib.sajal@...

9

kai.kang@...

8

hongxu.jia@...

7

Qi.Chen@...

6

mingli.yu@...

6

chee.yang.lee@...

5

raj.khem@...

5

tony.tascioglu@...

4

yi.zhao@...

4

alexandre.belloni@...

3

mostthingsweb@...

3

jon.mason@...

2

nicolas.dechesne@...

2

jaewon@...

2

ydirson@...

2

mshah@...

2

pokylinux@...

2

alejandro@...

2

yf3yu@...

2

liezhi.yang@...

1

stacygaikovaia@...

1

dl9pf@...

1

open.source@...

1

yoctoproject@...

1

mark.hatle@...

1

kexin.hao@...

1

kergoth@...

1

shachar@...

1

Martin.Jansa@...

1

mister_rs@...

1

diego.sueiro@...

1

john.kaldas.enpj@...

1

Nathan.Dunne@...

1

devendra.tewari@...

1

naveen.kumar.saini@...

1

prabin.ca@...

1

saul.wold@...

1

mhalstead@...

1

jeanmarie.lemetayer@...

1

thomas.perrot@...

1

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Yocto Project Newcomer & Unassigned Bugs - Help Needed

Stephen Jolley
 

All,

 

The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project.  If anyone can help, please take ownership of the bug and send patches!  If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 354 unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out with these.  Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.  There are also roughly four different "priority" classes right now, “3.2”, “3.3, "3.99" and "Future", the more pressing/urgent issues being in "3.2" and then “3.3”.

 

Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).  The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


[ANNOUNCEMENT] Yocto Project 3.3.1 (hardknott-25.0.1) is Released

Vineela
 

 

Generating announcement for point release 3.3.1.

 

We are pleased to announce the Yocto Project 3.3.1 (hardknott-25.0.1) Release is now available for download.

 

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/poky-hardknott-25.0.1.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.3.1/poky-hardknott-25.0.1.tar.bz2

 

A gpg signed version of these release notes is available at:

 

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/RELEASENOTES

 

Full Test Report:

 

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/testreport.txt

 

Thank you for everyone's contributions to this release.

 

Vineela Tummalapalli

Yocto Project Build and Release

vineela.tummalapalli@...

 

--------------------------

yocto-3.3.1 Release Notes

--------------------------

 

--------------------------

Repositories/Downloads

--------------------------

 

Repository Name: poky

Repository Location: https://git.yoctoproject.org/git/poky

Branch: hardknott

Tag: yocto-3.3.1

Git Revision: 05a8aad57ce250b124db16705acec557819905ae

Release Artefact: poky-hardknott-25.0.1

sha: 409b92d819f0c6e928b37bcc7cc4e80e5f27aa94748dcb479e325a4559c391c2

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/poky-hardknott-25.0.1.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.3.1/poky-hardknott-25.0.1.tar.bz2

 

Repository Name: openembedded-core

Repository Location: https://git.openembedded.org/openembedded-core

Branch: hardknott

Tag: 2021-04.1-hardknott

Git Revision: efce6334bf122a64f63d46c1c04e3dbffe298c51

Release Artefact: oecore-hardknott-25.0.1

sha: d53cdc060784ee7c86853b3b8120d6b3d0b445098cfcd27c939f303f9075262f

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/oecore-hardknott-25.0.1.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.3.1/oecore-hardknott-25.0.1.tar.bz2

 

Repository Name: meta-mingw

Repository Location: https://git.yoctoproject.org/git/meta-mingw

Branch: hardknott

Tag: yocto-3.3.1

Git Revision: 422b96cb2b6116442be1f40dfb5bd77447d1219e

Release Artefact: meta-mingw-hardknott-25.0.1

sha: 89bce008a93d4717bca4069c1fd0004d88bf39e8a8098eb1e8376bc7521a600f

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/meta-mingw-hardknott-25.0.1.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.3.1/meta-mingw-hardknott-25.0.1.tar.bz2

 

Repository Name: meta-gplv2

Repository Location: https://git.yoctoproject.org/git/meta-gplv2

Branch: hardknott

Tag: yocto-3.3.1

Git Revision: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f

Release Artefact: meta-gplv2-hardknott-25.0.1

sha: 988a222f13a9a87adf723cb86bd7db2648b3303e15bb3bac2d73e89f3faa547f

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/meta-gplv2-hardknott-25.0.1.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.3.1/meta-gplv2-hardknott-25.0.1.tar.bz2

 

Repository Name: bitbake

Repository Location: https://git.openembedded.org/bitbake

Branch: 1.50

Tag: 2021-04.1-hardknott

Git Revision: b67476d4758915db7a5d9f58bc903ae7501a1774

Release Artefact: bitbake-hardknott-25.0.1

sha: 3203a3c80f7ac749b1436b67b25733dbbe09b7ce9b32715a9f2fcd6bc24ec718

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/bitbake-hardknott-25.0.1.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.3.1/bitbake-hardknott-25.0.1.tar.bz2

 

Repository Name: yocto-docs

Repository Location: https://git.yoctoproject.org/git/yocto-docs

Branch: hardknott

Tag: yocto-3.3.1

Git Revision:eb19a2b5687f11c22c7fc26d3efabbf65adb572e

 

---------------

Contributors

--------------

Alejandro Enedino Hernandez Samaniego

Alexander Kanavin

Anders Wallin

Anthony Bagwell

Anuj Mittal

Bruce Ashfield

Changqing Li

Chen Qi

Christophe Chapuis

Daniel Ammann

Douglas Royds

Gavin Li

He Zhe

hongxu

Jonas Höppner

Jon Mason

Jose Quaresma

Joshua Watt

Kai Kang

Kevin Hao

Khairul Rohaizzat Jamaluddin

Khem Raj

Konrad Weihmann

Michael Opdenacker

Mikko Rapeli

Mingli Yu

Nicolas Dechesne

Niels Avonds

Paul Eggleton

Peter Budny

Peter Kjellerstedt

Quentin Schulz

Randy MacLeod

Reto Schneider

Richard Purdie

Romain Naour

Ross Burton

Sakib Sajal

Sangeeta Jain

Saul Wold

Stefan Ghinea

Stephen Jolley

Trevor Gamblin

Ulrich Ölmann

Vinícius Ossanes Aquino

wangmy

Wes Lindauer

Yanfei Xu

Yann Dirson

Yi Fan Yu

Yi Zhao

zhengruoqin

 

---------------

Known Issues

---------------

An intermittent systemtap issue occurred on arm during testing.

 

---------------

Security Fixes

---------------

db: update CVE_PRODUCT

qemu: fix CVE-2021-3392

qemu: fix CVE-2021-20263

qemu: fix CVE-2020-27821

xserver-xorg: fix CVE-2021-3472

rsync: fix CVE-2020-14387

glib-2.0: fix CVE-2021-28153

qemu: fix CVE-2021-20257

qemu: fix CVE-2021-3416

qemu: fix CVE-2021-3409

qemu: fix CVE-2021-20221

qemu: fix CVE-2020-29443

qemu: fix CVE-2021-20181

gdk-pixbuf: fix CVE-2021-20240

cairo: fix CVE-2020-35492

wpa-supplicant: fix CVE-2021-30004

busybox: fix CVE-2021-28831

qemu: Fix CVE-2020-35517

 

 

---------------

Fixes

---------------

documentation: prepare for 3.3.1 release

build-appliance-image: Update to hardknott head revision

poky.conf: Bump version for 3.3.1 hardknott release

puzzles: Upstream changed to main branch for development

linux-firmware: include all relevant files in -bcm4356

lsb-release: fix reproducibility failure

ruby: upgrade 3.0.0 -> 3.0.1

grub2.inc: remove '-O2' from CFLAGS

dejagnu: needs expect at runtime

libcap: Configure Make variables correctly without a horrible hack

lttng-modules: backport patches to fix build against 5.12+ kernel

linux-yocto/5.4: qemuppc32: reduce serial shutdown issues

linux-firmware: upgrade 20210208 -> 20210315

oeqa/qemurunner: Improve handling of run_serial for shutdown commands

oeqa/qemurunner: Fix binary vs str issue

oeqa/qemurunner: Improve logging thread exit handling for qemu shutdown test

sanity.bbclass: mention CONNECTIVITY_CHECK_URIS in network failure message

libevent: Increase ptest timing tolerance 50 ms -> 100 ms

classes/image: Use xargs to set file timestamps

linux-yocto/5.10: qemuppc32: reduce serial shutdown issues

lib/package_manager: Use shutil.copy instead of bb.utils.copyfile for intercepts

diffoscope: add native libraries to LD_LIBRARY_PATH

Revert "oeqa: Set LD_LIBRARY_PATH when executing native commands"

oe-buildenv-internal: add BitBake's library to PYTHONPATH

webkitgtk: Fix reproducibility in minibrowser

busybox: Fix reproducibility

libjpeg-turbo: Use --reproducible option for nasm

ptest-runner: libgcc must be installed for pthread_cancel to work

linux-yocto/5.4: update to v5.4.116

linux-yocto/5.10: update to v5.10.34

linux-yocto/5.4: update to v5.4.114

perf: fix python-audit RDEPENDS

linux-yocto/5.10: update to v5.10.32

linux-yocto/5.10: qemuriscv32.cfg: RV32 only supports 1G physical memory

linux-yocto/5.10: aufs fixes

yocto-uninative: Update to 3.1 which includes a patchelf fix

wireless-regdb: upgrade 2020.11.20 -> 2021.04.21

rootfs.py: find .ko.gz and .ko.xz kernel modules as well

pybootchart/draw: Avoid divide by zero error

patchelf: Fix alignment patch

mesa: upgrade 21.0.2 -> 21.0.3

patchelf: Fix note section alignment issues

license_image.bbclass: Fix symlink to generic license files

license_image.bbclass: Detect broken symlinks

bitbake: runqueue: Handle deferred task rehashing in multiconfig builds

bitbake: runqueue: Fix multiconfig deferred task sstate validity caching issue

patchelf: Backport fix from upstream for note section overlap error

weston: fix build failure due to race condition

meta/lib/oeqa/core/tests/cases/timeout.py: add a testcase for the previous fix

oeqa: tear down oeqa decorators if one of them raises an exception in setup

cmake.bbclass: remove ${B} before cmake_do_configure

kernel-yocto.bbclass: chdir to ${WORKDIR} for do_kernel_checkout

yocto-check-layer: Avoid bug when iterating and autoadding dependencies

libssh2: fix build failure with option no-ecdsa

go: Use dl.google.com for SRC_URI

cve-update-db-native: skip on empty cpe23Uri

rpm: Upgrade to 4.16.1.3

runqemu: Ensure we cleanup snapshot files after image run

lttng-tools: Fix path for test_python_looging

lttng-tools: Fix missing legacy test files

deb: apply postinstall on sdk

externalsrc: Detect code changes in submodules

Revert "externalsrc: Detect code changes in submodules"

arch-armv6m.inc: fix access rights

libxshmfence: Build fixes for riscv32

packagegroup-core-tools-testapps.bb: Remove kexec for riscv32

packagegroup-core-tools-profile: Remove valgrind for riscv32

ltp: fix empty ltp-dev package

glslang: strip whitespace in pkgconfig file

go: upgrade 1.16.2 -> 1.16.3

pango: re-enable ptest

kmod: do not symlink config.guess/config.sub during autoreconf

libtool: make sure autoheader run before automake

Revert "inittab: Add getty launch on hvc0 for qemuppc64"

sysvinit-inittab/start_getty: Check /sys for the tty device existence

modutils-initscripts: Bail out when no module is installed

systemd: upgrade 247.4 -> 247.6

insane: clean up some more warning messages

sanity: Add error check for '%' in build path

groff: not ship /usr/bin/grap2graph

oeqa/runtime: space needed

parselogs: ignore floppy error on qemu-system-x86 at boot stage

go: update SRC_URI to use https protocol

mesa: upgrade 21.0.1 -> 21.0.2

systemd: Fix build on mips/musl

python3: Improve logging, syntax and update deprecated modules to create_manifest

python3: Upgrade 3.9.2 -> 3.9.4

oeqa/runtime/cases: Only disable/enable for current boot

oe-time-dd-test.sh: increase timeout to 15 sec

scripts/oe-debuginfod: correct several issues

ca-certificates: Fix openssl runtime cert dependencies

nettle: upgrade 3.7.1 -> 3.7.2

linux-yocto/5.10: fix arm defconfig warnings

linux-yocto/5.4: fix arm defconfig warnings

linux-yocto/5.4: update to v5.4.112

linux-yocto-rt/5.10: update to -rt34

linux-yocto/5.10: update to v5.10.30

linux-yocto/5.4: update to v5.4.111

linux-yocto/5.10: update to v5.10.29

linux-yocto/5.10: BSP configuration fixes

linux-yocto-dev: add features/scsi/scsi-debug.scc features/gpio/mockup.scc to KERNEL_FEATURES

linux-yocto/5.10: update to v5.10.27

linux-yocto/5.4: update to v5.4.109

archiver: Fix typos

oeqa/selftest: Ensure packages classes are set correctly for maintainers test

pseudo: Upgrade to add trailing slashes ignore path fix

lib/oe/terminal: Fix tmux new-session on older tmux versions (<1.9)

bitbake: bitbake: tests/fetch: remove write protected files too

bitbake: fetch/gitsm: Fix crash when using git LFS and submodules

bitbake: bitbake-server: ensure server timeout is a float

bitbake: bitbake: tests/fetch: fix test execution without .gitconfig

bitbake: runqueue: Fix deferred task issues

oeqa/selftest: Hardcode test assumptions about heartbeat event timings

oe-time-dd-test.sh: provide more information from "top"

oe-time-dd-test.sh: make executable

ref-manual: add mention of DISTUTILS_SETUP_PATH

ref-manual: migration guide: add release codenames

ref-manual: add migration section for 3.3 release

ref-manual: tweak buildtools section

ref-manual: fix reference to build-essential

ref-manual: add FIT_KERNEL_COMP_ALG*

ref-manual: add passwd-expire to EXTRA_USERS_PARAMS

ref-manual: add python3targetconfig class and remove python 2 references

ref-manual: add REQUIRED_VERSION and adjust PREFERRED_VERSION entry

ref-manual: and SDK_CUSTOM_TEMPLATECONF to glossary

overview-manual: fix git command line

ref-manual: update/fix text for SDK_VERSION

Use variables for minimum host versions and bump Python to 3.6

ref-manual: add METADATA_REVISION and METADATA_BRANCH

bitbake: bitbake-user-manual: add REQUIRED_VERSION and adjust PREFERRED_VERSION entry

bitbake: bitbake-user-manual: document no support for using passwords in git URLs

docs: add a top level page for bitbake documentation

docs: replace anchor links

sdk-manual: fix typo

bitbake: bitbake: Update version to 1.50.0 stable release series


Re: ERROR: ParseError at .../bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4: Could not include required file images/basic-dev-image.bb

Quentin Schulz
 

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.


Re: using grpc fails with linker error: file in wrong format

Khem Raj
 

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


Re: ERROR: ParseError at .../bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4: Could not include required file images/basic-dev-image.bb

Zoran
 

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.


Re: ERROR: ParseError at .../bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4: Could not include required file images/basic-dev-image.bb

Zoran
 

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.


Re: Gatesgarth-24.0.4 image-live fails

Ferry Toth
 

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?


Re: ERROR: ParseError at .../bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4: Could not include required file images/basic-dev-image.bb

Quentin Schulz
 

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.


Gatesgarth-24.0.4 image-live fails

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?


ERROR: ParseError at .../bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4: Could not include required file images/basic-dev-image.bb

Zoran
 

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.

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
_______


using grpc fails with linker error: file in wrong format

Juergen Landwehr
 

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?

Thanks,

Jürgen


[meta-security][PATCH] libgssglue: update SRC_URI

Yi Zhao
 

Update SRC_URI to use Debian mirror because the original site is
unaccessible.

Fixes do_fetch error:
ERROR: libgssglue-0.4-r0 do_fetch: Fetcher failure for URL:
'http://www.citi.umich.edu/projects/nfsv4/linux/libgssglue/libgssglue-0.4.tar.gz'.
Unable to fetch URL from any source.

Signed-off-by: Yi Zhao <yi.zhao@...>
---
recipes-security/libgssglue/libgssglue_0.4.bb | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/recipes-security/libgssglue/libgssglue_0.4.bb b/recipes-security/libgssglue/libgssglue_0.4.bb
index f7859a7..88c58ed 100644
--- a/recipes-security/libgssglue/libgssglue_0.4.bb
+++ b/recipes-security/libgssglue/libgssglue_0.4.bb
@@ -21,7 +21,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=56871e72a5c475289c0d5e4ba3f2ee3a \
file://src/oid_ops.c;beginline=378;endline=398;md5=e02c165cb8383e950214baca2fbd664b \
"

-SRC_URI = "http://www.citi.umich.edu/projects/nfsv4/linux/${BPN}/${BP}.tar.gz \
+SRC_URI = "${DEBIAN_MIRROR}/main/libg/${BPN}/${BPN}_${PV}.orig.tar.bz2 \
file://libgssglue-canon-name.patch \
file://libgssglue-gss-inq-cred.patch \
file://libgssglue-mglueP.patch \
@@ -29,8 +29,8 @@ SRC_URI = "http://www.citi.umich.edu/projects/nfsv4/linux/${BPN}/${BP}.tar.gz \
file://libgssglue-fix-CVE-2011-2709.patch \
"

-SRC_URI[md5sum] = "088797f3180702fa54e786496b32e750"
-SRC_URI[sha256sum] = "3f791a75502ba723e5e85e41e5e0c711bb89e2716b7c0ec6e74bd1df6739043a"
+SRC_URI[md5sum] = "5ce81940965fa68c7635c42dcafcddfe"
+SRC_URI[sha256sum] = "bb47b2de78409f461811d0db8595c66e6631a9879c3621a35e4434b104ee52f5"

# gssglue can use krb5, spkm3... as gssapi library, configurable
RRECOMMENDS_${PN} += "krb5"
--
2.25.1


Re: [meta-dpdk][PATCH] dpdk: fix build with GCC 11

Naveen Saini
 

Please send this patch to meta-intel mailing list.

-----Original Message-----
From: yocto@... <yocto@...> On
Behalf Of Yu, Mingli
Sent: Thursday, May 20, 2021 3:38 PM
To: yocto@...
Subject: [yocto] [meta-dpdk][PATCH] dpdk: fix build with GCC 11

From: Mingli Yu <mingli.yu@...>

Fixes:
| In function 'memset',
| inlined from 'test_table_stub' at test_table_tables.c:151:4:
| /buildarea/tmp/work/intel_x86_64-wrs-linux/dpdk/19.11.5-r0/recipe-
sysroot/usr/include/bits/string_fortified.h:59:10: error: '__builtin_memset'
offset [0, 31] is out of the bounds [0, 0] [-Werror=array-bounds]

Signed-off-by: Mingli Yu <mingli.yu@...>
---
...001-test-table-fix-build-with-GCC-11.patch | 56 +++++++++++++++++++
recipes-extended/dpdk/dpdk_19.11.5.bb | 3 +-
2 files changed, 58 insertions(+), 1 deletion(-) create mode 100644 recipes-
extended/dpdk/dpdk/0001-test-table-fix-build-with-GCC-11.patch

diff --git a/recipes-extended/dpdk/dpdk/0001-test-table-fix-build-with-GCC-
11.patch b/recipes-extended/dpdk/dpdk/0001-test-table-fix-build-with-
GCC-11.patch
new file mode 100644
index 0000000..4f76290
--- /dev/null
+++ b/recipes-extended/dpdk/dpdk/0001-test-table-fix-build-with-GCC-
11.p
+++ atch
@@ -0,0 +1,56 @@
+From 33c12ac5ba5f09727c6de807e71403dd260a7bbc Mon Sep 17 00:00:00
2001
+From: Ferruh Yigit <ferruh.yigit@...>
+Date: Mon, 17 May 2021 16:57:39 +0100
+Subject: [PATCH] test/table: fix build with GCC 11
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Build error:
+../app/test/test_table_tables.c: In function ‘test_table_stub’:
+../app/test/test_table_tables.c:31:9:
+ warning: ‘memset’ offset [0, 31] is out of the bounds [0, 0]
+ [-Warray-bounds]
+ memset((uint8_t *)mbuf + sizeof(struct rte_mbuf) + 32, 0, 32); \
+
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
+../app/test/test_table_tables.c:151:25:
+ note: in expansion of macro ‘PREPARE_PACKET’
+ 151 | PREPARE_PACKET(mbufs[i], 0xadadadad);
+ | ^~~~~~~~~~~~~~
+
+'key' points to mbuf header + 32 bytes, and memset clears next 32 bytes
+of 'key', so overall there needs to be 64 bytes after mbuf header.
+Adding a mbuf size check before memset.
+
+The original code has an assumption that mbuf data buffer follows mbuf
+header, this patch accepts same assumption.
+
+Bugzilla ID: 677
+Fixes: 5205954791cb ("app/test: packet framework unit tests")
+Cc: stable@...
+
+Upstream-Status: Backport
+[https://github.com/DPDK/dpdk/commit/33c12ac5ba5f09727c6de807e7140
3dd26
+0a7bbc]
+
+Signed-off-by: Ferruh Yigit <ferruh.yigit@...>
+Signed-off-by: Mingli Yu <mingli.yu@...>
+---
+ app/test/test_table_tables.c | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/app/test/test_table_tables.c
+b/app/test/test_table_tables.c index 1aa269f95..4ff6ab16a 100644
+--- a/app/test/test_table_tables.c
++++ b/app/test/test_table_tables.c
+@@ -28,7 +28,8 @@ table_test table_tests[] = {
+ APP_METADATA_OFFSET(0)); \
+ key = RTE_MBUF_METADATA_UINT8_PTR(mbuf,
\
+ APP_METADATA_OFFSET(32)); \
+- memset(key, 0, 32); \
++ if (mbuf->priv_size + mbuf->buf_len >= 64) \
++ memset(key, 0, 32); \
+ k32 = (uint32_t *) key; \
+ k32[0] = (value); \
+ *signature = pipeline_test_hash(key, NULL, 0, 0);
\
+--
+2.17.1
+
diff --git a/recipes-extended/dpdk/dpdk_19.11.5.bb b/recipes-
extended/dpdk/dpdk_19.11.5.bb
index 8410c8a..2ae9b43 100644
--- a/recipes-extended/dpdk/dpdk_19.11.5.bb
+++ b/recipes-extended/dpdk/dpdk_19.11.5.bb
@@ -4,7 +4,8 @@ SRC_URI += " \
file://dpdk-16.04-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch \
file://dpdk-16.07-add-sysroot-option-within-app-makefile.patch \
file://0001-Starting-from-Linux-5.9-get_user_pages_remote-API-
do.patch \
- file://usertools-devbind-fix-binding-for-built-in-kernel-dr.patch"
+ file://usertools-devbind-fix-binding-for-built-in-kernel-dr.patch \
+ file://0001-test-table-fix-build-with-GCC-11.patch"


STABLE = "-stable"
--
2.29.2


[meta-security][PATCH] Correct "securiyt" typo in maintainers.inc

Robert P. J. Day
 

Signed-off-by: Robert P. J. Day <rpjday@...>

---

diff --git a/conf/distro/include/maintainers.inc b/conf/distro/include/maintainers.inc
index 7b82ef7..e02b903 100644
--- a/conf/distro/include/maintainers.inc
+++ b/conf/distro/include/maintainers.inc
@@ -1,4 +1,4 @@
-# meta-securiyt Maintainers File
+# meta-security Maintainers File
#
# This file contains a list of recipe maintainers.
#

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================


[meta-security][v2][PATCH] sssd: update to 2.5.0

Armin Kuster
 

Add new depends
Drop obsolete patches

Signed-off-by: Armin Kuster <akuster808@...>

----
v2]
Fix issue with nsupdate check
don't use host bind
---
...AC_CHECK_FILE-when-building-manpages.patch | 34 --------
...s-Collision-with-external-nss-symbol.patch | 78 -------------------
...defines-which-otherwise-are-availabl.patch | 32 --------
.../sssd/files/drop_ntpdate_chk.patch | 28 +++++++
.../sssd/files/fix-ldblibdir.patch | 25 ------
recipes-security/sssd/files/fix_gid.patch | 27 +++++++
recipes-security/sssd/files/no_gen.patch | 19 +++++
.../sssd/{sssd_1.16.5.bb => sssd_2.5.0.bb} | 29 +++----
8 files changed, 89 insertions(+), 183 deletions(-)
delete mode 100644 recipes-security/sssd/files/0001-build-Don-t-use-AC_CHECK_FILE-when-building-manpages.patch
delete mode 100644 recipes-security/sssd/files/0001-nss-Collision-with-external-nss-symbol.patch
delete mode 100644 recipes-security/sssd/files/0002-Provide-missing-defines-which-otherwise-are-availabl.patch
create mode 100644 recipes-security/sssd/files/drop_ntpdate_chk.patch
delete mode 100644 recipes-security/sssd/files/fix-ldblibdir.patch
create mode 100644 recipes-security/sssd/files/fix_gid.patch
create mode 100644 recipes-security/sssd/files/no_gen.patch
rename recipes-security/sssd/{sssd_1.16.5.bb => sssd_2.5.0.bb} (85%)

diff --git a/recipes-security/sssd/files/0001-build-Don-t-use-AC_CHECK_FILE-when-building-manpages.patch b/recipes-security/sssd/files/0001-build-Don-t-use-AC_CHECK_FILE-when-building-manpages.patch
deleted file mode 100644
index b64670c..0000000
--- a/recipes-security/sssd/files/0001-build-Don-t-use-AC_CHECK_FILE-when-building-manpages.patch
+++ /dev/null
@@ -1,34 +0,0 @@
-From d54aa109600bcd02bf72cfe64c01935890a102a1 Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Jonatan=20P=C3=A5lsson?= <jonatan.p@...>
-Date: Fri, 21 Aug 2020 14:45:10 +0200
-Subject: [PATCH] build: Don't use AC_CHECK_FILE when building manpages
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-AC_CHECK_FILE does not support cross-compilation, and will only check
-the host rootfs. Replace AC_CHECK_FILE with a 'test -f <FILE>' instead,
-to allow building manpages when cross-compiling.
-
-Upstream-status: Submitted [https://github.com/SSSD/sssd/pull/5289]
-Signed-off-by: Jonatan Pålsson <jonatan.p@...>
----
- src/external/docbook.m4 | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/src/external/docbook.m4 b/src/external/docbook.m4
-index deb8632fa..acdc89a68 100644
---- a/src/external/docbook.m4
-+++ b/src/external/docbook.m4
-@@ -18,7 +18,7 @@ dnl Checks if the XML catalog given by FILE exists and
- dnl if a particular URI appears in the XML catalog
- AC_DEFUN([CHECK_STYLESHEET],
- [
-- AC_CHECK_FILE($1, [], [AC_MSG_ERROR([could not find XML catalog])])
-+ AS_IF([test -f "$1"], [], [AC_MSG_ERROR([could not find XML catalog])])
-
- AC_MSG_CHECKING([for ifelse([$3],,[$2],[$3]) in XML catalog])
- if AC_RUN_LOG([$XSLTPROC --catalogs --nonet --noout "$2" >&2]); then
---
-2.26.1
-
diff --git a/recipes-security/sssd/files/0001-nss-Collision-with-external-nss-symbol.patch b/recipes-security/sssd/files/0001-nss-Collision-with-external-nss-symbol.patch
deleted file mode 100644
index c319269..0000000
--- a/recipes-security/sssd/files/0001-nss-Collision-with-external-nss-symbol.patch
+++ /dev/null
@@ -1,78 +0,0 @@
-From 05c315100a70d3372e891e9a0ea981a875b2ec90 Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Michal=20=C5=BDidek?= <mzidek@...>
-Date: Thu, 27 Feb 2020 06:50:40 +0100
-Subject: [PATCH] nss: Collision with external nss symbol
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-One of our internal static function names started
-to collide with external nss symbol. Additional
-sss_ suffix was added to avoid the collision.
-
-This is needed to unblock Fedora Rawhide's
-SSSD build.
-
-Reviewed-by: Pavel Březina <pbrezina@...>
-
-Upstream-Status: Backport [https://github.com/SSSD/sssd.git]
-Signed-off-by: Hongxu.jia@...
-Signed-off-by: Qi.Chen@...
----
- src/responder/nss/nss_cmd.c | 18 ++++++++++--------
- 1 file changed, 10 insertions(+), 8 deletions(-)
-
-diff --git a/src/responder/nss/nss_cmd.c b/src/responder/nss/nss_cmd.c
-index 25e663ed5..a4d4cfc0b 100644
---- a/src/responder/nss/nss_cmd.c
-+++ b/src/responder/nss/nss_cmd.c
-@@ -728,11 +728,13 @@ done:
- talloc_free(cmd_ctx);
- }
-
--static void nss_setnetgrent_done(struct tevent_req *subreq);
-+static void sss_nss_setnetgrent_done(struct tevent_req *subreq);
-
--static errno_t nss_setnetgrent(struct cli_ctx *cli_ctx,
-- enum cache_req_type type,
-- nss_protocol_fill_packet_fn fill_fn)
-+/* This function's name started to collide with external nss symbol,
-+ * so it has additional sss_* prefix unlike other functions here. */
-+static errno_t sss_nss_setnetgrent(struct cli_ctx *cli_ctx,
-+ enum cache_req_type type,
-+ nss_protocol_fill_packet_fn fill_fn)
- {
- struct nss_ctx *nss_ctx;
- struct nss_state_ctx *state_ctx;
-@@ -774,7 +776,7 @@ static errno_t nss_setnetgrent(struct cli_ctx *cli_ctx,
- goto done;
- }
-
-- tevent_req_set_callback(subreq, nss_setnetgrent_done, cmd_ctx);
-+ tevent_req_set_callback(subreq, sss_nss_setnetgrent_done, cmd_ctx);
-
- ret = EOK;
-
-@@ -787,7 +789,7 @@ done:
- return EOK;
- }
-
--static void nss_setnetgrent_done(struct tevent_req *subreq)
-+static void sss_nss_setnetgrent_done(struct tevent_req *subreq)
- {
- struct nss_cmd_ctx *cmd_ctx;
- errno_t ret;
-@@ -1037,8 +1039,8 @@ static errno_t nss_cmd_initgroups_ex(struct cli_ctx *cli_ctx)
-
- static errno_t nss_cmd_setnetgrent(struct cli_ctx *cli_ctx)
- {
-- return nss_setnetgrent(cli_ctx, CACHE_REQ_NETGROUP_BY_NAME,
-- nss_protocol_fill_setnetgrent);
-+ return sss_nss_setnetgrent(cli_ctx, CACHE_REQ_NETGROUP_BY_NAME,
-+ nss_protocol_fill_setnetgrent);
- }
-
- static errno_t nss_cmd_getnetgrent(struct cli_ctx *cli_ctx)
---
-2.21.0
-
diff --git a/recipes-security/sssd/files/0002-Provide-missing-defines-which-otherwise-are-availabl.patch b/recipes-security/sssd/files/0002-Provide-missing-defines-which-otherwise-are-availabl.patch
deleted file mode 100644
index 1a22332..0000000
--- a/recipes-security/sssd/files/0002-Provide-missing-defines-which-otherwise-are-availabl.patch
+++ /dev/null
@@ -1,32 +0,0 @@
-From 37a0999e5a9f54e1c61a02a7fbab6fcd04738b3c Mon Sep 17 00:00:00 2001
-From: Armin Kuster <akuster808@...>
-Date: Thu, 8 Oct 2020 05:54:13 -0700
-Subject: [PATCH] Provide missing defines which otherwise are available on
- glibc system headers
-
-Signed-off-by: Armin Kuster <akuster808@...>
-
-Upsteam-Status: Pending
-
----
- src/util/util.h | 4 ++++
- 1 file changed, 4 insertions(+)
-
-diff --git a/src/util/util.h b/src/util/util.h
-index 8a754dbfd..6e55b4bdc 100644
---- a/src/util/util.h
-+++ b/src/util/util.h
-@@ -76,6 +76,10 @@
- #define MAX(a, b) (((a) > (b)) ? (a) : (b))
- #endif
-
-+#ifndef ALLPERMS
-+# define ALLPERMS (S_ISUID|S_ISGID|S_ISVTX|S_IRWXU|S_IRWXG|S_IRWXO)/* 07777 */
-+#endif
-+
- #define SSSD_MAIN_OPTS SSSD_DEBUG_OPTS
-
- #define SSSD_SERVER_OPTS(uid, gid) \
---
-2.17.1
-
diff --git a/recipes-security/sssd/files/drop_ntpdate_chk.patch b/recipes-security/sssd/files/drop_ntpdate_chk.patch
new file mode 100644
index 0000000..338af5d
--- /dev/null
+++ b/recipes-security/sssd/files/drop_ntpdate_chk.patch
@@ -0,0 +1,28 @@
+nsupdate path is needed for various exec call
+but don't run natvie tests on it.
+
+
+Upstream-Status: Inappropriate [OE specific]
+Signed-off-by: Armin Kuster <akuster808@...>
+
+Index: sssd-2.5.0/src/external/nsupdate.m4
+===================================================================
+--- sssd-2.5.0.orig/src/external/nsupdate.m4
++++ sssd-2.5.0/src/external/nsupdate.m4
+@@ -3,16 +3,4 @@ AC_MSG_CHECKING(for executable nsupdate)
+ if test -x "$NSUPDATE"; then
+ AC_DEFINE_UNQUOTED([NSUPDATE_PATH], ["$NSUPDATE"], [The path to nsupdate])
+ AC_MSG_RESULT(yes)
+-
+- AC_MSG_CHECKING(for nsupdate 'realm' support')
+- if AC_RUN_LOG([echo realm |$NSUPDATE >&2]); then
+- AC_MSG_RESULT([yes])
+- else
+- AC_MSG_RESULT([no])
+- AC_MSG_ERROR([nsupdate does not support 'realm'])
+- fi
+-
+-else
+- AC_MSG_RESULT([no])
+- AC_MSG_ERROR([nsupdate is not available])
+ fi
diff --git a/recipes-security/sssd/files/fix-ldblibdir.patch b/recipes-security/sssd/files/fix-ldblibdir.patch
deleted file mode 100644
index e350baf..0000000
--- a/recipes-security/sssd/files/fix-ldblibdir.patch
+++ /dev/null
@@ -1,25 +0,0 @@
-When calculate value of ldblibdir, it checks whether the directory of
-$ldblibdir exists. If not, it assigns ldblibdir with ${libdir}/ldb. It is not
-suitable for cross compile. Fix it that only re-assign ldblibdir when its value
-is empty.
-
-Upstream-Status: Inappropriate [cross compile specific]
-
-Signed-off-by: Kai Kang <kai.kang@...>
----
- src/external/libldb.m4 | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/src/external/libldb.m4 b/src/external/libldb.m4
-index c400add..5e5f06d 100644
---- a/src/external/libldb.m4
-+++ b/src/external/libldb.m4
-@@ -19,7 +19,7 @@ if test x"$with_ldb_lib_dir" != x; then
- ldblibdir=$with_ldb_lib_dir
- else
- ldblibdir="`$PKG_CONFIG --variable=modulesdir ldb`"
-- if ! test -d $ldblibdir; then
-+ if test -z $ldblibdir; then
- ldblibdir="${libdir}/ldb"
- fi
- fi
diff --git a/recipes-security/sssd/files/fix_gid.patch b/recipes-security/sssd/files/fix_gid.patch
new file mode 100644
index 0000000..9b481cc
--- /dev/null
+++ b/recipes-security/sssd/files/fix_gid.patch
@@ -0,0 +1,27 @@
+from ../sssd-2.5.0/src/util/sss_pam_data.c:27:
+| ../sssd-2.5.0/src/util/debug.h:88:44: error: unknown type name 'uid_t'; did you mean 'uint_t'?
+| 88 | int chown_debug_file(const char *filename, uid_t uid, gid_t gid);
+| | ^~~~~
+| | uint_t
+| ../sssd-2.5.0/src/util/debug.h:88:55: error: unknown type name 'gid_t'
+| 88 | int chown_debug_file(const char *filename, uid_t uid, gid_t gid);
+| | ^~~~~
+| make[2]: *** [Makefile:22529: src/util/libsss_iface_la-sss_pam_data.lo] Error 1
+| make[2]: *** Waiting for unfinished jobs....
+
+Upstream-Status: Pending
+Signed-off-by: Armin Kuster <akuster808@...>
+
+Index: sssd-2.5.0/src/util/debug.h
+===================================================================
+--- sssd-2.5.0.orig/src/util/debug.h
++++ sssd-2.5.0/src/util/debug.h
+@@ -24,6 +24,8 @@
+ #include "config.h"
+
+ #include <stdio.h>
++#include <unistd.h>
++#include <sys/types.h>
+ #include <stdbool.h>
+
+ #include "util/util_errors.h"
diff --git a/recipes-security/sssd/files/no_gen.patch b/recipes-security/sssd/files/no_gen.patch
new file mode 100644
index 0000000..5c83777
--- /dev/null
+++ b/recipes-security/sssd/files/no_gen.patch
@@ -0,0 +1,19 @@
+don't run generate-sbus-code
+
+Upstream-Status: Inappropriate [OE Specific]
+
+Signed-off-by: Armin Kuster <akuster808@...>
+
+Index: sssd-2.5.0/Makefile.am
+===================================================================
+--- sssd-2.5.0.orig/Makefile.am
++++ sssd-2.5.0/Makefile.am
+@@ -1033,8 +1033,6 @@ generate-sbus-code:
+
+ .PHONY: generate-sbus-code
+
+-BUILT_SOURCES += generate-sbus-code
+-
+ EXTRA_DIST += \
+ sbus_generate.sh.in \
+ src/sbus/codegen/dbus.xml \
diff --git a/recipes-security/sssd/sssd_1.16.5.bb b/recipes-security/sssd/sssd_2.5.0.bb
similarity index 85%
rename from recipes-security/sssd/sssd_1.16.5.bb
rename to recipes-security/sssd/sssd_2.5.0.bb
index 9784ec7..4c92519 100644
--- a/recipes-security/sssd/sssd_1.16.5.bb
+++ b/recipes-security/sssd/sssd_2.5.0.bb
@@ -5,8 +5,8 @@ SECTION = "base"
LICENSE = "GPLv3+"
LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504"

-DEPENDS = "openldap cyrus-sasl libtdb ding-libs libpam c-ares krb5 autoconf-archive"
-DEPENDS_append = " libldb dbus libtalloc libpcre glib-2.0 popt e2fsprogs libtevent"
+DEPENDS = "acl attr openldap cyrus-sasl libtdb ding-libs libpam c-ares krb5 autoconf-archive"
+DEPENDS_append = " libldb dbus libtalloc libpcre glib-2.0 popt e2fsprogs libtevent bind p11-kit"

DEPENDS_append_libc-musl = " musl-nscd"

@@ -15,16 +15,14 @@ DEPENDS_append_libc-musl = " musl-nscd"
DEPENDS += "${@bb.utils.contains('PACKAGECONFIG', 'nss', '', \
bb.utils.contains('PACKAGECONFIG', 'crypto', '', 'nss', d), d)}"

-SRC_URI = "https://releases.pagure.org/SSSD/${BPN}/${BP}.tar.gz \
+SRC_URI = "https://github.com/SSSD/sssd/releases/download/2.5.0/sssd-2.5.0.tar.gz \
file://sssd.conf \
file://volatiles.99_sssd \
- file://fix-ldblibdir.patch \
- file://0001-build-Don-t-use-AC_CHECK_FILE-when-building-manpages.patch \
- file://0001-nss-Collision-with-external-nss-symbol.patch \
- file://0002-Provide-missing-defines-which-otherwise-are-availabl.patch \
+ file://no_gen.patch \
+ file://fix_gid.patch \
+ file://drop_ntpdate_chk.patch \
"
-
-SRC_URI[sha256sum] = "2e1a7bf036b583f686d35164f2d79bdf4857b98f51fe8b0d17aa0fa756e4d0c0"
+SRC_URI[sha256sum] = "afa62d7d8d23fca3aba093abe4ec0d14e7d9346c5b28ceb7c2c624bed98caa06"

inherit autotools pkgconfig gettext python3-dir features_check systemd

@@ -34,7 +32,7 @@ SSSD_UID ?= "root"
SSSD_GID ?= "root"

CACHED_CONFIGUREVARS = "ac_cv_member_struct_ldap_conncb_lc_arg=no \
- ac_cv_path_NSUPDATE=${bindir} ac_cv_prog_HAVE_PYTHON3=${PYTHON_DIR} \
+ ac_cv_prog_HAVE_PYTHON3=${PYTHON_DIR} \
"

PACKAGECONFIG ?="nss nscd autofs sudo infopipe"
@@ -42,13 +40,13 @@ PACKAGECONFIG += "${@bb.utils.contains('DISTRO_FEATURES', 'selinux', 'selinux',
PACKAGECONFIG += "${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'systemd', '', d)}"

PACKAGECONFIG[autofs] = "--with-autofs, --with-autofs=no"
-PACKAGECONFIG[crypto] = "--with-crypto=libcrypto, , libcrypto"
+PACKAGECONFIG[crypto] = ", , libcrypto"
PACKAGECONFIG[curl] = "--with-kcm, --without-kcm, curl jansson"
PACKAGECONFIG[infopipe] = "--with-infopipe, --with-infopipe=no, "
PACKAGECONFIG[manpages] = "--with-manpages, --with-manpages=no, libxslt-native docbook-xml-dtd4-native docbook-xsl-stylesheets-native"
PACKAGECONFIG[nl] = "--with-libnl, --with-libnl=no, libnl"
PACKAGECONFIG[nscd] = "--with-nscd=${sbindir}, --with-nscd=no "
-PACKAGECONFIG[nss] = "--with-crypto=nss, ,nss,"
+PACKAGECONFIG[nss] = ", ,nss,"
PACKAGECONFIG[python3] = "--with-python3-bindings, --without-python3-bindings"
PACKAGECONFIG[samba] = "--with-samba, --with-samba=no, samba"
PACKAGECONFIG[selinux] = "--with-selinux, --with-selinux=no --with-semanage=no, libselinux"
@@ -75,6 +73,9 @@ do_configure_prepend() {
sed -i -e "s#\$sss_extra_libdir##" ${S}/src/external/libresolv.m4
}

+do_compile_prepend () {
+ echo '#define NSUPDATE_PATH "${bindir}"' >> ${B}/config.h
+}
do_install () {
oe_runmake install DESTDIR="${D}"
rmdir --ignore-fail-on-non-empty "${D}/${bindir}"
@@ -119,10 +120,10 @@ SYSTEMD_SERVICE_${PN} = " \
"
SYSTEMD_AUTO_ENABLE = "disable"

-FILES_${PN} += "${libdir} ${datadir} ${base_libdir}/security/pam_sss.so"
+FILES_${PN} += "${libdir} ${datadir} ${base_libdir}/security/pam_sss*.so"
FILES_${PN}-dev = " ${includedir}/* ${libdir}/*la ${libdir}/*/*la"

# The package contains symlinks that trip up insane
INSANE_SKIP_${PN} = "dev-so"

-RDEPENDS_${PN} = "bind dbus libldb libpam"
+RDEPENDS_${PN} = "bind bind-utils dbus libldb libpam"
--
2.24.3


/proc/vmcore not created with CONFIG_PROC_VMCORE=y

Ori Pessach
 

Hello,

I'm trying to enable kdump on an intel x86_64 system, and while kexec boots the crash kernel (I use the same kernel image for the system and crash kernel) makedumpfile fails, apparently because it can't find /proc/vmcore.

My understanding is that vmcore should be found (and empty) in the system kernel, and populated in the crash kernel, but it's not found in either as far as I can tell.

/proc/config.gz shows that CONFIG_PROC_VMCORE Is set to 'y' so I'm not sure what's going on. Any ideas on how to solve this?

Thanks,

Ori Pessach


freescale imx-boot, fails to generate is imx-boot container for signed uboot ( wrong u-boot.bin used by imx-boot compile?)

richard allen
 

In Hardknott, trying to enabled signed uboot containers for signed fitimage

The interaction between the uboot-sign.bbclass and the imx-boot.bb is not working

 

MACHINE=imx8qxq-mek

UBOOT_SIGN_ENABLE= “1”

FIT_SIGN_INDIVIDUAL=”1”

 

(no SPL_SIGN_ENABLE)

 

I see the updated u-boot.bin in the uboot ${B}{config} sub-directory but other copies are still the original u-boot.bin

  • The updated u-boot.bin = u-boot-nodtb.bin + u-boot-pubkey.dtb ,

When imx-boot creates the flash.bin, it is using original u-boot.bin , not the updated one.

 

Have confirmed if I put the updated u-boot.bin where imx-boot will use when creating the flash.bin , then the resulting uboot will only boot signed fitImages .

 

Any known work-arounds ? or this a known bug?

Thanks

Richard Allen

 

 

 

 

 

 

 


[meta-zephyr][hardknott][PATCH] zephyr-kernel-src: switch from master branch to main

Naveen Saini
 

* branch was renamed in upstream repo

It fixes do_fetch failure

Signed-off-by: Naveen Saini <naveen.kumar.saini@...>
---
recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
index 8c987bb..5ee40d4 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
@@ -13,7 +13,7 @@ inherit cmake
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"

SRC_URI = "\
- git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=master;name=default \
+ git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=main;name=default \
git://github.com/zephyrproject-rtos/cmsis.git;protocol=https;destsuffix=git/modules/cmsis;name=cmsis \
git://github.com/zephyrproject-rtos/hal_nordic.git;protocol=https;destsuffix=git/modules/hal/nordic;name=nordic \
git://github.com/zephyrproject-rtos/hal_stm32.git;protocol=https;destsuffix=git/modules/hal/stm32;name=stm32 \
--
2.17.1


Re: Problem with YOCTO Dunfell and host Fedora 33

Zoran
 

Hello Joel,

Thank you for the tips. Really helpful, appreciated very much.

I spent some time this morning investigating this issue, and to find
the culprit.

Here are my findings, which resulted in a cannelloni.bb recipe change
(according to what you wrote).

The fix submitted is in recipe:
https://github.com/ZoranStojsavljevic/meta-socketcan/blob/master/recipes-can/cannelloni/cannelloni.bb

The last cannelloni version which works is:
https://github.com/mguentner/cannelloni/commit/0bd7e27db35bdef361226882ae04205504f7b2f4

The culprit introducing the cmake errors is this one:
https://github.com/mguentner/cannelloni/commit/d01dd1dc745914d129b1f4da2074e282253246af

And, the issue recorded with Maximilian Guentner's cannelloni repo:
https://github.com/mguentner/cannelloni/issues/35

Thank you again,
Zoran
_______

On Thu, May 20, 2021 at 4:48 PM Joel Winarske <joel.winarske@...> wrote:

Hi Zoran,

Your cannelloni recipe is set to autorev, meaning it's not locked to a commit. So when something changes upstream you have to manage it.

Chances are Canelloni introduced a CMake change which is overwriting (opposed to appending) one or more variables required for cross compiling. Perhaps try to cross compile (not a host build) Canelloni by itself without Yocto involved. Once that's sorted, then reintroduce yocto.


Joel


On Thu, May 20, 2021, 6:58 AM Zoran <zoran.stojsavljevic@...> wrote:

Hello Yocto developers,

I have few problems running the following self proprietary script from
one of my public git repos:
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/yocto-setup.sh

I recall that last time I used the script (I used then Fedora 31), the
./yocto setup dunfell worked seamlessly, did setup the environment,
and upon bitbake -k core-image-minimal completed the tasks without any
problem.

Now, I am using Fedora 33 (in the meantime I did two Fedora version upgrades).

The problem is that while compiling the cannelloni package, the
following errors were issued (please, look into the attached file
cmake_problem.txt).

This cmake problem was introduced after switching from Fedora 31 to Fedora 33 ?!

Any clue/idea why this is happening??? What is the cause of the problem?

Thank you,
Zoran
_______


4561 - 4580 of 58158