yocto@lists.yoctoproject.org

Re: Yocto recipe for Tailscale #yocto #golang

Mike Thompson <mthompson@...>

#50777

On Mon, Sep 21, 2020 at 10:31 AM, Randy MacLeod wrote:

Could you send your tailscale recipe to meta-openembedded/meta-networking?
Email: OpenEmbedded Development mailing list <openembedded-devel@...>
Instructions: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded

It looks like all the work is done aside from an email!

Sure. I'm traveling right now, but I'll look to do this in the next week or two.

Mike Thompson

Re: RDEPENDS problem

Greg Wilson-Lindberg

#50776

Hi Quentin,
It turns out that there was a problem in the build of the libcanfestival.so library that was adding in a reference to ../bin/....
This caused the failure that I asked about initially.

Thank you for your suggestions that then led me to figuring out the problem with the canfestival build.

Greg

Show quoted text

-----Original Message-----
From: Quentin Schulz <quentin.schulz@...>
Sent: Tuesday, September 22, 2020 1:20 AM
To: Greg Wilson-Lindberg <GWilson@...>
Cc: Yocto list discussion <yocto@...>
Subject: Re: [yocto] RDEPENDS problem

Hi Greg,

On Mon, Sep 21, 2020 at 09:46:51PM +0000, Greg Wilson-Lindberg wrote:

 I have a custom recipe that copies a .so, that libMotors.so calls functions inanother libcanfestival.so.

When I first added in the copy of the .so I didn't have an RDEPENDS
and Yocto printed out an warning listing the package that it wanted. I
added an RDEPENDS_${PN} with all of the packages listed, but I'm stillgetting an error for the first libMotors.so:

ERROR: userconfig-1.0-r0 do_package_qa: QA Issue:
/home/sakura/lib/libMotors.so.1.0.0 contained in package userconfig
requires libcanfestival.so, but no providers found in
RDEPENDS_userconfig? [file-rdeps]

In userdepends I added:

RDEPENDS_${PN} += "canfestival libelf libgcrypt pcsc-lite-lib qtbaseqtdeclarative qtserialport zint"

Package canfestival_3-asc in has:

FILES_${PN} = "/usr/lib/libcanfestival.so /usr/lib/libcanfestival_unix.so/usr/lib/libcanfestival_can_socket.so"
.so files are installed in the -dev package even with the line above.

Please have a look here:
https://wiki.yoctoproject.org/wiki/TipsAndTricks/Packaging_Prebuilt_Librarie
s#Non-versioned_Libraries
if there is really no way for you to avoid having a non-versioned library.First, the canfestival package that I have doesn't create versioned libraries, only the non-versioned .so's.

I changed the canfestival .bb to:

SOLIBS = ".so.*"
SOLIBSDEV = ".so"

FILES_${PN} = " ${libdir}/lib*${SOLIBSDEV}"
FILES_SOLIBSDEV ?= " ${libdir}/lib*${SOLIBSDEV}"
FILES_${PN}-dev = " /usr/include/canfestival/*.h  ${FILES_SOLIBSDEV}"

And I get the following error:

ERROR: canfestival-3-asc-r01 do_package_qa: QA Issue: -dev package contains non-symlink .so: canfestival-dev path '/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/canfestival/3-asc-r01/packages-split/canfestival-dev/usr/lib/libcanfestival_unix.so'
-dev package contains non-symlink .so: canfestival-dev path '/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/canfestival/3-asc-r01/packages-split/canfestival-dev/usr/lib/libcanfestival.so'
-dev package contains non-symlink .so: canfestival-dev path '/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/canfestival/3-asc-r01/packages-split/canfestival-dev/usr/lib/libcanfestival_can_socket.so' [dev-elf]
ERROR: canfestival-3-asc-r01 do_package_qa: QA run found fatal errors. Please consider fixing them.

I removed the ${FILES_SOLIBSDEV} from the FILES_${PN}-dev  and then I get:
WARNING: canfestival-3-asc-r01 do_package: canfestival-dev-3-asc was registered as shlib provider for ../bin/libcanfestival.so, changing it to canfestival-3-asc because it was built later
WARNING: canfestival-3-asc-r01 do_package: canfestival-dev-3-asc was registered as shlib provider for libcanfestival_can_socket.so, changing it to canfestival-3-asc because it was built later
WARNING: canfestival-3-asc-r01 do_package: canfestival-dev-3-asc was registered as shlib provider for libcanfestival_unix.so, changing it to canfestival-3-asc because it was built later
ERROR: userconfig-1.0-r0 do_package_qa: QA Issue: /home/sakura/lib/libMotors.so.1.0.0 contained in package userconfig requires libcanfestival.so, but no providers found in RDEPENDS_userconfig? [file-rdeps]
ERROR: userconfig-1.0-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.

It looks like the first warning is the key to the ERROR of not finding libcanfestival.so, but not getting errors for the other 2 libraries.

I looked in the build for canfestival and nowhere is there a bin/libcanfestival.so. Any ideas of how this could be created or referenced?

You can check if .so files are part of a package by using `oe-pkgdata-util find-
path /usr/lib/libcanfestival.so`

