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 WW18 of who have open medium or higher bugs and enhancements against YP 3.4.   There are 125 possible work days left until the final release candidates for YP 3.4 needs to be released.

Who

Count

richard.purdie@...

30

ross@...

28

david.reyna@...

22

bruce.ashfield@...

20

michael.opdenacker@...

17

trevor.gamblin@...

13

bluelightning@...

12

timothy.t.orling@...

12

akuster808@...

11

randy.macleod@...

11

sakib.sajal@...

10

JPEWhacker@...

10

kai.kang@...

8

hongxu.jia@...

7

raj.khem@...

6

chee.yang.lee@...

6

Qi.Chen@...

6

mingli.yu@...

5

yi.zhao@...

4

saul.wold@...

3

mostthingsweb@...

3

pokylinux@...

2

stacygaikovaia@...

2

ydirson@...

2

nicolas.dechesne@...

2

mshah@...

2

jon.mason@...

2

alejandro@...

2

alexandre.belloni@...

2

jaewon@...

2

yf3yu@...

2

john.kaldas.enpj@...

1

changqing.li@...

1

mhalstead@...

1

open.source@...

1

yoctoproject@...

1

liezhi.yang@...

1

devendra.tewari@...

1

prabin.ca@...

1

shachar@...

1

Martin.Jansa@...

1

mister_rs@...

1

jeanmarie.lemetayer@...

1

victor.kamensky7@...

1

aehs29@...

1

kexin.hao@...

1

matthewzmd@...

1

dl9pf@...

1

naveen.kumar.saini@...

1

diego.sueiro@...

1

Nathan.Dunne@...

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

 


Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am on the first Tuesday (PDT)

Stephen Jolley
 

All,

 

Just a reminder we will hold the monthly Yocto Project Technical Meeting at 8am PST tomorrow. (5/4) 

 

Yocto Project Technical Team Meeting: We encourage people attending the meeting to logon and announce themselves on the Yocto Project IRC chancel during the meeting (optional):

Yocto IRC: http://webchat.freenode.net/?channels=#yocto

 

Wiki: https://www.yoctoproject.org/public-virtual-meetings/

 

When            Monthly from 8am to 9am on the first Tuesday Pacific Time

Where           Zoom Meeting: https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09

 

We are tracking the minutes at: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit?pli=1 Please request access if you want to assist in editing them.  The world should have view access.

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Re: Criteria for bitbake to skip recipes #bitbake

Randy MacLeod
 

On 2021-04-26 12:25 p.m., keydi wrote:
I wonder what are all possible criteria for Bitbake to decide to skip recipe (please compare to reports delivered by bitbake-layers). Recipe overlay, recipe version, others? Which knowledge source to find more details in?
I'm not aware of a specific list but two that come to mind are,
(in meta-openembedded):

$ rgrep PNBLACKLIST meta-*| wc -l
10
$ rgrep COMPATIBLE_HOST meta-*| wc -l
115


Maybe you can explain why you want to know why bitbake would skip a
recipe and that will help us to help you.



../Randy




--
# Randy MacLeod
# Wind River Linux


SSH_AUTH_SOCK unavailable when pulling modules #golang

Sven
 

Hi,

I have put together a recipe inheriting from go-mod. This project depends on out-of-repo modules that sit in private repos. As long as the SSH key required to pull the requirements is present as a file (under $HOME/.ssh), everything works fine. However, as soon as the SSH credentials are only available via agent and $SSH_AUTH_SOCK, the do_compile step fails. I have traced this down to the fact that the $SSH_AUTH_SOCK environment variable is not available to do_compile which is when the requirements are pulled. This is the sort of error message I get:

ERROR: mypackage-git-r0 do_compile: Execution of '[...]/mypackage/git-r0/temp/run.do_compile.20076' failed with exit code 1:
# cd .; git ls-remote https://bitbucket.org/myorg/some-requirement
Permission denied (publickey).
fatal: Could not read from remote repository.

Note, that the do_fetch step succeeds in pulling the actual repo. I tried fixing the problem by wrapping the do_compile function and providing $SSH_AUTH_SOCK from the original environment:

def origenv(d, var):
return d.getVar("BB_ORIGENV", False).getVar(var, False)

do_compile() {
if [ -n "${@origenv(d, 'SSH_AUTH_SOCK') or ''}" ]; then
export SSH_AUTH_SOCK="${@origenv(d, 'SSH_AUTH_SOCK')}"
fi
go_do_compile
}

This allows the do_compile step (and all subsequent steps) to finish successfully. However, that way, I get a bunch of errors like this (cleansstate does not help):

ERROR: When reparsing [...]/mypackage_git.bb:do_compile, the basehash value changed from eb51e4ec321c723587cec03bb9b33b94ee43e0b0939eb43b52824e3d5cfebec2 to 2bb034f43856917d6454a56b32946b1c68cf7f286b20fd7a7eaf1bfd2a92d34f. The metadata is not deterministic and this needs to be fixed.
ERROR: The following commands may help:
ERROR: $ bitbake mypackage -cdo_compile -Snone
ERROR: Then:
ERROR: $ bitbake mypackage -cdo_compile -Sprintdiff

Neither command helps to fix this. What can I do? I'm on poky yocto-3.1.5-18-gbb7747497a.

Best regards,
Sven


Re: [meta-gplv2][PATCH] elfutils: ignore format-truncation and stringop-overflow issues to fix build with gcc-11

Khem Raj
 

On 5/2/21 11:41 PM, Martin Jansa wrote:
* works around:
http://errors.yoctoproject.org/Errors/Details/580076/
elfutils-0.148/src/ar.c:1088:56: error: '%-*ld' directive output may be truncated writing between 6 and 10 bytes into a region of size 7 [-Werror=format-truncation=]
1088 | snprintf (tmpbuf, sizeof (tmpbuf), ofmt ? "%-*lo" : "%-*ld", bufsize, val);
| ^~~~~
elfutils-0.148/src/ar.c:1088:55: note: directive argument in the range [0, 4294967295]
1088 | snprintf (tmpbuf, sizeof (tmpbuf), ofmt ? "%-*lo" : "%-*ld", bufsize, val);
| ^~~~~~~
http://errors.yoctoproject.org/Errors/Details/580078/
elfutils-0.148/tests/addrcfi.c:90:16: error: 'dwarf_frame_register' accessing 96 bytes in a region of size 64 [-Werror=stringop-overflow=]
90 | int result = dwarf_frame_register (stuff->frame, regno, ops_mem, &ops, &nops);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
looks ok. Thanks for fixing it

Signed-off-by: Martin Jansa <Martin.Jansa@...>
---
recipes-devtools/elfutils/elfutils_0.148.bb | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/recipes-devtools/elfutils/elfutils_0.148.bb b/recipes-devtools/elfutils/elfutils_0.148.bb
index 1f07a28..654a715 100644
--- a/recipes-devtools/elfutils/elfutils_0.148.bb
+++ b/recipes-devtools/elfutils/elfutils_0.148.bb
@@ -61,6 +61,14 @@ inherit autotools gettext
# but 0.175 has different license, so to be safe don't backport the fix, just ignore the issue
CFLAGS += "-Wno-error=missing-attributes"
+# There is a fix in 0.171 version (commit b10d7eb74064c5906f031cd17c0f82041c6a4ca1)
+# but 0.171 has different license, so to be safe don't backport the fix, just ignore the issue
+CFLAGS += "-Wno-error=format-truncation="
+
+# There is a fix in 0.182 version (commit 5621fe5443da23112170235dd5cac161e5c75e65)
+# but 0.182 has different license, so to be safe don't backport the fix, just ignore the issue
+CFLAGS += "-Wno-error=stringop-overflow="
+
EXTRA_OECONF = "--program-prefix=eu- --without-lzma"
EXTRA_OECONF_append_class-native = " --without-bzlib"
EXTRA_OECONF_append_libc-uclibc = " --enable-uclibc"


[meta-gplv2][PATCH] elfutils: ignore format-truncation and stringop-overflow issues to fix build with gcc-11

Martin Jansa
 