Cheers,
Quentin

Re: How to *properly* use SSTATE_DUPWHITELIST?

Richard Purdie

#50775

On Tue, 2020-09-22 at 16:40 -0400, Robert P. J. Day wrote:
Quoting "Robert P. J. Day" <rpjday@...>:

Never had cause to dig into SSTATE_DUPWHITELIST until now,
so a couple questions. (Side Note: This variable is not listed
in the YP Reference Manual variable glossary -- should it be?)

Ran across this as current project incorporates recipes
grpc-python and python-grpcio, which is problematic as the
latter is simply the renamed version of the former so, yeah,
that's definitely going to generate a ton of file install
conflicts.

The solution selected (and, yes, I know this is tacky and
gross and this should be fixed the right way) was to add
the line:

SSTATE_DUPWHITELIST = "/"

to python-grpcio.inc, which *seemed* to fix the problem,
until I started playing this morning to clarify what different
variations of this solution would do.

First oddity was that, after I added or deleted that line,
it seemed it made no difference in the rebuild of the
incorporating image, until I noticed this in
sstate.bbclass:

sstate_install[vardepsexclude] += "SSTATE_DUPWHITELIST ..."

which suggests that the sstate doesn't check dependency
based on SSTATE_DUPWHITELIST, so to get the change to kick in,
I did a "bitbake -c cleanall ..." on those recipes first,
and that seemed to do it.

But even that showed some weirdly non-deterministic behaviour,
as there seemed to be a difference based on which recipe I
added that line to, and which recipe I cleaned. So the
obvious question is, if I have two recipes that clash in
terms of installed files like these two, does one add that
line to either or both of the recipes? What does it mean to
add it to only one, and if that happens (as it did here),
how does that affect the eventual install? Does ordering then
matter?

In a general case, if I have, say, 5 recipes all of which
clash in the same place, do I add that line to all 5 recipes?
And if I don't, do I get undefined behaviour?   Oh, wait, I think I misunderstood this variable entirely --
it's not a per-recipe variable, is it? Its value represents the
combination over all recipes in the image, is that right? So
by adding the line:

SSTATE_DUPWHITELIST = "/"

I've effectively de-activated file conflict errors across the
entire rootfs and all recipes in the image, do I have that right?You are totally misunderstanding what this variable does. It has
nothing to do with images or rootfs. Its also definitely not per
recipe.

sstate has an overall view of any output 'deployed' in TMPDIR. For
example the sstate of the do_package_write_ipk tasks deploys the ipks
into DEPLOY_DIR_IPK. 

In a perfect world, no sstate should overwrite the sstate of anything
else.

In reality there are some corner cases where one set of sstate output
may overwrite another set. An example would be the sdk-provides-dummy-
target ipk/rpm files when multilib is enabled.

This variable controls whether these overlapping sstate files should be
allowed or whether they should be errors.

Documenting it is a low priority as either you understand the sstate
code internals and know how to use it or you probably shouldn't be
changing it.

Cheers,

Richard

Re: How to *properly* use SSTATE_DUPWHITELIST?

Robert P. J. Day

#50774

Quoting "Robert P. J. Day" <rpjday@...>:

Never had cause to dig into SSTATE_DUPWHITELIST until now,
so a couple questions. (Side Note: This variable is not listed
in the YP Reference Manual variable glossary -- should it be?)

Ran across this as current project incorporates recipes
grpc-python and python-grpcio, which is problematic as the
latter is simply the renamed version of the former so, yeah,
that's definitely going to generate a ton of file install
conflicts.

The solution selected (and, yes, I know this is tacky and
gross and this should be fixed the right way) was to add
the line:

SSTATE_DUPWHITELIST = "/"

to python-grpcio.inc, which *seemed* to fix the problem,
until I started playing this morning to clarify what different
variations of this solution would do.

First oddity was that, after I added or deleted that line,
it seemed it made no difference in the rebuild of the
incorporating image, until I noticed this in
sstate.bbclass:

sstate_install[vardepsexclude] += "SSTATE_DUPWHITELIST ..."

which suggests that the sstate doesn't check dependency
based on SSTATE_DUPWHITELIST, so to get the change to kick in,
I did a "bitbake -c cleanall ..." on those recipes first,
and that seemed to do it.

But even that showed some weirdly non-deterministic behaviour,
as there seemed to be a difference based on which recipe I
added that line to, and which recipe I cleaned. So the
obvious question is, if I have two recipes that clash in
terms of installed files like these two, does one add that
line to either or both of the recipes? What does it mean to
add it to only one, and if that happens (as it did here),
how does that affect the eventual install? Does ordering then
matter?

In a general case, if I have, say, 5 recipes all of which
clash in the same place, do I add that line to all 5 recipes?
And if I don't, do I get undefined behaviour?  Oh, wait, I think I misunderstood this variable entirely --
it's not a per-recipe variable, is it? Its value represents the
combination over all recipes in the image, is that right? So
by adding the line:

SSTATE_DUPWHITELIST = "/"

I've effectively de-activated file conflict errors across the
entire rootfs and all recipes in the image, do I have that right?