* works around:
http://errors.yoctoproject.org/Errors/Details/580076/
elfutils-0.148/src/ar.c:1088:56: error: '%-*ld' directive output may be truncated writing between 6 and 10 bytes into a region of size 7 [-Werror=format-truncation=]
1088 | snprintf (tmpbuf, sizeof (tmpbuf), ofmt ? "%-*lo" : "%-*ld", bufsize, val);
| ^~~~~
elfutils-0.148/src/ar.c:1088:55: note: directive argument in the range [0, 4294967295]
1088 | snprintf (tmpbuf, sizeof (tmpbuf), ofmt ? "%-*lo" : "%-*ld", bufsize, val);
| ^~~~~~~

http://errors.yoctoproject.org/Errors/Details/580078/
elfutils-0.148/tests/addrcfi.c:90:16: error: 'dwarf_frame_register' accessing 96 bytes in a region of size 64 [-Werror=stringop-overflow=]
90 | int result = dwarf_frame_register (stuff->frame, regno, ops_mem, &ops, &nops);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Signed-off-by: Martin Jansa <Martin.Jansa@...>
---
recipes-devtools/elfutils/elfutils_0.148.bb | 8 ++++++++
1 file changed, 8 insertions(+)

diff --git a/recipes-devtools/elfutils/elfutils_0.148.bb b/recipes-devtools/elfutils/elfutils_0.148.bb
index 1f07a28..654a715 100644
--- a/recipes-devtools/elfutils/elfutils_0.148.bb
+++ b/recipes-devtools/elfutils/elfutils_0.148.bb
@@ -61,6 +61,14 @@ inherit autotools gettext
# but 0.175 has different license, so to be safe don't backport the fix, just ignore the issue
CFLAGS += "-Wno-error=missing-attributes"

+# There is a fix in 0.171 version (commit b10d7eb74064c5906f031cd17c0f82041c6a4ca1)
+# but 0.171 has different license, so to be safe don't backport the fix, just ignore the issue
+CFLAGS += "-Wno-error=format-truncation="
+
+# There is a fix in 0.182 version (commit 5621fe5443da23112170235dd5cac161e5c75e65)
+# but 0.182 has different license, so to be safe don't backport the fix, just ignore the issue
+CFLAGS += "-Wno-error=stringop-overflow="
+
EXTRA_OECONF = "--program-prefix=eu- --without-lzma"
EXTRA_OECONF_append_class-native = " --without-bzlib"
EXTRA_OECONF_append_libc-uclibc = " --enable-uclibc"
--
2.30.2


[meta-selinux] MAINTAINERS: Remove myself.

flihp@...
 

I have been inactive for an extended period.

Signed-off-by: Philip Tricca <flihp@...>
---
MAINTAINERS | 5 -----
1 file changed, 5 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 36c451f..3166b32 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -24,11 +24,6 @@ F: conf
F: classes
F: recipes-*
=20
-M: Philip Tricca <flihp@...>
-F: conf
-F: classes
-F: recipes-*
-
COMMON
M: Yi Zhao <yi.zhao@...>
F: conf
--=20
2.20.1


Observed issue regarding hostapd

rohit jadhav
 

Hi
can you please help out with following issue
ERROR: core-image-minimal-1.0-r0 do_rootfs: Postinstall scriptlets of ['hostapd'] have failed. If the intention is to defer them to first boot,
then please place them into pkg_postinst_ontarget_${PN} ().
Deferring to first boot via 'exit 1' is no longer supported.

Thanks and regards
rohit


#yocto cmake configurations #yocto

Monsees, Steven C (US)
 

 

I am using zeus, standard SDK, cmake…

 

Can I pre-configure the SDK to setup cmake package search paths ?, say for find_package, etc. (i.e. detecting external libraries/programs)…

 

The majority of my env is configuring properly, but I am finding cmake is setup for a standard linux env with regards to these types of searches, and

I wanted the cmake built in to look at my SDK paths (first by default) when doing such things as detecting python interpreter, libraries, etc.

 

I am working on third party package unaware of my SDK setup.

 

Thanks,

Steve


[meta-raspberrypi] Booting a Raspberry Pi 4 using PXE

Manuel Wagesreither
 

Hello all!

Since a certain eeprom version, the Raspberry Pi 4 can directly boot from network. Has anyone experience on this?