rday

How to *properly* use SSTATE_DUPWHITELIST?

Robert P. J. Day

#50773

Never had cause to dig into SSTATE_DUPWHITELIST until now,
so a couple questions. (Side Note: This variable is not listed
in the YP Reference Manual variable glossary -- should it be?)

Ran across this as current project incorporates recipes
grpc-python and python-grpcio, which is problematic as the
latter is simply the renamed version of the former so, yeah,
that's definitely going to generate a ton of file install
conflicts.

The solution selected (and, yes, I know this is tacky and
gross and this should be fixed the right way) was to add
the line:

SSTATE_DUPWHITELIST = "/"

to python-grpcio.inc, which *seemed* to fix the problem,
until I started playing this morning to clarify what different
variations of this solution would do.

First oddity was that, after I added or deleted that line,
it seemed it made no difference in the rebuild of the
incorporating image, until I noticed this in
sstate.bbclass:

sstate_install[vardepsexclude] += "SSTATE_DUPWHITELIST ..."

which suggests that the sstate doesn't check dependency
based on SSTATE_DUPWHITELIST, so to get the change to kick in,
I did a "bitbake -c cleanall ..." on those recipes first,
and that seemed to do it.

But even that showed some weirdly non-deterministic behaviour,
as there seemed to be a difference based on which recipe I
added that line to, and which recipe I cleaned. So the
obvious question is, if I have two recipes that clash in
terms of installed files like these two, does one add that
line to either or both of the recipes? What does it mean to
add it to only one, and if that happens (as it did here),
how does that affect the eventual install? Does ordering then
matter?

In a general case, if I have, say, 5 recipes all of which
clash in the same place, do I add that line to all 5 recipes?
And if I don't, do I get undefined behaviour?

rday

M+ & H bugs with Milestone Movements WW38

Stephen Jolley

#50772

All,

YP M+ or high bugs which moved to a new milestone in WW38 are listed below:

Priority	Bug ID	Short Description	Changer	Owner	Was	Became
High	14027	bitbake cooker processes left hanging at exit	randy.macleod@...	richard.purdie@...	3.2 M3	3.2 M4
Medium+	5389	bitbake/lib/bb/fetch2: filename too long	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	8805	Detect and warn people naming functions something_remove_something	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	10061	Ctrl+C during BB_HASHCHECK_FUNCTION execution does not interrupt processing nicely	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	10731	bitbake --observe-only doesn't work with memres	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	11781	bitbake --observe-only may get KeyError	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	11899	broken 'bitbake --status-only' and 'bitbake -m'	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	12023	bitbake-layers show-layers doesn't show layer if it doesn't append itself to BBFILE_COLLECTIONS	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	12290	cross recipe kernel module dependency generation stopped working	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	12374	do_rootfs failed when len(TMPDIR) == 410	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	12367	moving or removing tmp breaks persistent bitbake server	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	12963	nativesdk-opkg prefixes all internal paths with $SDKPATH and won't work	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	13039	fetch2: PREMIRROR and SRC_URI with type https and parameter downloadfilename yields invalid url	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	13181	persist_data sqlite database mixed with forking is irreparably broken	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	13236	sstate for host native packages	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	13279	Make sure users/groups exist for package_write_* tasks	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	13306	bitbake starts up to n^2 processes with n cpus	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	13353	bitbake git fetcher does not honour BB_FETCH_PREMIRRORONLY	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	13411	ptest-perl.bbclass run-ptest is too greedy for SKIP	timothy.t.orling@...	timothy.t.orling@...	3.2 M3	3.3 M1
	13419	recipes that add users to groups cannot rely on other recipes creating those groups (when population from sstate happens)	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	13646	runtime tests sometimes can't login to the serial console on systemd images (generates warning)	richard.purdie@...	kai.kang@...	3.2 M4	3.2 M3
	13690	runqemu with slirp, forwarded host ports are not available on host	timothy.t.orling@...	timothy.t.orling@...	3.2 M3	3.2 M4
	13705	master] bitbake and hashserve.sock left behind when ^C a build	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	13803	devtool setupClass file copying race	timothy.t.orling@...	timothy.t.orling@...	3.2 M3	3.2 M4
	13843	bitbake worker stuck using 100% cpu on aborted build	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	13868	Python cache files get lost in packages	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	13897	POSTINST_INTERCEPTS_DIR broken by undocumented POSTINST_INTERCEPTS_PATHS since thud	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	13910	Intermittent host UID contamination highlighted by devtool tests	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	13919	Multi License GPLv3 -lic cannot be installed into the image because it has incompatible license	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	13920	uninative tarball license compliance in ESDK	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	13929	toaster-container has been broken since morty	timothy.t.orling@...	timothy.t.orling@...	3.2 M3	3.2 M4
	13930	Port the CROPS toaster-container selenium tests to the Autobuilder	timothy.t.orling@...	timothy.t.orling@...	3.2 M3	3.3 M1
	13938	devtool modify virtual/kernel fails when EXTRAVERSION field is empty in Makefile	timothy.t.orling@...	timothy.t.orling@...	3.2 M3	3.2 M4
	13976	gdb8.3 do compile with musl is error	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	13993	tinfoil error handling during server startup suboptimal	randy.macleod@...	unassigned@...	3.2 M3	3.2 M4
	13994	wic is modifying /etc/fstab in place, which races with other image type tasks	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	13998	Changing create_sdk_files doesn't rebuild buildtools-tarball	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1
	14015	URL Arguments in MIRROR/PREMIRROR get encoded	randy.macleod@...	unassigned@...	3.2 M3	3.3 M1

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