I already managed to to have the Raspi to load the kernel and all the device tree stuff over network. I then exported `build/tmp/work/raspberrypi4_64-poky-linux/bora-image/1.0-r0/rootfs/` as via nfs and changed the linux kernel commandline so it would use this share as nfsroot. At boot many failing services get reported and and the boot progress stops somewhere along the way. It tells me the system is in emergency mode and asks me for the root password for maintenance. I have an empty root password. When I press Control-D to continue, the same prompt reappears. Same when I simply press enter.

Has onyone any input for me? I guess I'll need to monitor what gets written to the serial port.

Regards,
Manuel


[meta-mingw] [PATCH 2/2] nativesdk-mingw-w64-winpthreads: Implement __udivmoddi4

Khem Raj
 

Fixes build with gcc 11+

Signed-off-by: Khem Raj <raj.khem@...>
---
.../0001-winpthreads-Add-__udivmoddi4.patch | 52 +++++++++++++++++++
.../nativesdk-mingw-w64-winpthreads_8.0.0.bb | 2 +
2 files changed, 54 insertions(+)
create mode 100644 recipes-devtools/mingw-w64/files/0001-winpthreads-Add-__udivmoddi4.patch

diff --git a/recipes-devtools/mingw-w64/files/0001-winpthreads-Add-__udivmoddi4.patch b/recipes-devtools/mingw-w64/files/0001-winpthreads-Add-__udivmoddi4.patch
new file mode 100644
index 0000000..3eb298e
--- /dev/null
+++ b/recipes-devtools/mingw-w64/files/0001-winpthreads-Add-__udivmoddi4.patch
@@ -0,0 +1,52 @@
+From 3b0af7327446ae179dc93b6a6ab1074251d348d0 Mon Sep 17 00:00:00 2001
+From: Khem Raj <raj.khem@...>
+Date: Fri, 30 Apr 2021 16:50:36 -0700
+Subject: [PATCH] winpthreads: Add __udivmoddi4
+
+Newer GCC ( 11.1.0+ ) is generating calls to __udivmoddi4 on i686
+architecture, therefore provide an implementation to avoid undefined
+references
+
+Upstream-Status: Pending
+Signed-off-by: Khem Raj <raj.khem@...>
+---
+ .../winpthreads/src/libgcc/dll_math.c | 16 +++++++++++++++-
+ 1 file changed, 15 insertions(+), 1 deletion(-)
+
+diff --git a/mingw-w64-libraries/winpthreads/src/libgcc/dll_math.c b/mingw-w64-libraries/winpthreads/src/libgcc/dll_math.c
+index aeec068..d170967 100644
+--- a/mingw-w64-libraries/winpthreads/src/libgcc/dll_math.c
++++ b/mingw-w64-libraries/winpthreads/src/libgcc/dll_math.c
+@@ -121,6 +121,7 @@ u_quad_t __udivdi3(u_quad_t a, u_quad_t b);
+ u_quad_t __umoddi3(u_quad_t a, u_quad_t b);
+ int __ucmpdi2(u_quad_t a, u_quad_t b);
+ quad_t __divmoddi4(quad_t a, quad_t b, quad_t *rem);
++u_quad_t __udivmoddi4(u_quad_t a, u_quad_t b, u_quad_t *rem);
+
+ #endif /* !_LIBKERN_QUAD_H_ */
+
+@@ -573,7 +574,20 @@ __divmoddi4(a, b, rem)
+ return (negq ? -uq : uq);
+ }
+
++/*
++ * Divide two unsigned quads.
++ * This function is new in GCC 7.
++ */
++u_quad_t
++__udivmoddi4(a, b, rem)
++ u_quad_t a, b, *rem;
++{
++ u_quad_t q = __udivdi3(a, b);
++ if (rem)
++ *rem = a - b * q;
++ return q;
++}
++
+ #else
+ static int __attribute__((unused)) dummy;
+ #endif /*deined (_X86_) && !defined (__x86_64__)*/
+-
+--
+2.31.1
+
diff --git a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_8.0.0.bb b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_8.0.0.bb
index e694e5b..814268d 100644
--- a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_8.0.0.bb
+++ b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_8.0.0.bb
@@ -2,6 +2,8 @@ DESCRIPTION = "Winpthreads runtime libraries from MinGW-w64 project"

require mingw-w64.inc

+SRC_URI += "file://0001-winpthreads-Add-__udivmoddi4.patch;striplevel=3"
+
S = "${WORKDIR}/mingw-w64-v${PV}/mingw-w64-libraries/winpthreads"
B = "${WORKDIR}/build-${TARGET_SYS}"

--
2.31.1


[meta-mingw] [PATCH 1/2] mingw-w64-runtime,mingw-w64-winpthreads: Upgrade to 8.0.0

Khem Raj
 

Signed-off-by: Khem Raj <raj.khem@...>
---
recipes-devtools/mingw-w64/mingw-w64.inc | 2 +-
...64-headers_7.0.0.bb => nativesdk-mingw-w64-headers_8.0.0.bb} | 0
...64-runtime_7.0.0.bb => nativesdk-mingw-w64-runtime_8.0.0.bb} | 0
...hreads_7.0.0.bb => nativesdk-mingw-w64-winpthreads_8.0.0.bb} | 0
4 files changed, 1 insertion(+), 1 deletion(-)
rename recipes-devtools/mingw-w64/{nativesdk-mingw-w64-headers_7.0.0.bb => nativesdk-mingw-w64-headers_8.0.0.bb} (100%)
rename recipes-devtools/mingw-w64/{nativesdk-mingw-w64-runtime_7.0.0.bb => nativesdk-mingw-w64-runtime_8.0.0.bb} (100%)
rename recipes-devtools/mingw-w64/{nativesdk-mingw-w64-winpthreads_7.0.0.bb => nativesdk-mingw-w64-winpthreads_8.0.0.bb} (100%)

diff --git a/recipes-devtools/mingw-w64/mingw-w64.inc b/recipes-devtools/mingw-w64/mingw-w64.inc
index a435dea..d40d4a5 100644
--- a/recipes-devtools/mingw-w64/mingw-w64.inc
+++ b/recipes-devtools/mingw-w64/mingw-w64.inc
@@ -5,7 +5,7 @@ COMPATIBLE_HOST = ".*-mingw.*"

SRC_URI = "${SOURCEFORGE_MIRROR}/project/mingw-w64/mingw-w64/mingw-w64-release/mingw-w64-v${PV}.tar.bz2"

-SRC_URI[sha256sum] = "aa20dfff3596f08a7f427aab74315a6cb80c2b086b4a107ed35af02f9496b628"
+SRC_URI[sha256sum] = "44c740ea6ab3924bc3aa169bad11ad3c5766c5c8459e3126d44eabb8735a5762"

UPSTREAM_CHECK_URI = "http://sourceforge.net/projects/mingw-w64/files/mingw-w64/mingw-w64-release/"
UPSTREAM_CHECK_REGEX = "mingw-w64-v(?P<pver>(\d+[\.\-_]*)+)\.tar"
diff --git a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-headers_7.0.0.bb b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-headers_8.0.0.bb
similarity index 100%
rename from recipes-devtools/mingw-w64/nativesdk-mingw-w64-headers_7.0.0.bb
rename to recipes-devtools/mingw-w64/nativesdk-mingw-w64-headers_8.0.0.bb
diff --git a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_8.0.0.bb
similarity index 100%
rename from recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb
rename to recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_8.0.0.bb
diff --git a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_7.0.0.bb b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_8.0.0.bb
similarity index 100%
rename from recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_7.0.0.bb
rename to recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_8.0.0.bb
--
2.31.1


devtool modify fails

Kent Dorfman <kent.dorfman766@...>
 

To my way of thinking, a

$ devtool modify linux

should NEVER fail if it is preceded by

$ bitbake -c do_cleanall linux

The intended staging of the kernel into the workspace fails, saying
that it cannot find miscellaneous and adhoc .scc files that no longer
exist after several variants of kernel config modifications.

fails on do_kernel_metadata...

| ERROR. input file "cfg/xilinx_intc.scc" does not exist

How to fix???


Re: any compelling reason to use SDK rather than eSDK?

Quentin Schulz
 

Hi,

On Fri, Apr 30, 2021 at 05:49:29AM -0400, Robert P. J. Day wrote:

colleague wants to get into working with SDKs, and as i'm just
diving into the intricacies of that myself, i'm not sure how to
answser the question: "is there any reason to use the regular SDK as
opposed to the extensible SDK?"