( Cell: (208) 244-4460

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

Enhancements/Bugs closed WW38!

Stephen Jolley

#50771

All,

The below were the owners of enhancements or bugs closed during the last week!

Who	Count
akuster808@...	1
randy.macleod@...	1
Grand Total	2

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

( Cell: (208) 244-4460

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

Yocto Project Status WW38'20

Stephen Jolley

#50770

Current Dev Position: YP 3.2 M4

Next Deadline: YP 3.2 M4 Feature Freeze - Now

Next Team Meetings:

Bug Triage meeting Thursday Sept. 24th at 7:30am PDT (https://zoom.us/j/454367603)
Monthly Project Meeting Tuesday Oct. 6th at 8am PDT (https://zoom.us/j/990892712)
Weekly Engineering Sync Tuesday Sept. 23th at 8am PDT (https://zoom.us/j/990892712)
Twitch - See https://www.twitch.tv/theyoctojester

Key Status/Updates:

M3 rc1 has been built and been through QA. Unfortunately beaglebone fails to boot so we’ll have to go to an rc2. There were 4 other issues reported by QA too (3 ptest regressions and a bitbake UI issue).
We plan to build 3.1.3 imminently
The sphinx documentation transition has merged. There is still work needed to clean up various links and other conversion glitches as well as areas the manual needs to be brought up to date. Any help much appreciated. Big thanks to Nico for driving this!
The new documentation can be seen at https://docs.yoctoproject.org/,
One significant potential cause for autobuilder timeout issues has been identified, potentially the journal on ext4 filesystems was causing IO prioritisation to fail as the journal only runs with one IO level. We’ve modified the journal options on autobuilder workers to be “writeback” to avoid this. This should reduce autobuilder bitbake timeout issues.
Two of the three significant autobuilder issues mentioned last week remain:

qemumips fails with systemd with 256MB memory, it needs 512MB. If we enable 512MB, we see random hangs. Unless someone can debug and sort the qemu memory issues, we may end up disabling core-image-sato-sdk and core-image-full-cmdline for qemumips+systemd
networking with qemu images appears to glitch at times (particularly slower targets such as ltp and qemumips), the session stalls with “no route to host”. We need better serial interrogation to determine the state of qemu when this happens, it's unclear if qemu/kernel hangs, networking fails or what is breaking. Help to add this extra debugging would be much appreciated.

There are new autobuilder issues this week, a pseudo bug appears to be being exposed as well as new intermittent issues, as yet not looked into.
We continue to struggle with a number of autobuilder intermittent bugs. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

Help with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing.

Ways to contribute:

There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
There are bugs that are currently unassigned for YP 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
We’d welcome new maintainers for recipes in OE-Core. Please see the list at: http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc and discuss with the existing maintainer, or ask on the OE-Core mailing list. We will likely move a chunk of these to “Unassigned” soon to help facilitate this.

YP 3.2 Milestone Dates:

YP 3.2 M3 is out of QA and will be rebuilt
YP 3.2 M4 build date 2020/10/5
YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

YP 3.1.3 build date 2020/9/14
YP 3.1.3 release date 2020/9/25
YP 3.1.4 build date 2020/11/2
YP 3.1.4 release date 2020/11/13

Tracking Metrics:

WDD 2469 (last week 2466) (https://wiki.yoctoproject.org/charts/combo.html)
Poky Patch Metrics

Total patches found: 1268 (last week 1258)
Patches in the Pending State: 496 (39%) [last week 496 (39%)]

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC

The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status

[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

( Cell: (208) 244-4460

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

Current Autobuilder Intermittent bugs by the WW created or closed.

Stephen Jolley

#50769

All,

Below are the lists of open and closed medium or higher Autobuilder Intermittent bugs by the WW created or closed'.

Opened	Count	Closed	Count
2019WW47	1	2020WW26	2
2020WW8	1	2020WW27	2
2020WW24	1	2020WW28	3
2020WW25	1	2020WW29	2
2020WW29	1	2020WW30	3
2020WW30	1	2020WW31	1
2020WW31	2	2020WW33	1
2020WW33	5	2020WW34	4
2020WW34	2	2020WW35	1
2020WW35	3	2020WW37	2
2020WW36	3	Grand Total	21
2020WW37	1
Grand Total	22

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

( Cell: (208) 244-4460

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

Current high bug count owners for Yocto Project 3.2

Stephen Jolley

#50768

All,

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

Who	Count
richard.purdie@...	33
david.reyna@...	23
bruce.ashfield@...	18
akuster808@...	18
ross@...	17
bluelightning@...	17
mark.morton@...	11
kai.kang@...	10
sakib.sajal@...	10
JPEWhacker@...	10
trevor.gamblin@...	9
Qi.Chen@...	9
timothy.t.orling@...	9
raj.khem@...	5
hongxu.jia@...	5
randy.macleod@...	5
rpjday@...	4
mostthingsweb@...	4
mingli.yu@...	4
yi.zhao@...	3
jon.mason@...	3
jeanmarie.lemetayer@...	2
alejandro@...	2
michael@...	2
ydirson@...	2
jaewon@...	2
jpuhlman@...	2
steve@...	2
chee.yang.lee@...	2
kergoth@...	2
mark.hatle@...	2
khairul.rohaizzat.jamaluddin@...	1
joe.slater@...	1
liu.ming50@...	1
kai.ruhnau@...	1
akuster@...	1
Martin.Jansa@...	1
jason.wessel@...	1
kexin.hao@...	1
anuj.mittal@...	1
amber.n.elliot@...	1
maxime.roussinbelanger@...	1
changqing.li@...	1
matt.ranostay@...	1
ankur.tyagi85@...	1
aehs29@...	1
dl9pf@...	1
liezhi.yang@...	1
Grand Total	264

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

#50767

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

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 334 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@...

Re: QA notification for completed autobuilder build (yocto-3.2_M3.rc1)

Sangeeta Jain

#50766

Hello all,

This is the full report for yocto-3.2_M3.rc1:  
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults

======= Summary ========
Beaglebone can not boot up, hence all beaglebone test case are blocked in this release.
No high milestone defects.
  
2 new defects and 3 ptest failures are found:

1. The beaglebone can not bootup (BUG id:14052)
This bug blocked all beaglebone test cases.
2. failure in oe-core manual test: test_dependency_explorer_is_launched (BUG id:14055)
3. valgrind ptest failed (BUG id:14051)
4. parted ptest failed (BUG id:14050)
5. pango ptest failed (BUG id:14049)

======= Bugs ========
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14052
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14055
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14051
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14050
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14049 This is the full report for yocto-3.2_M3.rc1:  
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults

Thanks,
Sangeeta

Show quoted text

-----Original Message-----
From: Pokybuild User <pokybuild@...>
Sent: Friday, 18 September, 2020 12:18 AM
To: yocto@...
Cc: otavio@...; yi.zhao@...; Sangal, Apoorv
<apoorv.sangal@...>; Yeoh, Ee Peng <ee.peng.yeoh@...>;
Chan, Aaron Chun Yew <aaron.chun.yew.chan@...>;
richard.purdie@...; akuster808@...;
sjolley.yp.pm@...; Jain, Sangeeta <sangeeta.jain@...>
Subject: QA notification for completed autobuilder build (yocto-3.2_M3.rc1)


A build flagged for QA (yocto-3.2_M3.rc1) was completed on the autobuilder
and is available at:


    https://autobuilder.yocto.io/pub/releases/yocto-3.2_M3.rc1


Build hash information:

bitbake: 29081375659e3dcf1c578cd98ab2c8a2e9f07ca8
meta-arm: 1f3cf5812c91cdc15f63737bf9b30cce665b2999
meta-gplv2: a8da8eb127a56561bf633ab53bec57fb5dbba537
meta-intel: f7580d72763653893c06e1d9ece7a77c4adb8485
meta-kernel: cb7f0dc5bb1ea0998c8d4fcb486148d4cab575f4
meta-mingw: 30a051401c0a73dfff486ca4d0303b434816200f
oecore: 4e7506882cabf3936f0269c2a98f61c7d595d613
poky: c6bc20857cd1bdfd25dfc50e413be84d1d12b189



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.purdie@...

[meta-zephyr][PATCH v3] zephyr-kernel: add Zephyr RTOS version 2.3.0 support

yock.gen.mah@...

#50765

From: "Mah, Yock Gen" <yock.gen.mah@...>

Signed-off-by: Mah, Yock Gen <yock.gen.mah@...>
---
 classes/zephyr-kernel-src.bbclass             | 16 ++++++---
 .../{qemu_4.2.%.bbappend => qemu_%.bbappend}  |  0
 .../zephyr-kernel/zephyr-kernel-common.inc    |  3 +-
 .../zephyr-kernel/zephyr-kernel-src_2.2.bb    | 33 -------------------
 .../zephyr-kernel/zephyr-kernel-src_2.3.bb    | 24 ++++++++++++++
 .../zephyr-kernel/zephyr-kernel-test.inc      |  5 ++-
 6 files changed, 39 insertions(+), 42 deletions(-)
 rename recipes-devtools/qemu/{qemu_4.2.%.bbappend => qemu_%.bbappend} (100%)
 delete mode 100644 recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb
 create mode 100644 recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb

diff --git a/classes/zephyr-kernel-src.bbclass b/classes/zephyr-kernel-src.bbclass
index 653cb9b..50e46af 100644
--- a/classes/zephyr-kernel-src.bbclass
+++ b/classes/zephyr-kernel-src.bbclass
@@ -1,13 +1,19 @@
 #Set relevant variables based on Zephyr kernel version
 
-PREFERRED_VERSION_zephyr-kernel ??= "2.2.0"
+PREFERRED_VERSION_zephyr-kernel ??= "2.3.0"
 
-SRCREV = "d39cb42d0920d5658fad358ad5b91de75d747a20"
+SRCREV_FORMAT = "default_cmsis"
+SRCREV_default  = "b8c78e254ff875680e99c9f131fbe285c4575927"
+SRCREV_cmsis = "542b2296e6d515b265e25c6b7208e8fea3014f90"
 
-SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.2-branch \
+
+SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.3-branch;name=default \
+           git://github.com/zephyrproject-rtos/cmsis.git;protocol=https;destsuffix=git/modules/cmsis;name=cmsis \
           file://0001-cmake-add-yocto-toolchain.patch \
         "
-PV = "2.2.0"
+
+PV = "2.3.0+git${SRCPV}"
+
 LICENSE = "Apache-2.0"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=fa818a259cbed7ce8bc2a22d35a464fc"
 
@@ -15,7 +21,7 @@ ZEPHYR_TEST_SRCDIR = "tests/legacy/kernel/"
 
 python () {
     src_pn = d.getVar('PREFERRED_VERSION_zephyr-kernel', True)
-    if src_pn == '2.2.0':
+    if src_pn == '2.3.0':
         return
     else:
         bb.error("Unsupported Zephyr kernel version requested")
diff --git a/recipes-devtools/qemu/qemu_4.2.%.bbappend b/recipes-devtools/qemu/qemu_%.bbappend
similarity index 100%
rename from recipes-devtools/qemu/qemu_4.2.%.bbappend
rename to recipes-devtools/qemu/qemu_%.bbappend
diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
index 7e569ed..7fa4b25 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
@@ -15,13 +15,14 @@ ZEPHYR_MAKE_OUTPUT = "zephyr.elf"
 
 
 EXTRA_OECMAKE = " -DZEPHYR_BASE=${S} -DZEPHYR_GCC_VARIANT=yocto -DBOARD=${BOARD} -DARCH=${ARCH} -DCROSS_COMPILE=${CROSS_COMPILE} -DZEPHYR_SYSROOT=${ZEPHYR_SYSROOT} -DZEPHYR_TOOLCHAIN_VARIANT=yocto"
+EXTRA_OECMAKE_append_arm = " -DZEPHYR_MODULES=${S}/modules/cmsis"
 export ZEPHYR_BASE="${S}"
 
 
 # We always need a toolchain to cross-compile.
 INHIBIT_DEFAULT_DEPS = "1"
 DEPENDS += "gcc-cross-${TARGET_ARCH} libgcc ${TOOLCHAIN_TARGET_TASK} gperf-native"
-DEPENDS += " python3-pyelftools-native python3-pyyaml-native"
+DEPENDS += " python3-pyelftools-native python3-pyyaml-native python3-pykwalify-native"
 CROSS_COMPILE = "${STAGING_BINDIR_TOOLCHAIN}/${TARGET_PREFIX}"
 
 DEPENDS_append_qemuall = " qemu-native qemu-helper-native"
diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb
deleted file mode 100644
index a3e1c28..0000000
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb
+++ /dev/null
@@ -1,33 +0,0 @@
-
-LICENSE = "Apache-2.0"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=fa818a259cbed7ce8bc2a22d35a464fc"
-
-# tag v2.2
-SRCREV="d39cb42d0920d5658fad358ad5b91de75d747a20"
-SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.2-branch \
-          file://0001-cmake-add-yocto-toolchain.patch \
-        "
-inherit cmake 
-PV = "2.2.0"
-S = "${WORKDIR}/git"
-
-IMAGE_NO_MANIFEST = "1"
-INHIBIT_DEFAULT_DEPS = "1"
-
-do_configure[noexec] = "1"
-do_compile[noexec] = "1"
-
-do_compile () {
-}
-
-do_install () {
-    kerneldir=${D}/usr/src/zephyr
-    install -d $kerneldir
-    cp -r ${S}/* $kerneldir
-}
-
-PACKAGES = "${PN}"
-FILES_${PN} = "/usr/src/zephyr"
-
-SYSROOT_DIRS += "/usr/src/zephyr"
-
diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb
new file mode 100644
index 0000000..8e8b5b8
--- /dev/null
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb
@@ -0,0 +1,24 @@
+
+inherit zephyr-kernel-src
+inherit cmake
+
+S = "${WORKDIR}/git"
+
+IMAGE_NO_MANIFEST = "1"
+INHIBIT_DEFAULT_DEPS = "1"
+
+do_configure[noexec] = "1"
+do_compile[noexec] = "1"
+
+
+do_install () {
+    kerneldir=${D}/usr/src/zephyr
+    install -d $kerneldir
+    cp -r ${S}/* $kerneldir
+}
+
+PACKAGES = "${PN}"
+FILES_${PN} = "/usr/src/zephyr"
+
+SYSROOT_DIRS += "/usr/src/zephyr"
+
diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc
index 65da7e8..faf28bd 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc
@@ -1,4 +1,4 @@
-ZEPHYRTESTS_remove = "fifo fp_sharing lifo mbox mem_heap mem_pool \
+ZEPHYRTESTS_remove = "fifo fpu_sharing lifo mbox mem_heap mem_pool \
     mem_protect mem_slab msgq mutex pipe profiling sched semaphore \
     stack threads tickless timer workq"
 
@@ -23,12 +23,11 @@ ZEPHYRTESTS_remove = "gen_isr_table spinlock smp mp"
 ZEPHYRTESTS = " \
     common \
     context \
-    critical \
     device \
     early_sleep \
     fatal \
     fifo \
-    fp_sharing \
+    fpu_sharing \
     gen_isr_table \
     interrupt \
     lifo \
-- 
2.25.1

Re: RDEPENDS problem

Quentin Schulz

#50764

Hi Greg,

On Mon, Sep 21, 2020 at 09:46:51PM +0000, Greg Wilson-Lindberg wrote:

 I have a custom recipe that copies a .so, that libMotors.so calls functions in another libcanfestival.so.

When I first added in the copy of the .so
I didn't have an RDEPENDS and Yocto printed out an warning listing the package that it wanted. I added an RDEPENDS_${PN} 
with all of the packages listed, but I'm still getting an error for the first libMotors.so:

ERROR: userconfig-1.0-r0 do_package_qa: QA Issue: /home/sakura/lib/libMotors.so.1.0.0 contained in package userconfig requires libcanfestival.so, but no providers found in RDEPENDS_userconfig? [file-rdeps]

In userdepends I added:

RDEPENDS_${PN} += "canfestival libelf libgcrypt pcsc-lite-lib qtbase qtdeclarative qtserialport zint"

Package canfestival_3-asc in has:

FILES_${PN} = "/usr/lib/libcanfestival.so /usr/lib/libcanfestival_unix.so /usr/lib/libcanfestival_can_socket.so"
.so files are installed in the -dev package even with the line above.

Please have a look here: https://wiki.yoctoproject.org/wiki/TipsAndTricks/Packaging_Prebuilt_Libraries#Non-versioned_Libraries
if there is really no way for you to avoid having a non-versioned library.

You can check if .so files are part of a package by using
`oe-pkgdata-util find-path /usr/lib/libcanfestival.so`

Cheers,
Quentin

Re: #yocto systemd not able to start sshd after a reboot #yocto

Khem Raj

#50763

On 9/21/20 5:17 AM, srijan.nandi@... wrote:
    /Seems that some leftovers from System V still reside in YOCTO...
    Correct???Yocto project supports sysvinit as init system option as well so no there are no leftovers.

    /
Not sure about that.
The problem I faced was because there was a sshd.socket that had the following line in it. The sshd.socket comes with openssh.
Conflicts=sshd.service
So I had two options. either to add the ExecStartPre in the sshd.service file or to remove the Conflicts line in sshd.socket.
I choose to remove the Conflicts line and add the following in the sshd.socket file.
After=network.target
Before=sshd.serviceUsually you use socket activation for sshd then you would enable sshd.socket and not sshd.service, socket will be listening on incoming connections on ssh port ( 22  by defaault ) and launch sshd.service whenever there is incoming ssh connection request. I suggest you should perhaps follow this approach as well, its also efficient due to its on-demand launch nature.

Thanks and Regards,
-=Srijan Nandi

Re: preistall package when use a package manager

Khem Raj

#50762

On 9/21/20 1:28 AM, Matteo Facchinetti wrote:
Hi,
I need to preinstall a package in a specific directory in my target image.
In detail I use RPM package manager and I like to include RPM packages in my target to provide a way to install services only when used.
This is useful when you don't have an internet connection.
Is there a way to do this?
Opinions are welcome.it seems you want to bundle unstalled packages ( rpms ) in your firmware, perhaps you can look at adding a ROOTFS_POSTPROCESS_COMMAND and copy the needed packages, but you need to be sure that all dependencies(rpms) are also made available as part of this bundle
and you have to check this consistency everytime you update firmware


Regards,
Matteo
Sirius Electronic Systems

Re: RDEPENDS problem

Maciej Pijanowski

#50761

On 21.09.2020 23:46, Greg Wilson-Lindberg wrote:

 I have a custom recipe that copies a .so, that libMotors.so calls functions in another libcanfestival.so.

When I first added in the copy of the .so
I didn't have an RDEPENDS and Yocto printed out an warning listing the package that it wanted. I added an RDEPENDS_${PN} 
with all of the packages listed, but I'm still getting an error for the first libMotors.so:

ERROR: userconfig-1.0-r0 do_package_qa: QA Issue: /home/sakura/lib/libMotors.so.1.0.0 contained in package userconfig requires libcanfestival.so, but no providers found in RDEPENDS_userconfig? [file-rdeps]

In userdepends I added:

RDEPENDS_${PN} += "canfestival libelf libgcrypt pcsc-lite-lib qtbase qtdeclarative qtserialport zint"

Package canfestival_3-asc in has:

FILES_${PN} = "/usr/lib/libcanfestival.so /usr/lib/libcanfestival_unix.so /usr/lib/libcanfestival_can_socket.so"

which seems to me like it should satisfy the requirements of the RDEPENDS, but it is not. bitbake initially gave me a warning 
that listed canfestival as needing to be added to an RDEPENDS for userconfig. But now it is saying that it can't figure out
what package supplies the libcanfestival.so file.

Can someone help me to understand what is going on? How do I explicitly say that a package supplies a given file?

You could try with PROVIDES: https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-PROVIDES

-- 
Maciej Pijanowski
Embedded Systems Engineer
GPG: 9963C36AAC3B2B46
https://3mdeb.com | @3mdeb_com

[meta-zephyr][morty PATCH] zephyr-kernel: update URLs

Jon Mason

#50760

URLs no longer point to a valid location.  Update to the current
location.

Signed-off-by: Jon Mason <jon.mason@...>
---
 classes/zephyr-kernel-src.bbclass                     | 2 +-
 recipes-kernel/zephyr-kernel/zephyr-kernel-src_1.6.bb | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/classes/zephyr-kernel-src.bbclass b/classes/zephyr-kernel-src.bbclass
index d7aa81bfaa62..cd1503dc1299 100644
--- a/classes/zephyr-kernel-src.bbclass
+++ b/classes/zephyr-kernel-src.bbclass
@@ -3,7 +3,7 @@
 PREFERRED_VERSION_zephyr-kernel ??= "1.6.0"
 
 SRCREV = "d4e799d77a36eaf6d678b357c207411ec32b2d62"
-SRC_URI = "git://gerrit.zephyrproject.org/r/zephyr.git;protocol=https;branch=v1.6.0-branch \
+SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v1.6-branch \
           file://Makefile.toolchain.yocto "
 PV = "1.6.0"
 
diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_1.6.bb b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_1.6.bb
index df373e850c94..b47e8ac1b7d0 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_1.6.bb
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_1.6.bb
@@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=fa818a259cbed7ce8bc2a22d35a464fc"
 
 # tag v1.6.0
 SRCREV="d4e799d77a36eaf6d678b357c207411ec32b2d62"
-SRC_URI = "git://gerrit.zephyrproject.org/r/zephyr.git;protocol=https;branch=v1.6.0-branch"
+SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v1.6-branch"
 SRC_URI += "file://Makefile.toolchain.yocto"
 
 PV = "1.6.0"
-- 
2.20.1

[meta-zephyr][PATCH] zephyr-kernel: Add python dependencies

Jon Mason

#50759

Zephyr refuses to compile due to missing python dependencies.

Signed-off-by: Jon Mason <jon.mason@...>
Signed-off-by: Ross Burton <ross.burton@...>
---
 recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
index d7147d5b7b86..7e569edb694c 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
@@ -2,6 +2,7 @@
 
 ZEPHYR_INHERIT_CLASSES += "zephyr cmake"
 inherit ${ZEPHYR_INHERIT_CLASSES}
+inherit python3native
 
 # There shouldn't be a manifest for zephyr kernels since there is no root
 # filesystem.
@@ -20,6 +21,7 @@ export ZEPHYR_BASE="${S}"
 # We always need a toolchain to cross-compile.
 INHIBIT_DEFAULT_DEPS = "1"
 DEPENDS += "gcc-cross-${TARGET_ARCH} libgcc ${TOOLCHAIN_TARGET_TASK} gperf-native"
+DEPENDS += " python3-pyelftools-native python3-pyyaml-native"
 CROSS_COMPILE = "${STAGING_BINDIR_TOOLCHAIN}/${TARGET_PREFIX}"
 
 DEPENDS_append_qemuall = " qemu-native qemu-helper-native"
-- 
2.20.1

RDEPENDS problem

Greg Wilson-Lindberg

#50758

I have a custom recipe that copies a .so, that libMotors.so calls functions in another libcanfestival.so.

When I first added in the copy of the .so
I didn't have an RDEPENDS and Yocto printed out an warning listing the package that it wanted. I added an RDEPENDS_${PN} 
with all of the packages listed, but I'm still getting an error for the first libMotors.so:

ERROR: userconfig-1.0-r0 do_package_qa: QA Issue: /home/sakura/lib/libMotors.so.1.0.0 contained in package userconfig requires libcanfestival.so, but no providers found in RDEPENDS_userconfig? [file-rdeps]

In userdepends I added:

RDEPENDS_${PN} += "canfestival libelf libgcrypt pcsc-lite-lib qtbase qtdeclarative qtserialport zint"

Package canfestival_3-asc in has:

FILES_${PN} = "/usr/lib/libcanfestival.so /usr/lib/libcanfestival_unix.so /usr/lib/libcanfestival_can_socket.so"

which seems to me like it should satisfy the requirements of the RDEPENDS, but it is not. bitbake initially gave me a warning 
that listed canfestival as needing to be added to an RDEPENDS for userconfig. But now it is saying that it can't figure out
what package supplies the libcanfestival.so file.

Can someone help me to understand what is going on? How do I explicitly say that a package supplies a given file?