superficially, it would seem that the eSDK has nothing but benefits,
It's very big and probably include your proprietary SW header and
libraries at the very least... or third party prebuilt
binaries/libraries you're not supposed to share outside of your product.

This is useful if you're doing active development internally and you
don't upgrade your Yocto layers too often. This means non-Yocto verse
people could work on the main SW stack without caring about Yocto at
all.

so other than perhaps needing more resources, is there any reason to
use the regular SDK and forego the benefits of eSDK?
Normal SDK is just a toolchain, very practical if a third party vendor
requires you to send them something so they can build a blob that works
on your machine. And usually, you don't want to send anything that is
remotely critical to your business, IP wise.

I have barely used SDK, so to be taken with a grain of salt as usual.

Cheers,
Quentin


[meta-gplv2][PATCH] gnutls: add possibility to build with cryptodev support

Federico Pellegrin
 

Add possibility, via PACKAGECONFIG variable, to enable cryptodev
(hardware crypto acceleration) for gnutls in a very similar way
as it is already present for openssl.

Signed-off-by: Federico Pellegrin <fede@...>
---
meta/recipes-support/gnutls/gnutls_3.7.1.bb | 1 +
1 file changed, 1 insertion(+)

diff --git a/meta/recipes-support/gnutls/gnutls_3.7.1.bb b/meta/recipes-support/gnutls/gnutls_3.7.1.bb
index 350d0a018bd..6674542a77d 100644
--- a/meta/recipes-support/gnutls/gnutls_3.7.1.bb
+++ b/meta/recipes-support/gnutls/gnutls_3.7.1.bb
@@ -36,6 +36,7 @@ PACKAGECONFIG[libidn] = "--with-idn,--without-idn,libidn2"
PACKAGECONFIG[libtasn1] = "--with-included-libtasn1=no,--with-included-libtasn1,libtasn1"
PACKAGECONFIG[p11-kit] = "--with-p11-kit,--without-p11-kit,p11-kit"
PACKAGECONFIG[tpm] = "--with-tpm,--without-tpm,trousers"
+PACKAGECONFIG[cryptodev-linux] = "--enable-cryptodev,,cryptodev-linux,cryptodev-module"

EXTRA_OECONF = " \
--enable-doc \
--
2.26.3


Re: [PATCH yocto-autobuilder2 1/2] meta-arm has a hardknott branch now

Ross Burton <ross@...>
 

On Thu, 29 Apr 2021 at 22:40, akuster808 <akuster808@...> wrote:
When we actually release, yes.
So do you plan on doing the dot releases too?
The plan is that today-ish we roll the 3.3 release for hardknott and
also tag point releases on the stable branches too.

Ross


any compelling reason to use SDK rather than eSDK?

Robert P. J. Day
 

colleague wants to get into working with SDKs, and as i'm just
diving into the intricacies of that myself, i'm not sure how to
answser the question: "is there any reason to use the regular SDK as
opposed to the extensible SDK?"

superficially, it would seem that the eSDK has nothing but benefits,
so other than perhaps needing more resources, is there any reason to
use the regular SDK and forego the benefits of eSDK?

rday


Re: Can layer maintainers add yocto-X.Y tags for yocto-3.3 and later?

Khem Raj
 

On Thu, Apr 29, 2021 at 3:32 PM Martin Jansa <martin.jansa@...> wrote:

On Thu, Apr 29, 2021 at 06:05:30PM -0400, Randy MacLeod wrote:
Most yocto layers have not adopted the tagging perhaps because they
weren't aware of it so that's why I'm writing this email. Tagging
will make it easy to find the first commit for a specific release
independent of what the branching policy of a layer is. Layer
maintainers sometimes create the release branch in advance of
when oe-core is released and by adding the tag, it would make it
clear when the layer considers content to be officially released.
Of course it's up to users to decide if they are going to follow
the HEAD of a branch or, for some reason, stick with a tagged commit
or private branch off that commit.
I think this could be a good thing, although it does put the burden on
release maintainers. mostly they
test against the tip of the release branch, So if yocto project
testing is including these layers for wider
testing and can then recommend a validated commit then perhaps this
could be made viable.
That could open up a can of worms as who will fix the QA test failures?
Hi Armin,

The community will fix bugs on HEAD just like before.
It's a tag indicating where the branch was at GA time.
There's no obligation for he maintainer do do anything in addition
to what they were doing if we didn't have a tag.

I guess that could be made clear in the README if needed.
To be honest I don't see much value of these tags for layers not
included in the QA testing with oe-core release.

I believe we agreed on promoting latest revisions in the branches for
selected release.

And I think the process for stable branches works reasonably well in the
layers I usually use and only very rarely new regression is introduced
in stable branch so from my experience the latest revision is always better
than GA tag (or any tag for various point releases).

Why should anyone use yocto-3.3 tag of meta-oe if the harknott branch
has few more fixes and tip of hardknott branch was tested exactly the
same as the yocto-3.3 tag?

TLDR: Why should some low traffic layer have these tags which might point to
exactly the same commit for multiple release (when all of them
still parse, build and work correctly). Many layers don't feel the need
to create a separate branch for each release when the same master works
fine for last 3 Yocto releases. And I feel the pain when e.g. with
meta-ros the last 4 branches (dunfell, gatesgarth, hardknott, master)
are 99% identical, so whatever ROS update I merge to one of them gets
distributed across all of them and only rarely with some small
modification added only in some of them. Adding a yocto-3.3 tag there
won't make that commit any better than a tip of hardknott and it might
be actually a lot worse than tip of hardknott.
I think its perhaps also that distros have mechanisms to lock layers at a given
revision whatever tooling they use ( git submod, android repo,
combotools something else)
so distro manifest at that point acts as pseudo tag and seems better
downstream way
to create a uniform tested view of that distro. Something similar is
needed for poky distro perhaps a layer manifest
which tells about revisions of tested layers with poky version X if we
desire to have more layers tested along with what it supports as of
now.
oe-core supports nodistro and its self-sufficient.


Regards,


Re: Can layer maintainers add yocto-X.Y tags for yocto-3.3 and later?

Martin Jansa
 

On Thu, Apr 29, 2021 at 06:05:30PM -0400, Randy MacLeod wrote:
Most yocto layers have not adopted the tagging perhaps because they
weren't aware of it so that's why I'm writing this email. Tagging
will make it easy to find the first commit for a specific release
independent of what the branching policy of a layer is. Layer
maintainers sometimes create the release branch in advance of
when oe-core is released and by adding the tag, it would make it
clear when the layer considers content to be officially released.
Of course it's up to users to decide if they are going to follow
the HEAD of a branch or, for some reason, stick with a tagged commit
or private branch off that commit.
I think this could be a good thing, although it does put the burden on
release maintainers. mostly they
test against the tip of the release branch, So if yocto project
testing is including these layers for wider
testing and can then recommend a validated commit then perhaps this
could be made viable.
That could open up a can of worms as who will fix the QA test failures?
Hi Armin,

The community will fix bugs on HEAD just like before.
It's a tag indicating where the branch was at GA time.
There's no obligation for he maintainer do do anything in addition
to what they were doing if we didn't have a tag.

I guess that could be made clear in the README if needed.
To be honest I don't see much value of these tags for layers not
included in the QA testing with oe-core release.

I believe we agreed on promoting latest revisions in the branches for
selected release.

And I think the process for stable branches works reasonably well in the
layers I usually use and only very rarely new regression is introduced
in stable branch so from my experience the latest revision is always better
than GA tag (or any tag for various point releases).

Why should anyone use yocto-3.3 tag of meta-oe if the harknott branch
has few more fixes and tip of hardknott branch was tested exactly the
same as the yocto-3.3 tag?

TLDR: Why should some low traffic layer have these tags which might point to
exactly the same commit for multiple release (when all of them
still parse, build and work correctly). Many layers don't feel the need
to create a separate branch for each release when the same master works
fine for last 3 Yocto releases. And I feel the pain when e.g. with
meta-ros the last 4 branches (dunfell, gatesgarth, hardknott, master)
are 99% identical, so whatever ROS update I merge to one of them gets
distributed across all of them and only rarely with some small
modification added only in some of them. Adding a yocto-3.3 tag there
won't make that commit any better than a tip of hardknott and it might
be actually a lot worse than tip of hardknott.

Regards,

4061 - 4080 of 57376