[OE-core] [PATCH] nativesdk-pseudo: Fix to work with glibc 2.34 systems
Since commit [df313aa810 pseudo: Fix to work with glibc 2.34 systems] applied, it fixed native only. And nativesdk has the similar issue Tweak library search order, make prebuilt lib ahead of recipe lib, after apply the fix: ... $ readelf -a lib/pseudo/lib64/libpseudo.so | grep 'Shared library' 0x0001 (NEEDED) Shared library: [libdl.so.2] 0x0001 (NEEDED) Shared library:[libpthread.so.0] 0x0001 (NEEDED) Shared library: [libc.so.6] ... Signed-off-by: Hongxu Jia --- .../pseudo/files/older-glibc-symbols.patch| 38 +++ meta/recipes-devtools/pseudo/pseudo_git.bb| 3 ++ 2 files changed, 26 insertions(+), 15 deletions(-) diff --git a/meta/recipes-devtools/pseudo/files/older-glibc-symbols.patch b/meta/recipes-devtools/pseudo/files/older-glibc-symbols.patch index 1552c69b52..c453b5f735 100644 --- a/meta/recipes-devtools/pseudo/files/older-glibc-symbols.patch +++ b/meta/recipes-devtools/pseudo/files/older-glibc-symbols.patch @@ -12,26 +12,31 @@ Yes this is horrible. Better solutions welcome. There is more info in the bug: [YOCTO #14521] -Upstream-Status: Inappropriate [this patch is native only] +Upstream-Status: Inappropriate [this patch is native and nativesdk] Signed-off-by: Richard Purdie -Index: git/Makefile.in -=== git.orig/Makefile.in -+++ git/Makefile.in -@@ -122,7 +122,7 @@ libpseudo: $(LIBPSEUDO) +Tweak library search order, make prebuilt lib ahead of recipe lib +Signed-off-by: Hongxu Jia +--- + Makefile.in | 2 +- + pseudo_wrappers.c | 5 - + 2 files changed, 5 insertions(+), 2 deletions(-) + +diff --git a/Makefile.in b/Makefile.in +--- a/Makefile.in b/Makefile.in +@@ -120,7 +120,7 @@ $(PSEUDODB): pseudodb.o $(SHOBJS) $(DBOBJS) pseudo_ipc.o | $(BIN) + libpseudo: $(LIBPSEUDO) + $(LIBPSEUDO): $(WRAPOBJS) pseudo_client.o pseudo_ipc.o $(SHOBJS) | $(LIB) - $(CC) $(CFLAGS) $(CFLAGS_PSEUDO) -shared -o $(LIBPSEUDO) \ +- $(CC) $(CFLAGS) $(CFLAGS_PSEUDO) -shared -o $(LIBPSEUDO) \ ++ $(CC) $(CFLAGS) -Lprebuilt/$(shell uname -m)-linux/lib/ $(CFLAGS_PSEUDO) -shared -o $(LIBPSEUDO) \ pseudo_client.o pseudo_ipc.o \ -- $(WRAPOBJS) $(SHOBJS) $(LDFLAGS) $(CLIENT_LDFLAGS) -+ $(WRAPOBJS) $(SHOBJS) $(LDFLAGS) -Lprebuilt/$(shell uname -m)-linux/lib/ $(CLIENT_LDFLAGS) + $(WRAPOBJS) $(SHOBJS) $(LDFLAGS) $(CLIENT_LDFLAGS) - # *everything* now relies on stuff that's generated in the - # wrapper process. -Index: git/pseudo_wrappers.c -=== git.orig/pseudo_wrappers.c -+++ git/pseudo_wrappers.c +diff --git a/pseudo_wrappers.c b/pseudo_wrappers.c +--- a/pseudo_wrappers.c b/pseudo_wrappers.c @@ -100,10 +100,13 @@ static void libpseudo_atfork_child(void) pseudo_mutex_holder = 0; } @@ -47,3 +52,6 @@ Index: git/pseudo_wrappers.c pseudo_getlock(); pseudo_antimagic(); +-- +2.27.0 + diff --git a/meta/recipes-devtools/pseudo/pseudo_git.bb b/meta/recipes-devtools/pseudo/pseudo_git.bb index 79b7123e38..328177c9bf 100644 --- a/meta/recipes-devtools/pseudo/pseudo_git.bb +++ b/meta/recipes-devtools/pseudo/pseudo_git.bb @@ -8,6 +8,9 @@ SRC_URI = "git://git.yoctoproject.org/pseudo;branch=oe-core \ SRC_URI:append:class-native = " \ http://downloads.yoctoproject.org/mirror/sources/pseudo-prebuilt-2.33.tar.xz;subdir=git/prebuilt;name=prebuilt \ file://older-glibc-symbols.patch" +SRC_URI:append:class-nativesdk = " \ + http://downloads.yoctoproject.org/mirror/sources/pseudo-prebuilt-2.33.tar.xz;subdir=git/prebuilt;name=prebuilt \ +file://older-glibc-symbols.patch" SRC_URI[prebuilt.sha256sum] = "ed9f456856e9d86359f169f46a70ad7be4190d6040282b84c8d97b99072485aa" SRCREV = "b988b0a6b8afd8d459bc9a2528e834f63a3d59b2" -- 2.30.2 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#155336): https://lists.openembedded.org/g/openembedded-core/message/155336 Mute This Topic: https://lists.openembedded.org/mt/85154607/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH v2] libcgroup: fix installed-vs-shipped qa issue
From: Kai Kang
When pam is enabled, it complains installed-vs-shipped QA issue:
| ERROR: libcgroup-2.0-r0 do_package: QA Issue: libcgroup:
Files/directories were installed but not shipped in any package:
| /lib/security/pam_cgroup.a
Signed-off-by: Kai Kang
---
meta/recipes-core/libcgroup/libcgroup_2.0.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/libcgroup/libcgroup_2.0.bb
b/meta/recipes-core/libcgroup/libcgroup_2.0.bb
index bc0a75d46c..a58dd88ea5 100644
--- a/meta/recipes-core/libcgroup/libcgroup_2.0.bb
+++ b/meta/recipes-core/libcgroup/libcgroup_2.0.bb
@@ -27,6 +27,7 @@ PACKAGECONFIG[pam] =
"--enable-pam-module-dir=${base_libdir}/security --enable-p
PACKAGES =+ "cgroups-pam-plugin"
FILES:cgroups-pam-plugin = "${base_libdir}/security/pam_cgroup.so*"
FILES:${PN}-dev += "${base_libdir}/security/*.la"
+FILES:${PN}-staticdev += "${base_libdir}/security/pam_cgroup.a"
do_install:append() {
# Until we ship the test suite, this library isn't useful
--
2.17.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155335):
https://lists.openembedded.org/g/openembedded-core/message/155335
Mute This Topic: https://lists.openembedded.org/mt/85152139/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH] libcgroup: remove static pam library
On 8/25/21 11:35 PM, Khem Raj wrote:
On 8/25/21 1:10 AM, kai wrote:
From: Kai Kang
libpam disables static build by default, so remove static pam library of
libcgroup. Otherwise it complains QA issue:
| ERROR: libcgroup-2.0-r0 do_package: QA Issue: libcgroup:
Files/directories were installed but not shipped in any
package:
| /lib/security/pam_cgroup.a
Signed-off-by: Kai Kang
---
meta/recipes-core/libcgroup/libcgroup_2.0.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/libcgroup/libcgroup_2.0.bb
b/meta/recipes-core/libcgroup/libcgroup_2.0.bb
index bc0a75d46c..f48b8ece9b 100644
--- a/meta/recipes-core/libcgroup/libcgroup_2.0.bb
+++ b/meta/recipes-core/libcgroup/libcgroup_2.0.bb
@@ -31,4 +31,5 @@ FILES:${PN}-dev += "${base_libdir}/security/*.la"
do_install:append() {
# Until we ship the test suite, this library isn't useful
rm -f ${D}${libdir}/libcgroupfortesting.*
+ rm -f ${D}${base_libdir}/security/pam_cgroup.a
}
should this be simply packaged into FILES_${PN}-staticdev instead ?
OK. v2 will send.
Regards,
Kai
--
Kai Kang
Wind River Linux
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155334):
https://lists.openembedded.org/g/openembedded-core/message/155334
Mute This Topic: https://lists.openembedded.org/mt/85130950/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH] qemurunner.py: print output from runqemu/qemu-system in stop()
This is done when starting up qemu has failed, but is not done
when qemu started ok, but fails later in QMP communication.
Output from runqemu does contain valuable information to find out
why, so rather than fix all the QMP fails to include it, let's just
print it in stop().
Signed-off-by: Alexander Kanavin
---
meta/lib/oeqa/utils/qemurunner.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/lib/oeqa/utils/qemurunner.py
b/meta/lib/oeqa/utils/qemurunner.py
index 5c9d2b24a3..e099c6e2a7 100644
--- a/meta/lib/oeqa/utils/qemurunner.py
+++ b/meta/lib/oeqa/utils/qemurunner.py
@@ -535,6 +535,8 @@ class QemuRunner:
if self.runqemu.poll() is None:
self.logger.debug("Sending SIGKILL to runqemu")
os.killpg(os.getpgid(self.runqemu.pid), signal.SIGKILL)
+if not self.runqemu.stdout.closed:
+self.logger.warning("Output from runqemu:\n%s" %
self.getOutput(self.runqemu.stdout))
self.runqemu.stdin.close()
self.runqemu.stdout.close()
self.runqemu_exited = True
--
2.31.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155333):
https://lists.openembedded.org/g/openembedded-core/message/155333
Mute This Topic: https://lists.openembedded.org/mt/85148684/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[v2][oe-core][hardknott][PATCH 1/1] icu: increase pkgdata command buffer size
Mitigate pathname truncation when installing in a project
with a very long pathname.
Signed-off-by: Joe Slater
---
...pkgdata-increase-command-buffer-size.patch | 46 +++
meta/recipes-support/icu/icu_68.2.bb | 1 +
2 files changed, 47 insertions(+)
create mode 100644
meta/recipes-support/icu/icu/0001-pkgdata-increase-command-buffer-size.patch
diff --git
a/meta/recipes-support/icu/icu/0001-pkgdata-increase-command-buffer-size.patch
b/meta/recipes-support/icu/icu/0001-pkgdata-increase-command-buffer-size.patch
new file mode 100644
index 00..a5483568bb
--- /dev/null
+++
b/meta/recipes-support/icu/icu/0001-pkgdata-increase-command-buffer-size.patch
@@ -0,0 +1,46 @@
+From ab6b1acdeed76899f8227c38ab7e7675c7673ff1 Mon Sep 17 00:00:00 2001
+From: Joe Slater
+Date: Thu, 5 Aug 2021 09:23:48 -0700
+Subject: [PATCH 1/1] pkgdata: increase command buffer size
+
+Make cmd LARGE_BUFFER_SIZE to avoid pathname truncation
+when install paths are longer than about 150 characters.
+
+https://unicode-org.atlassian.net/browse/ICU-21702 has been
+created to address this issue and error reporting.
+
+Upstream-Status: Submitted [ICU-21702 opened]
+
+Signed-off-by: Joe Slater
+---
+ source/tools/pkgdata/pkgdata.cpp | 6 +++---
+ 1 file changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/source/tools/pkgdata/pkgdata.cpp
b/source/tools/pkgdata/pkgdata.cpp
+index 5ab682e..d4b70ef 100644
+--- a/tools/pkgdata/pkgdata.cpp
b/tools/pkgdata/pkgdata.cpp
+@@ -1131,17 +1131,17 @@ normal_symlink_mode:
+
+ static int32_t pkg_installLibrary(const char *installDir, const char
*targetDir, UBool noVersion) {
+ int32_t result = 0;
+-char cmd[SMALL_BUFFER_MAX_SIZE];
++char cmd[LARGE_BUFFER_MAX_SIZE];
+
+ auto ret = snprintf(cmd,
+-SMALL_BUFFER_MAX_SIZE,
++LARGE_BUFFER_MAX_SIZE,
+ "cd %s && %s %s %s%s%s",
+ targetDir,
+ pkgDataFlags[INSTALL_CMD],
+ libFileNames[LIB_FILE_VERSION],
+ installDir, PKGDATA_FILE_SEP_STRING,
libFileNames[LIB_FILE_VERSION]);
+ (void)ret;
+-U_ASSERT(0 <= ret && ret < SMALL_BUFFER_MAX_SIZE);
++U_ASSERT(0 <= ret && ret < LARGE_BUFFER_MAX_SIZE);
+
+ result = runCommand(cmd);
+
+--
+2.29.2
+
diff --git a/meta/recipes-support/icu/icu_68.2.bb
b/meta/recipes-support/icu/icu_68.2.bb
index 1ca87feee4..130212d245 100644
--- a/meta/recipes-support/icu/icu_68.2.bb
+++ b/meta/recipes-support/icu/icu_68.2.bb
@@ -107,6 +107,7 @@ SRC_URI = "${BASE_SRC_URI};name=code \
file://filter.json \
file://fix-install-manx.patch \
file://0001-icu-Added-armeb-support.patch \
+ file://0001-pkgdata-increase-command-buffer-size.patch \
"
SRC_URI_append_class-target = "\
--
2.31.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155332):
https://lists.openembedded.org/g/openembedded-core/message/155332
Mute This Topic: https://lists.openembedded.org/mt/85148189/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] what means the test 'if [ -z "$D" ]' in a pkg_postinst routine?
It used to be that 'exit 1' was the way to defer to boot time, but that was
changed long time ago to not be ambiguous like that and cause a real
failure at build time. Deferring to first boot needs to be explicitly
requested with _ontarget() (you can read the definition for it to see what
really happens, how $D is used and how request to defer is made).
Alex
On Wed, 25 Aug 2021 at 23:51, Robert P. J. Day
wrote:
>
> Quoting Phil Blundell :
>
> > That's testing for offline installation. If $D is not set, it's
> > running on the target.
> >
> > p.
>
>one last query before i head off for dinner ... so what about
> pkg_postinst() routines that do double duty, like this one from
> dbus_1.12.20.bb:
>
>
> PACKAGE_WRITE_DEPS += "${@bb.utils.contains('DISTRO_FEATURES','systemd
> sysvinit','systemd-systemctl-native','',d)}"
> pkg_postinst:dbus() {
> # If both systemd and sysvinit are enabled, mask the dbus-1
> init script
> if ${@bb.utils.contains('DISTRO_FEATURES','systemd
> sysvinit','true','false',d)}; then
> if [ -n "$D" ]; then
> OPTS="--root=$D"
> fi
> systemctl $OPTS mask dbus-1.service
> fi
>
> if [ -z "$D" ] && [ -e /etc/init.d/populate-volatile.sh ] ; then
> /etc/init.d/populate-volatile.sh update
> fi
> }
>
>
> note how that routine checks its context and, as i recall (but
> it's not documented in the docs i'm looking at), i'd swear that
> i read somewhere that if a pkg_postinst() routine fails at image
> creation time, it was deferred until boot time, which would
> explain the above routine checking its runtime context.
>
>anyway, off for food.
>
> rday
>
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155331):
https://lists.openembedded.org/g/openembedded-core/message/155331
Mute This Topic: https://lists.openembedded.org/mt/85146007/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [meta-oe][PATCH] hidapi: add rdep on glibc-gconv-utf-16
libhidapi-libusb needs to convert from UTF-16LE to WCHAR_T in order to
read various libusb string descriptors.
Signed-off-by: Justin Bronder
---
meta-oe/recipes-support/hidapi/hidapi_git.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta-oe/recipes-support/hidapi/hidapi_git.bb
b/meta-oe/recipes-support/hidapi/hidapi_git.bb
index 76f5dc762..54b794774 100644
--- a/meta-oe/recipes-support/hidapi/hidapi_git.bb
+++ b/meta-oe/recipes-support/hidapi/hidapi_git.bb
@@ -7,6 +7,7 @@ LICENSE = "BSD-3-Clause | GPLv3"
LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=7c3949a631240cb6c31c50f3eb696077"
DEPENDS = "libusb udev"
+RDEPENDS_${PN} += "glibc-gconv-utf-16"
inherit autotools pkgconfig
--
2.33.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155330):
https://lists.openembedded.org/g/openembedded-core/message/155330
Mute This Topic: https://lists.openembedded.org/mt/85147825/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] what means the test 'if [ -z "$D" ]' in a pkg_postinst routine?
Quoting Phil Blundell :
That's testing for offline installation. If $D is not set, it's
running on the target.
p.
one last query before i head off for dinner ... so what about
pkg_postinst() routines that do double duty, like this one from
dbus_1.12.20.bb:
PACKAGE_WRITE_DEPS += "${@bb.utils.contains('DISTRO_FEATURES','systemd
sysvinit','systemd-systemctl-native','',d)}"
pkg_postinst:dbus() {
# If both systemd and sysvinit are enabled, mask the dbus-1
init script
if ${@bb.utils.contains('DISTRO_FEATURES','systemd
sysvinit','true','false',d)}; then
if [ -n "$D" ]; then
OPTS="--root=$D"
fi
systemctl $OPTS mask dbus-1.service
fi
if [ -z "$D" ] && [ -e /etc/init.d/populate-volatile.sh ] ; then
/etc/init.d/populate-volatile.sh update
fi
}
note how that routine checks its context and, as i recall (but
it's not documented in the docs i'm looking at), i'd swear that
i read somewhere that if a pkg_postinst() routine fails at image
creation time, it was deferred until boot time, which would
explain the above routine checking its runtime context.
anyway, off for food.
rday
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155329):
https://lists.openembedded.org/g/openembedded-core/message/155329
Mute This Topic: https://lists.openembedded.org/mt/85146007/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] what means the test 'if [ -z "$D" ]' in a pkg_postinst routine?
_ontarget() is basically syntactic sugar for $D test, but yes it's the new preferred form. If you see $D, that means the recipe hasn't been converted. Alex On Wed, 25 Aug 2021 at 23:27, Robert P. J. Day wrote: > > Quoting Phil Blundell : > > > That's testing for offline installation. If $D is not set, it's > > running on the target. > > > > p. > >right, that's exactly what i suspected in my original posting, > i just wanted to make sure, which raises a couple issues. > >first, that distinction doesn't seem to be mentioned in the > docs, so i'll ponder writing something. > >second, is that simply an old form that would be superseded > by using "pkg_postinst_ontarget()" instead? > >anyway, more questions later as i work on some lengthier docs > on this. > > rday > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#155328): https://lists.openembedded.org/g/openembedded-core/message/155328 Mute This Topic: https://lists.openembedded.org/mt/85146007/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] what means the test 'if [ -z "$D" ]' in a pkg_postinst routine?
Quoting Phil Blundell : That's testing for offline installation. If $D is not set, it's running on the target. p. right, that's exactly what i suspected in my original posting, i just wanted to make sure, which raises a couple issues. first, that distinction doesn't seem to be mentioned in the docs, so i'll ponder writing something. second, is that simply an old form that would be superseded by using "pkg_postinst_ontarget()" instead? anyway, more questions later as i work on some lengthier docs on this. rday -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#155327): https://lists.openembedded.org/g/openembedded-core/message/155327 Mute This Topic: https://lists.openembedded.org/mt/85146007/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] what means the test 'if [ -z "$D" ]' in a pkg_postinst routine?
That's testing for offline installation. If $D is not set, it's running on the
target.
p.
On 25 August 2021 22:12:22 BST, "Robert P. J. Day"
wrote:
>
>Quoting Alexander Kanavin :
>
>> If you show the confusing examples, we could try to figure it out.
>>
>> Alex
>>
>> On Wed, 25 Aug 2021 at 22:35, Robert P. J. Day
>> wrote:
>>
>>>
>>> there will be many more questions about pkg_postinst (and related)
>>> routines shortly, but digging into these for the first time, i
>>> thought that that test checked whether the routine was being run
>>> at image creation time, or at first-time boot. now i'm not quite
>>> sure what to think after seeing several examples.
>>>
>>> what does the test for null or non-null variable "D" mean in
>>> a pkg_postinst routine? and once i figure all this out, i may
>>> very well contribute some enhanced docs for the next confused
>>> person.
>
> there's no shortage of examples ... here's just one from
>recipes-bsp/alsa-state/alsa-state.bb:
>
>
>pkg_postinst:${PN}() {
> if test -z "$D" <
> then
> if test -x ${sbindir}/alsactl
> then
> ${sbindir}/alsactl -g -f
>${localstatedir}/lib/alsa/asound.state restore
> fi
> fi
>}
>
>
>there's plenty more ... recipes-bsp/keymaps/keymaps_1.0.bb:
>
>
>pkg_postinst:${PN} () {
> if ${@bb.utils.contains('DISTRO_FEATURES','systemd
>sysvinit','true','false',d)}; then
> if [ -n "$D" ]; then<
> OPTS="--root=$D"
> fi
> systemctl $OPTS mask keymap.service
> fi
>}
>
>
>rday
>
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155326):
https://lists.openembedded.org/g/openembedded-core/message/155326
Mute This Topic: https://lists.openembedded.org/mt/85146007/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] what means the test 'if [ -z "$D" ]' in a pkg_postinst routine?
Quoting Alexander Kanavin :
If you show the confusing examples, we could try to figure it out.
Alex
On Wed, 25 Aug 2021 at 22:35, Robert P. J. Day
wrote:
there will be many more questions about pkg_postinst (and related)
routines shortly, but digging into these for the first time, i
thought that that test checked whether the routine was being run
at image creation time, or at first-time boot. now i'm not quite
sure what to think after seeing several examples.
what does the test for null or non-null variable "D" mean in
a pkg_postinst routine? and once i figure all this out, i may
very well contribute some enhanced docs for the next confused
person.
there's no shortage of examples ... here's just one from
recipes-bsp/alsa-state/alsa-state.bb:
pkg_postinst:${PN}() {
if test -z "$D" <
then
if test -x ${sbindir}/alsactl
then
${sbindir}/alsactl -g -f
${localstatedir}/lib/alsa/asound.state restore
fi
fi
}
there's plenty more ... recipes-bsp/keymaps/keymaps_1.0.bb:
pkg_postinst:${PN} () {
if ${@bb.utils.contains('DISTRO_FEATURES','systemd
sysvinit','true','false',d)}; then
if [ -n "$D" ]; then<
OPTS="--root=$D"
fi
systemctl $OPTS mask keymap.service
fi
}
rday
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155325):
https://lists.openembedded.org/g/openembedded-core/message/155325
Mute This Topic: https://lists.openembedded.org/mt/85146007/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] what means the test 'if [ -z "$D" ]' in a pkg_postinst routine?
If you show the confusing examples, we could try to figure it out. Alex On Wed, 25 Aug 2021 at 22:35, Robert P. J. Day wrote: > > there will be many more questions about pkg_postinst (and related) > routines shortly, but digging into these for the first time, i > thought that that test checked whether the routine was being run > at image creation time, or at first-time boot. now i'm not quite > sure what to think after seeing several examples. > > what does the test for null or non-null variable "D" mean in > a pkg_postinst routine? and once i figure all this out, i may > very well contribute some enhanced docs for the next confused > person. > > rday > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#155324): https://lists.openembedded.org/g/openembedded-core/message/155324 Mute This Topic: https://lists.openembedded.org/mt/85146007/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] what means the test 'if [ -z "$D" ]' in a pkg_postinst routine?
there will be many more questions about pkg_postinst (and related) routines shortly, but digging into these for the first time, i thought that that test checked whether the routine was being run at image creation time, or at first-time boot. now i'm not quite sure what to think after seeing several examples. what does the test for null or non-null variable "D" mean in a pkg_postinst routine? and once i figure all this out, i may very well contribute some enhanced docs for the next confused person. rday -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#155323): https://lists.openembedded.org/g/openembedded-core/message/155323 Mute This Topic: https://lists.openembedded.org/mt/85146007/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH] python3-pluggy: upgrade 0.13.1 -> 1.0.0
* All ptests pass on qemux86-64
pluggy 1.0.0 (2021-08-25)
Deprecations and Removals
#116: Remove deprecated implprefix support. Decorate hook
implementations using an instance of HookimplMarker instead.
The deprecation was announced in release 0.7.0.
#120: Remove the deprecated proc argument to call_historic. Use
result_callback instead, which has the same behavior. The
deprecation was announced in release 0.7.0.
#265: Remove the _Result.result property. Use _Result.get_result()
instead. Note that unlike result, get_result() raises the
exception if the hook raised. The deprecation was announced in release
0.6.0.
#267: Remove official support for Python 3.4.
#272: Dropped support for Python 2. Continue to use pluggy 0.13.x
for Python 2 support.
#308: Remove official support for Python 3.5.
#313: The internal pluggy.callers, pluggy.manager and pluggy.hooks
are now explicitly marked private by a _ prefix (e.g.
pluggy._callers). Only API exported by the top-level pluggy module is
considered public.
#59: Remove legacy __multicall__ recursive hook calling system. The
deprecation was announced in release 0.5.0.
Features
#282: When registering a hookimpl which is declared as
hookwrapper=True but whose function is not a generator
function, a PluggyValidationError exception is now raised.
Previously this problem would cause an error only later, when
calling the hook.
In the unlikely case that you have a hookwrapper that returns a
generator instead of yielding directly, for example:
def my_hook_real_implementation(arg):
print("before")
yield
print("after")
@hookimpl(hookwrapper=True)
def my_hook(arg):
return my_hook_implementation(arg)
change it to use yield from instead:
@hookimpl(hookwrapper=True)
def my_hook(arg):
yield from my_hook_implementation(arg)
#309: Add official support for Python 3.9.
Signed-off-by: Tim Orling
---
.../{python3-pluggy_0.13.1.bb => python3-pluggy_1.0.0.bb} | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
rename meta/recipes-devtools/python/{python3-pluggy_0.13.1.bb =>
python3-pluggy_1.0.0.bb} (80%)
diff --git a/meta/recipes-devtools/python/python3-pluggy_0.13.1.bb
b/meta/recipes-devtools/python/python3-pluggy_1.0.0.bb
similarity index 80%
rename from meta/recipes-devtools/python/python3-pluggy_0.13.1.bb
rename to meta/recipes-devtools/python/python3-pluggy_1.0.0.bb
index 479c10fcdc..14a7ccb0b0 100644
--- a/meta/recipes-devtools/python/python3-pluggy_0.13.1.bb
+++ b/meta/recipes-devtools/python/python3-pluggy_1.0.0.bb
@@ -3,8 +3,7 @@ HOMEPAGE = "https://github.com/pytest-dev/pluggy;
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=1c8206d16fd5cc02fa9b0bb98955e5c2"
-SRC_URI[md5sum] = "7f610e28b8b34487336b585a3dfb803d"
-SRC_URI[sha256sum] =
"15b2acde666561e1298d71b523007ed7364de07029219b604cf808bfa1c765b0"
+SRC_URI[sha256sum] =
"4224373bacce55f955a878bf9cfa763c1e360858e330072059e10bad68531159"
DEPENDS += "${PYTHON_PN}-setuptools-scm-native"
RDEPENDS:${PN} += "${PYTHON_PN}-importlib-metadata \
--
2.30.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155322):
https://lists.openembedded.org/g/openembedded-core/message/155322
Mute This Topic: https://lists.openembedded.org/mt/85145840/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH] go: upgrade to 1.17 release
On Wed, 2021-08-25 at 21:31 +0200, Alexander Kanavin wrote: > On Wed, 25 Aug 2021 at 21:26, Bruce Ashfield wrote: > > I mentioned meta-virtualization in the non-threaded part of this > > discussion, so that specific information has been covered. Sakib is a > > contributor there (and isn't new to core), and knows what he's doing, > > hence why I have the luxury of being less detailed in the reponses. > > > > I've said my bit on this, I'll pick up the pieces if anything ends up > > breaking .. I'm just trying to be proactive since history shows that > > go always breaks something. > > > > > Please try to understand where I am coming from. Yours truly is doing the bulk > of version updates in oe-core, because no one else bothers to, not even listed > maintainers (and more and more recipes do not even have a listed maintainer > anyore). So when someone else is showing initiative in version updates - and > Sakib has not updated go before - I would much rather show appreciation for > the effort, rather than immediate (and vague!) criticism for not enough > testing. > Enough, please :) Alex does a lot of good work with version upgrades in OE-Core and it is much appreciated. Bruce does a lot of good work with the kernels, associated bits and other things, both in core and as maintainer of meta-virtualization and it is also much appreciated. Go is a bit of a problem at the moment as previous upgrades introduced bugs which the triage team has been unable to get resolved. We know the next version makes further related changes which *will* cause problems. As such we are worried about it. I'm close to reverting the last uprev over the lack of attention to bugs. OE-Core doesn't use go that much and our test coverage is known to be weak there. meta-virt does use it much more heavily so asking for that to be tested with go uprevs is a reasonable request IMO. We are increasing the test matrix the autobuilder covers and meta-virt is potentially part of that, as is meta-oe. We do already have some basic check- layer tests. I think we all agree that it is too late for 1.17 in this cycle, we have enough risky problems on the go without that one. Cheers, Richard > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#155321): https://lists.openembedded.org/g/openembedded-core/message/155321 Mute This Topic: https://lists.openembedded.org/mt/85141060/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH] go: upgrade to 1.17 release
On Wed, 25 Aug 2021 at 21:26, Bruce Ashfield
wrote:
> I mentioned meta-virtualization in the non-threaded part of this
> discussion, so that specific information has been covered. Sakib is a
> contributor there (and isn't new to core), and knows what he's doing,
> hence why I have the luxury of being less detailed in the reponses.
>
> I've said my bit on this, I'll pick up the pieces if anything ends up
> breaking .. I'm just trying to be proactive since history shows that
> go always breaks something.
>
Please try to understand where I am coming from. Yours truly is doing the
bulk of version updates in oe-core, because no one else bothers to, not
even listed maintainers (and more and more recipes do not even have a
listed maintainer anyore). So when someone else is showing initiative in
version updates - and Sakib has not updated go before - I would much rather
show appreciation for the effort, rather than immediate (and vague!)
criticism for not enough testing.
Alex
>
> Bruce
>
>
> Bruce
>
> >
> > Alex
> >
> >
> >>
> >>
> >> Cheers,
> >>
> >> Bruce
> >>
> >> > That said, I agree that it's a bit late to place this into oe-core
> now, and it's best to stash this until the start of the next cycle.
> >> >
> >> > Alex
> >> >
> >> >>
> >> >>
> >> >> Bruce
> >> >>
> >> >> >
> >> >> > Sakib
> >> >> >
> >> >> > On 2021-08-25 1:20 p.m., Sakib Sajal wrote:
> >> >> >
> >> >> > go 1.17 includes small enhancements to the language.
> >> >> > Release notes: https://golang.org/doc/go1.17
> >> >> >
> >> >> > Signed-off-by: Sakib Sajal
> >> >> > ---
> >> >> > meta/conf/distro/include/tcmode-default.inc | 2 +-
> >> >> > .../go/{go-1.16.5.inc => go-1.17.inc} | 6 +-
> >> >> > ...ow-CC-and-CXX-to-have-multiple-words.patch | 10 ++-
> >> >> > ...ent-based-hash-generation-less-pedan.patch | 62
> +++---
> >> >> > ...-to-be-overridden-in-the-environment.patch | 18 --
> >> >> > ...4-ld-add-soname-to-shareable-objects.patch | 13 ++--
> >> >> > ...de-CC-when-building-dist-and-go_boot.patch | 15 +++--
> >> >> > ...dist-separate-host-and-target-builds.patch | 64
> ++-
> >> >> > ...d-go-make-GOROOT-precious-by-default.patch | 21 --
> >> >> > ...008-use-GOBUILDMODE-to-set-buildmode.patch | 9 ++-
> >> >> > ...go-make-sure-CC-and-CXX-are-absolute.patch | 45 ++---
> >> >> > ...ive_1.16.5.bb => go-binary-native_1.17.bb} | 4 +-
> >> >> > ...an_1.16.5.bb => go-cross-canadian_1.17.bb} | 0
> >> >> > .../{go-cross_1.16.5.bb => go-cross_1.17.bb} | 0
> >> >> > ...crosssdk_1.16.5.bb => go-crosssdk_1.17.bb} | 0
> >> >> > ...{go-native_1.16.5.bb => go-native_1.17.bb} | 0
> >> >> > ...o-runtime_1.16.5.bb => go-runtime_1.17.bb} | 0
> >> >> > .../go/{go_1.16.5.bb => go_1.17.bb} | 0
> >> >> > 18 files changed, 163 insertions(+), 106 deletions(-)
> >> >> > rename meta/recipes-devtools/go/{go-1.16.5.inc => go-1.17.inc}
> (85%)
> >> >> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0001-allow-CC-and-CXX-to-have-multiple-words.patch (80%)
> >> >> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0002-cmd-go-make-content-based-hash-generation-less-pedan.patch
> (80%)
> >> >> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0003-allow-GOTOOLDIR-to-be-overridden-in-the-environment.patch
> (78%)
> >> >> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0004-ld-add-soname-to-shareable-objects.patch (78%)
> >> >> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0005-make.bash-override-CC-when-building-dist-and-go_boot.patch
> (76%)
> >> >> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0006-cmd-dist-separate-host-and-target-builds.patch (90%)
> >> >> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0007-cmd-go-make-GOROOT-precious-by-default.patch (78%)
> >> >> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0008-use-GOBUILDMODE-to-set-buildmode.patch (84%)
> >> >> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch (75%)
> >> >> > rename meta/recipes-devtools/go/{go-binary-native_1.16.5.bb =>
> go-binary-native_1.17.bb} (83%)
> >> >> > rename meta/recipes-devtools/go/{go-cross-canadian_1.16.5.bb =>
> go-cross-canadian_1.17.bb} (100%)
> >> >> > rename meta/recipes-devtools/go/{go-cross_1.16.5.bb =>
> go-cross_1.17.bb} (100%)
> >> >> > rename meta/recipes-devtools/go/{go-crosssdk_1.16.5.bb =>
> go-crosssdk_1.17.bb} (100%)
> >> >> > rename meta/recipes-devtools/go/{go-native_1.16.5.bb =>
> go-native_1.17.bb} (100%)
> >> >> > rename meta/recipes-devtools/go/{go-runtime_1.16.5.bb =>
> go-runtime_1.17.bb} (100%)
> >> >> > rename meta/recipes-devtools/go/{go_1.16.5.bb => go_1.17.bb}
> (100%)
> >> >> >
> >> >> > diff --git a/meta/conf/distro/include/tcmode-default.inc
> b/meta/conf/distro/include/tcmode-default.inc
> >> >> > index 47f23f5c39..5b8a532943 100644
> >> >> > --- a/meta/conf/distro/include/tcmode-default.inc
> >> >>
Re: [OE-core] [PATCH] go: upgrade to 1.17 release
On Wed, Aug 25, 2021 at 3:14 PM Alexander Kanavin
wrote:
>
> On Wed, 25 Aug 2021 at 21:05, Bruce Ashfield wrote:
>>
>> Let's agree to disagree. Anyone doing toolchain work, needs to have an
>> extra level of caution.
>>
>> I'm constantly dealing with kernel issues and tightly coupled
>> applications in all layers that have nothing in core. I don't simply
>> tell people "go test it yourself".
>
>
> In that case, apologies, but you do need to be more clear in your request.
> Specifically tell what layers should be taken into the build, and what kind
> of testing, exactly, needs to be performed with them. Otherwise, you're just
> going to scare oe-core contributors away.
I mentioned meta-virtualization in the non-threaded part of this
discussion, so that specific information has been covered. Sakib is a
contributor there (and isn't new to core), and knows what he's doing,
hence why I have the luxury of being less detailed in the reponses.
I've said my bit on this, I'll pick up the pieces if anything ends up
breaking .. I'm just trying to be proactive since history shows that
go always breaks something.
Bruce
Bruce
>
> Alex
>
>
>>
>>
>> Cheers,
>>
>> Bruce
>>
>> > That said, I agree that it's a bit late to place this into oe-core now,
>> > and it's best to stash this until the start of the next cycle.
>> >
>> > Alex
>> >
>> >>
>> >>
>> >> Bruce
>> >>
>> >> >
>> >> > Sakib
>> >> >
>> >> > On 2021-08-25 1:20 p.m., Sakib Sajal wrote:
>> >> >
>> >> > go 1.17 includes small enhancements to the language.
>> >> > Release notes: https://golang.org/doc/go1.17
>> >> >
>> >> > Signed-off-by: Sakib Sajal
>> >> > ---
>> >> > meta/conf/distro/include/tcmode-default.inc | 2 +-
>> >> > .../go/{go-1.16.5.inc => go-1.17.inc} | 6 +-
>> >> > ...ow-CC-and-CXX-to-have-multiple-words.patch | 10 ++-
>> >> > ...ent-based-hash-generation-less-pedan.patch | 62 +++---
>> >> > ...-to-be-overridden-in-the-environment.patch | 18 --
>> >> > ...4-ld-add-soname-to-shareable-objects.patch | 13 ++--
>> >> > ...de-CC-when-building-dist-and-go_boot.patch | 15 +++--
>> >> > ...dist-separate-host-and-target-builds.patch | 64 ++-
>> >> > ...d-go-make-GOROOT-precious-by-default.patch | 21 --
>> >> > ...008-use-GOBUILDMODE-to-set-buildmode.patch | 9 ++-
>> >> > ...go-make-sure-CC-and-CXX-are-absolute.patch | 45 ++---
>> >> > ...ive_1.16.5.bb => go-binary-native_1.17.bb} | 4 +-
>> >> > ...an_1.16.5.bb => go-cross-canadian_1.17.bb} | 0
>> >> > .../{go-cross_1.16.5.bb => go-cross_1.17.bb} | 0
>> >> > ...crosssdk_1.16.5.bb => go-crosssdk_1.17.bb} | 0
>> >> > ...{go-native_1.16.5.bb => go-native_1.17.bb} | 0
>> >> > ...o-runtime_1.16.5.bb => go-runtime_1.17.bb} | 0
>> >> > .../go/{go_1.16.5.bb => go_1.17.bb} | 0
>> >> > 18 files changed, 163 insertions(+), 106 deletions(-)
>> >> > rename meta/recipes-devtools/go/{go-1.16.5.inc => go-1.17.inc} (85%)
>> >> > rename meta/recipes-devtools/go/{go-1.16 =>
>> >> > go-1.17}/0001-allow-CC-and-CXX-to-have-multiple-words.patch (80%)
>> >> > rename meta/recipes-devtools/go/{go-1.16 =>
>> >> > go-1.17}/0002-cmd-go-make-content-based-hash-generation-less-pedan.patch
>> >> > (80%)
>> >> > rename meta/recipes-devtools/go/{go-1.16 =>
>> >> > go-1.17}/0003-allow-GOTOOLDIR-to-be-overridden-in-the-environment.patch
>> >> > (78%)
>> >> > rename meta/recipes-devtools/go/{go-1.16 =>
>> >> > go-1.17}/0004-ld-add-soname-to-shareable-objects.patch (78%)
>> >> > rename meta/recipes-devtools/go/{go-1.16 =>
>> >> > go-1.17}/0005-make.bash-override-CC-when-building-dist-and-go_boot.patch
>> >> > (76%)
>> >> > rename meta/recipes-devtools/go/{go-1.16 =>
>> >> > go-1.17}/0006-cmd-dist-separate-host-and-target-builds.patch (90%)
>> >> > rename meta/recipes-devtools/go/{go-1.16 =>
>> >> > go-1.17}/0007-cmd-go-make-GOROOT-precious-by-default.patch (78%)
>> >> > rename meta/recipes-devtools/go/{go-1.16 =>
>> >> > go-1.17}/0008-use-GOBUILDMODE-to-set-buildmode.patch (84%)
>> >> > rename meta/recipes-devtools/go/{go-1.16 =>
>> >> > go-1.17}/0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch
>> >> > (75%)
>> >> > rename meta/recipes-devtools/go/{go-binary-native_1.16.5.bb =>
>> >> > go-binary-native_1.17.bb} (83%)
>> >> > rename meta/recipes-devtools/go/{go-cross-canadian_1.16.5.bb =>
>> >> > go-cross-canadian_1.17.bb} (100%)
>> >> > rename meta/recipes-devtools/go/{go-cross_1.16.5.bb =>
>> >> > go-cross_1.17.bb} (100%)
>> >> > rename meta/recipes-devtools/go/{go-crosssdk_1.16.5.bb =>
>> >> > go-crosssdk_1.17.bb} (100%)
>> >> > rename meta/recipes-devtools/go/{go-native_1.16.5.bb =>
>> >> > go-native_1.17.bb} (100%)
>> >> > rename meta/recipes-devtools/go/{go-runtime_1.16.5.bb =>
>> >> > go-runtime_1.17.bb} (100%)
>> >> > rename meta/recipes-devtools/go/{go_1.16.5.bb => go_1.17.bb} (100%)
>> >> >
>> >> > diff --git a/meta/conf/distro/include/tcmode-default.inc
>> >> >
Re: [OE-core] [PATCH] go: upgrade to 1.17 release
On Wed, 25 Aug 2021 at 21:05, Bruce Ashfield
wrote:
> Let's agree to disagree. Anyone doing toolchain work, needs to have an
> extra level of caution.
>
> I'm constantly dealing with kernel issues and tightly coupled
> applications in all layers that have nothing in core. I don't simply
> tell people "go test it yourself".
>
In that case, apologies, but you do need to be more clear in your request.
Specifically tell what layers should be taken into the build, and what kind
of testing, exactly, needs to be performed with them. Otherwise, you're
just going to scare oe-core contributors away.
Alex
>
> Cheers,
>
> Bruce
>
> > That said, I agree that it's a bit late to place this into oe-core now,
> and it's best to stash this until the start of the next cycle.
> >
> > Alex
> >
> >>
> >>
> >> Bruce
> >>
> >> >
> >> > Sakib
> >> >
> >> > On 2021-08-25 1:20 p.m., Sakib Sajal wrote:
> >> >
> >> > go 1.17 includes small enhancements to the language.
> >> > Release notes: https://golang.org/doc/go1.17
> >> >
> >> > Signed-off-by: Sakib Sajal
> >> > ---
> >> > meta/conf/distro/include/tcmode-default.inc | 2 +-
> >> > .../go/{go-1.16.5.inc => go-1.17.inc} | 6 +-
> >> > ...ow-CC-and-CXX-to-have-multiple-words.patch | 10 ++-
> >> > ...ent-based-hash-generation-less-pedan.patch | 62 +++---
> >> > ...-to-be-overridden-in-the-environment.patch | 18 --
> >> > ...4-ld-add-soname-to-shareable-objects.patch | 13 ++--
> >> > ...de-CC-when-building-dist-and-go_boot.patch | 15 +++--
> >> > ...dist-separate-host-and-target-builds.patch | 64
> ++-
> >> > ...d-go-make-GOROOT-precious-by-default.patch | 21 --
> >> > ...008-use-GOBUILDMODE-to-set-buildmode.patch | 9 ++-
> >> > ...go-make-sure-CC-and-CXX-are-absolute.patch | 45 ++---
> >> > ...ive_1.16.5.bb => go-binary-native_1.17.bb} | 4 +-
> >> > ...an_1.16.5.bb => go-cross-canadian_1.17.bb} | 0
> >> > .../{go-cross_1.16.5.bb => go-cross_1.17.bb} | 0
> >> > ...crosssdk_1.16.5.bb => go-crosssdk_1.17.bb} | 0
> >> > ...{go-native_1.16.5.bb => go-native_1.17.bb} | 0
> >> > ...o-runtime_1.16.5.bb => go-runtime_1.17.bb} | 0
> >> > .../go/{go_1.16.5.bb => go_1.17.bb} | 0
> >> > 18 files changed, 163 insertions(+), 106 deletions(-)
> >> > rename meta/recipes-devtools/go/{go-1.16.5.inc => go-1.17.inc} (85%)
> >> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0001-allow-CC-and-CXX-to-have-multiple-words.patch (80%)
> >> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0002-cmd-go-make-content-based-hash-generation-less-pedan.patch
> (80%)
> >> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0003-allow-GOTOOLDIR-to-be-overridden-in-the-environment.patch
> (78%)
> >> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0004-ld-add-soname-to-shareable-objects.patch (78%)
> >> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0005-make.bash-override-CC-when-building-dist-and-go_boot.patch
> (76%)
> >> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0006-cmd-dist-separate-host-and-target-builds.patch (90%)
> >> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0007-cmd-go-make-GOROOT-precious-by-default.patch (78%)
> >> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0008-use-GOBUILDMODE-to-set-buildmode.patch (84%)
> >> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch (75%)
> >> > rename meta/recipes-devtools/go/{go-binary-native_1.16.5.bb =>
> go-binary-native_1.17.bb} (83%)
> >> > rename meta/recipes-devtools/go/{go-cross-canadian_1.16.5.bb =>
> go-cross-canadian_1.17.bb} (100%)
> >> > rename meta/recipes-devtools/go/{go-cross_1.16.5.bb =>
> go-cross_1.17.bb} (100%)
> >> > rename meta/recipes-devtools/go/{go-crosssdk_1.16.5.bb =>
> go-crosssdk_1.17.bb} (100%)
> >> > rename meta/recipes-devtools/go/{go-native_1.16.5.bb =>
> go-native_1.17.bb} (100%)
> >> > rename meta/recipes-devtools/go/{go-runtime_1.16.5.bb =>
> go-runtime_1.17.bb} (100%)
> >> > rename meta/recipes-devtools/go/{go_1.16.5.bb => go_1.17.bb} (100%)
> >> >
> >> > diff --git a/meta/conf/distro/include/tcmode-default.inc
> b/meta/conf/distro/include/tcmode-default.inc
> >> > index 47f23f5c39..5b8a532943 100644
> >> > --- a/meta/conf/distro/include/tcmode-default.inc
> >> > +++ b/meta/conf/distro/include/tcmode-default.inc
> >> > @@ -23,7 +23,7 @@ GDBVERSION ?= "10.%"
> >> > GLIBCVERSION ?= "2.34"
> >> > LINUXLIBCVERSION ?= "5.13%"
> >> > QEMUVERSION ?= "6.0%"
> >> > -GOVERSION ?= "1.16%"
> >> > +GOVERSION ?= "1.17%"
> >> > # This can not use wildcards like 8.0.% since it is also used in
> mesa to denote
> >> > # llvm version being used, so always bump it with llvm recipe
> version bump
> >> > LLVMVERSION ?= "12.0.1"
> >> > diff --git a/meta/recipes-devtools/go/go-1.16.5.inc
> b/meta/recipes-devtools/go/go-1.17.inc
> >> > similarity index 85%
> >> > rename from
Re: [OE-core] [PATCH] go: upgrade to 1.17 release
On Wed, Aug 25, 2021 at 2:58 PM Alexander Kanavin
wrote:
>
> On Wed, 25 Aug 2021 at 19:45, Bruce Ashfield wrote:
>>
>> >
>> > bitbake core-image-full-cmdline && bitbake core-image-full-cmdline -c
>> > testimage
>> >
>> > Result:
>> >
>> > World build passes without warnings/errors.
>> >
>> > All image tests passed
>>
>> But do any of those test images have anything more than go ptests ?
>> They didn't last time I checked.
>
>
> But Bruce, it is not reasonable to ask for testing with anything else than
> oe-core, especially if the submitter has no idea what layers exactly that
> would be, and what kind of testing is supposed to be performed with them.
> If oe-core has testing gaps, then the gaps should be addressed, otherwise I
> think it's on you to cherry-pick the proposed update into your builds and run
> the tests you may have with all those other layers.
>
Let's agree to disagree. Anyone doing toolchain work, needs to have an
extra level of caution.
I'm constantly dealing with kernel issues and tightly coupled
applications in all layers that have nothing in core. I don't simply
tell people "go test it yourself".
Cheers,
Bruce
> That said, I agree that it's a bit late to place this into oe-core now, and
> it's best to stash this until the start of the next cycle.
>
> Alex
>
>>
>>
>> Bruce
>>
>> >
>> > Sakib
>> >
>> > On 2021-08-25 1:20 p.m., Sakib Sajal wrote:
>> >
>> > go 1.17 includes small enhancements to the language.
>> > Release notes: https://golang.org/doc/go1.17
>> >
>> > Signed-off-by: Sakib Sajal
>> > ---
>> > meta/conf/distro/include/tcmode-default.inc | 2 +-
>> > .../go/{go-1.16.5.inc => go-1.17.inc} | 6 +-
>> > ...ow-CC-and-CXX-to-have-multiple-words.patch | 10 ++-
>> > ...ent-based-hash-generation-less-pedan.patch | 62 +++---
>> > ...-to-be-overridden-in-the-environment.patch | 18 --
>> > ...4-ld-add-soname-to-shareable-objects.patch | 13 ++--
>> > ...de-CC-when-building-dist-and-go_boot.patch | 15 +++--
>> > ...dist-separate-host-and-target-builds.patch | 64 ++-
>> > ...d-go-make-GOROOT-precious-by-default.patch | 21 --
>> > ...008-use-GOBUILDMODE-to-set-buildmode.patch | 9 ++-
>> > ...go-make-sure-CC-and-CXX-are-absolute.patch | 45 ++---
>> > ...ive_1.16.5.bb => go-binary-native_1.17.bb} | 4 +-
>> > ...an_1.16.5.bb => go-cross-canadian_1.17.bb} | 0
>> > .../{go-cross_1.16.5.bb => go-cross_1.17.bb} | 0
>> > ...crosssdk_1.16.5.bb => go-crosssdk_1.17.bb} | 0
>> > ...{go-native_1.16.5.bb => go-native_1.17.bb} | 0
>> > ...o-runtime_1.16.5.bb => go-runtime_1.17.bb} | 0
>> > .../go/{go_1.16.5.bb => go_1.17.bb} | 0
>> > 18 files changed, 163 insertions(+), 106 deletions(-)
>> > rename meta/recipes-devtools/go/{go-1.16.5.inc => go-1.17.inc} (85%)
>> > rename meta/recipes-devtools/go/{go-1.16 =>
>> > go-1.17}/0001-allow-CC-and-CXX-to-have-multiple-words.patch (80%)
>> > rename meta/recipes-devtools/go/{go-1.16 =>
>> > go-1.17}/0002-cmd-go-make-content-based-hash-generation-less-pedan.patch
>> > (80%)
>> > rename meta/recipes-devtools/go/{go-1.16 =>
>> > go-1.17}/0003-allow-GOTOOLDIR-to-be-overridden-in-the-environment.patch
>> > (78%)
>> > rename meta/recipes-devtools/go/{go-1.16 =>
>> > go-1.17}/0004-ld-add-soname-to-shareable-objects.patch (78%)
>> > rename meta/recipes-devtools/go/{go-1.16 =>
>> > go-1.17}/0005-make.bash-override-CC-when-building-dist-and-go_boot.patch
>> > (76%)
>> > rename meta/recipes-devtools/go/{go-1.16 =>
>> > go-1.17}/0006-cmd-dist-separate-host-and-target-builds.patch (90%)
>> > rename meta/recipes-devtools/go/{go-1.16 =>
>> > go-1.17}/0007-cmd-go-make-GOROOT-precious-by-default.patch (78%)
>> > rename meta/recipes-devtools/go/{go-1.16 =>
>> > go-1.17}/0008-use-GOBUILDMODE-to-set-buildmode.patch (84%)
>> > rename meta/recipes-devtools/go/{go-1.16 =>
>> > go-1.17}/0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch (75%)
>> > rename meta/recipes-devtools/go/{go-binary-native_1.16.5.bb =>
>> > go-binary-native_1.17.bb} (83%)
>> > rename meta/recipes-devtools/go/{go-cross-canadian_1.16.5.bb =>
>> > go-cross-canadian_1.17.bb} (100%)
>> > rename meta/recipes-devtools/go/{go-cross_1.16.5.bb => go-cross_1.17.bb}
>> > (100%)
>> > rename meta/recipes-devtools/go/{go-crosssdk_1.16.5.bb =>
>> > go-crosssdk_1.17.bb} (100%)
>> > rename meta/recipes-devtools/go/{go-native_1.16.5.bb =>
>> > go-native_1.17.bb} (100%)
>> > rename meta/recipes-devtools/go/{go-runtime_1.16.5.bb =>
>> > go-runtime_1.17.bb} (100%)
>> > rename meta/recipes-devtools/go/{go_1.16.5.bb => go_1.17.bb} (100%)
>> >
>> > diff --git a/meta/conf/distro/include/tcmode-default.inc
>> > b/meta/conf/distro/include/tcmode-default.inc
>> > index 47f23f5c39..5b8a532943 100644
>> > --- a/meta/conf/distro/include/tcmode-default.inc
>> > +++ b/meta/conf/distro/include/tcmode-default.inc
>> > @@ -23,7 +23,7 @@ GDBVERSION ?= "10.%"
>> > GLIBCVERSION ?= "2.34"
>> >
Re: [OE-core] [PATCH] go: upgrade to 1.17 release
On Wed, 25 Aug 2021 at 19:45, Bruce Ashfield
wrote:
> >
> > bitbake core-image-full-cmdline && bitbake core-image-full-cmdline -c
> testimage
> >
> > Result:
> >
> > World build passes without warnings/errors.
> >
> > All image tests passed
>
> But do any of those test images have anything more than go ptests ?
> They didn't last time I checked.
>
But Bruce, it is not reasonable to ask for testing with anything else than
oe-core, especially if the submitter has no idea what layers exactly that
would be, and what kind of testing is supposed to be performed with them.
If oe-core has testing gaps, then the gaps should be addressed, otherwise I
think it's on you to cherry-pick the proposed update into your builds and
run the tests you may have with all those other layers.
That said, I agree that it's a bit late to place this into oe-core now, and
it's best to stash this until the start of the next cycle.
Alex
>
> Bruce
>
> >
> > Sakib
> >
> > On 2021-08-25 1:20 p.m., Sakib Sajal wrote:
> >
> > go 1.17 includes small enhancements to the language.
> > Release notes: https://golang.org/doc/go1.17
> >
> > Signed-off-by: Sakib Sajal
> > ---
> > meta/conf/distro/include/tcmode-default.inc | 2 +-
> > .../go/{go-1.16.5.inc => go-1.17.inc} | 6 +-
> > ...ow-CC-and-CXX-to-have-multiple-words.patch | 10 ++-
> > ...ent-based-hash-generation-less-pedan.patch | 62 +++---
> > ...-to-be-overridden-in-the-environment.patch | 18 --
> > ...4-ld-add-soname-to-shareable-objects.patch | 13 ++--
> > ...de-CC-when-building-dist-and-go_boot.patch | 15 +++--
> > ...dist-separate-host-and-target-builds.patch | 64 ++-
> > ...d-go-make-GOROOT-precious-by-default.patch | 21 --
> > ...008-use-GOBUILDMODE-to-set-buildmode.patch | 9 ++-
> > ...go-make-sure-CC-and-CXX-are-absolute.patch | 45 ++---
> > ...ive_1.16.5.bb => go-binary-native_1.17.bb} | 4 +-
> > ...an_1.16.5.bb => go-cross-canadian_1.17.bb} | 0
> > .../{go-cross_1.16.5.bb => go-cross_1.17.bb} | 0
> > ...crosssdk_1.16.5.bb => go-crosssdk_1.17.bb} | 0
> > ...{go-native_1.16.5.bb => go-native_1.17.bb} | 0
> > ...o-runtime_1.16.5.bb => go-runtime_1.17.bb} | 0
> > .../go/{go_1.16.5.bb => go_1.17.bb} | 0
> > 18 files changed, 163 insertions(+), 106 deletions(-)
> > rename meta/recipes-devtools/go/{go-1.16.5.inc => go-1.17.inc} (85%)
> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0001-allow-CC-and-CXX-to-have-multiple-words.patch (80%)
> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0002-cmd-go-make-content-based-hash-generation-less-pedan.patch
> (80%)
> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0003-allow-GOTOOLDIR-to-be-overridden-in-the-environment.patch
> (78%)
> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0004-ld-add-soname-to-shareable-objects.patch (78%)
> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0005-make.bash-override-CC-when-building-dist-and-go_boot.patch
> (76%)
> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0006-cmd-dist-separate-host-and-target-builds.patch (90%)
> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0007-cmd-go-make-GOROOT-precious-by-default.patch (78%)
> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0008-use-GOBUILDMODE-to-set-buildmode.patch (84%)
> > rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch (75%)
> > rename meta/recipes-devtools/go/{go-binary-native_1.16.5.bb =>
> go-binary-native_1.17.bb} (83%)
> > rename meta/recipes-devtools/go/{go-cross-canadian_1.16.5.bb =>
> go-cross-canadian_1.17.bb} (100%)
> > rename meta/recipes-devtools/go/{go-cross_1.16.5.bb => go-cross_1.17.bb}
> (100%)
> > rename meta/recipes-devtools/go/{go-crosssdk_1.16.5.bb =>
> go-crosssdk_1.17.bb} (100%)
> > rename meta/recipes-devtools/go/{go-native_1.16.5.bb =>
> go-native_1.17.bb} (100%)
> > rename meta/recipes-devtools/go/{go-runtime_1.16.5.bb =>
> go-runtime_1.17.bb} (100%)
> > rename meta/recipes-devtools/go/{go_1.16.5.bb => go_1.17.bb} (100%)
> >
> > diff --git a/meta/conf/distro/include/tcmode-default.inc
> b/meta/conf/distro/include/tcmode-default.inc
> > index 47f23f5c39..5b8a532943 100644
> > --- a/meta/conf/distro/include/tcmode-default.inc
> > +++ b/meta/conf/distro/include/tcmode-default.inc
> > @@ -23,7 +23,7 @@ GDBVERSION ?= "10.%"
> > GLIBCVERSION ?= "2.34"
> > LINUXLIBCVERSION ?= "5.13%"
> > QEMUVERSION ?= "6.0%"
> > -GOVERSION ?= "1.16%"
> > +GOVERSION ?= "1.17%"
> > # This can not use wildcards like 8.0.% since it is also used in mesa
> to denote
> > # llvm version being used, so always bump it with llvm recipe version
> bump
> > LLVMVERSION ?= "12.0.1"
> > diff --git a/meta/recipes-devtools/go/go-1.16.5.inc
> b/meta/recipes-devtools/go/go-1.17.inc
> > similarity index 85%
> > rename from meta/recipes-devtools/go/go-1.16.5.inc
> > rename to meta/recipes-devtools/go/go-1.17.inc
>
Re: [OE-core] [PATCH] go: upgrade to 1.17 release
On Wed, Aug 25, 2021 at 1:30 PM Sakib Sajal wrote:
>
> Testing done:
>
> bitbake -k world
I assume that only oe-core is in the bblayers ? or is it more extensive ?
>
> bitbake core-image-full-cmdline && bitbake core-image-full-cmdline -c
> testimage
>
> Result:
>
> World build passes without warnings/errors.
>
> All image tests passed
But do any of those test images have anything more than go ptests ?
They didn't last time I checked.
Bruce
>
> Sakib
>
> On 2021-08-25 1:20 p.m., Sakib Sajal wrote:
>
> go 1.17 includes small enhancements to the language.
> Release notes: https://golang.org/doc/go1.17
>
> Signed-off-by: Sakib Sajal
> ---
> meta/conf/distro/include/tcmode-default.inc | 2 +-
> .../go/{go-1.16.5.inc => go-1.17.inc} | 6 +-
> ...ow-CC-and-CXX-to-have-multiple-words.patch | 10 ++-
> ...ent-based-hash-generation-less-pedan.patch | 62 +++---
> ...-to-be-overridden-in-the-environment.patch | 18 --
> ...4-ld-add-soname-to-shareable-objects.patch | 13 ++--
> ...de-CC-when-building-dist-and-go_boot.patch | 15 +++--
> ...dist-separate-host-and-target-builds.patch | 64 ++-
> ...d-go-make-GOROOT-precious-by-default.patch | 21 --
> ...008-use-GOBUILDMODE-to-set-buildmode.patch | 9 ++-
> ...go-make-sure-CC-and-CXX-are-absolute.patch | 45 ++---
> ...ive_1.16.5.bb => go-binary-native_1.17.bb} | 4 +-
> ...an_1.16.5.bb => go-cross-canadian_1.17.bb} | 0
> .../{go-cross_1.16.5.bb => go-cross_1.17.bb} | 0
> ...crosssdk_1.16.5.bb => go-crosssdk_1.17.bb} | 0
> ...{go-native_1.16.5.bb => go-native_1.17.bb} | 0
> ...o-runtime_1.16.5.bb => go-runtime_1.17.bb} | 0
> .../go/{go_1.16.5.bb => go_1.17.bb} | 0
> 18 files changed, 163 insertions(+), 106 deletions(-)
> rename meta/recipes-devtools/go/{go-1.16.5.inc => go-1.17.inc} (85%)
> rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0001-allow-CC-and-CXX-to-have-multiple-words.patch (80%)
> rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0002-cmd-go-make-content-based-hash-generation-less-pedan.patch (80%)
> rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0003-allow-GOTOOLDIR-to-be-overridden-in-the-environment.patch (78%)
> rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0004-ld-add-soname-to-shareable-objects.patch (78%)
> rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0005-make.bash-override-CC-when-building-dist-and-go_boot.patch (76%)
> rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0006-cmd-dist-separate-host-and-target-builds.patch (90%)
> rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0007-cmd-go-make-GOROOT-precious-by-default.patch (78%)
> rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0008-use-GOBUILDMODE-to-set-buildmode.patch (84%)
> rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch (75%)
> rename meta/recipes-devtools/go/{go-binary-native_1.16.5.bb =>
> go-binary-native_1.17.bb} (83%)
> rename meta/recipes-devtools/go/{go-cross-canadian_1.16.5.bb =>
> go-cross-canadian_1.17.bb} (100%)
> rename meta/recipes-devtools/go/{go-cross_1.16.5.bb => go-cross_1.17.bb}
> (100%)
> rename meta/recipes-devtools/go/{go-crosssdk_1.16.5.bb =>
> go-crosssdk_1.17.bb} (100%)
> rename meta/recipes-devtools/go/{go-native_1.16.5.bb => go-native_1.17.bb}
> (100%)
> rename meta/recipes-devtools/go/{go-runtime_1.16.5.bb => go-runtime_1.17.bb}
> (100%)
> rename meta/recipes-devtools/go/{go_1.16.5.bb => go_1.17.bb} (100%)
>
> diff --git a/meta/conf/distro/include/tcmode-default.inc
> b/meta/conf/distro/include/tcmode-default.inc
> index 47f23f5c39..5b8a532943 100644
> --- a/meta/conf/distro/include/tcmode-default.inc
> +++ b/meta/conf/distro/include/tcmode-default.inc
> @@ -23,7 +23,7 @@ GDBVERSION ?= "10.%"
> GLIBCVERSION ?= "2.34"
> LINUXLIBCVERSION ?= "5.13%"
> QEMUVERSION ?= "6.0%"
> -GOVERSION ?= "1.16%"
> +GOVERSION ?= "1.17%"
> # This can not use wildcards like 8.0.% since it is also used in mesa to
> denote
> # llvm version being used, so always bump it with llvm recipe version bump
> LLVMVERSION ?= "12.0.1"
> diff --git a/meta/recipes-devtools/go/go-1.16.5.inc
> b/meta/recipes-devtools/go/go-1.17.inc
> similarity index 85%
> rename from meta/recipes-devtools/go/go-1.16.5.inc
> rename to meta/recipes-devtools/go/go-1.17.inc
> index 545aa0c828..6b412afe25 100644
> --- a/meta/recipes-devtools/go/go-1.16.5.inc
> +++ b/meta/recipes-devtools/go/go-1.17.inc
> @@ -1,7 +1,7 @@
> require go-common.inc
>
> -GO_BASEVERSION = "1.16"
> -PV = "1.16.5"
> +GO_BASEVERSION = "1.17"
> +PV = "1.17"
> FILESEXTRAPATHS:prepend := "${FILE_DIRNAME}/go-${GO_BASEVERSION}:"
>
> LIC_FILES_CHKSUM = "file://LICENSE;md5=5d4950ecb7b26d2c5e4e7b4e0dd74707"
> @@ -17,4 +17,4 @@ SRC_URI += "\
> file://0008-use-GOBUILDMODE-to-set-buildmode.patch \
> file://0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch \
> "
>
Re: [OE-core] [PATCH] go: upgrade to 1.17 release
Testing done:
bitbake -k world
bitbake core-image-full-cmdline && bitbake core-image-full-cmdline -c
testimage
Result:
World build passes without warnings/errors.
All image tests passed
Sakib
On 2021-08-25 1:20 p.m., Sakib Sajal wrote:
go 1.17 includes small enhancements to the language.
Release notes: https://golang.org/doc/go1.17
Signed-off-by: Sakib Sajal
---
meta/conf/distro/include/tcmode-default.inc | 2 +-
.../go/{go-1.16.5.inc => go-1.17.inc} | 6 +-
...ow-CC-and-CXX-to-have-multiple-words.patch | 10 ++-
...ent-based-hash-generation-less-pedan.patch | 62 +++---
...-to-be-overridden-in-the-environment.patch | 18 --
...4-ld-add-soname-to-shareable-objects.patch | 13 ++--
...de-CC-when-building-dist-and-go_boot.patch | 15 +++--
...dist-separate-host-and-target-builds.patch | 64 ++-
...d-go-make-GOROOT-precious-by-default.patch | 21 --
...008-use-GOBUILDMODE-to-set-buildmode.patch | 9 ++-
...go-make-sure-CC-and-CXX-are-absolute.patch | 45 ++---
...ive_1.16.5.bb => go-binary-native_1.17.bb} | 4 +-
...an_1.16.5.bb => go-cross-canadian_1.17.bb} | 0
.../{go-cross_1.16.5.bb => go-cross_1.17.bb} | 0
...crosssdk_1.16.5.bb => go-crosssdk_1.17.bb} | 0
...{go-native_1.16.5.bb => go-native_1.17.bb} | 0
...o-runtime_1.16.5.bb => go-runtime_1.17.bb} | 0
.../go/{go_1.16.5.bb => go_1.17.bb} | 0
18 files changed, 163 insertions(+), 106 deletions(-)
rename meta/recipes-devtools/go/{go-1.16.5.inc => go-1.17.inc} (85%)
rename meta/recipes-devtools/go/{go-1.16 =>
go-1.17}/0001-allow-CC-and-CXX-to-have-multiple-words.patch (80%)
rename meta/recipes-devtools/go/{go-1.16 =>
go-1.17}/0002-cmd-go-make-content-based-hash-generation-less-pedan.patch (80%)
rename meta/recipes-devtools/go/{go-1.16 =>
go-1.17}/0003-allow-GOTOOLDIR-to-be-overridden-in-the-environment.patch (78%)
rename meta/recipes-devtools/go/{go-1.16 =>
go-1.17}/0004-ld-add-soname-to-shareable-objects.patch (78%)
rename meta/recipes-devtools/go/{go-1.16 =>
go-1.17}/0005-make.bash-override-CC-when-building-dist-and-go_boot.patch (76%)
rename meta/recipes-devtools/go/{go-1.16 =>
go-1.17}/0006-cmd-dist-separate-host-and-target-builds.patch (90%)
rename meta/recipes-devtools/go/{go-1.16 =>
go-1.17}/0007-cmd-go-make-GOROOT-precious-by-default.patch (78%)
rename meta/recipes-devtools/go/{go-1.16 =>
go-1.17}/0008-use-GOBUILDMODE-to-set-buildmode.patch (84%)
rename meta/recipes-devtools/go/{go-1.16 =>
go-1.17}/0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch (75%)
rename meta/recipes-devtools/go/{go-binary-native_1.16.5.bb =>
go-binary-native_1.17.bb} (83%)
rename meta/recipes-devtools/go/{go-cross-canadian_1.16.5.bb =>
go-cross-canadian_1.17.bb} (100%)
rename meta/recipes-devtools/go/{go-cross_1.16.5.bb => go-cross_1.17.bb}
(100%)
rename meta/recipes-devtools/go/{go-crosssdk_1.16.5.bb =>
go-crosssdk_1.17.bb} (100%)
rename meta/recipes-devtools/go/{go-native_1.16.5.bb => go-native_1.17.bb}
(100%)
rename meta/recipes-devtools/go/{go-runtime_1.16.5.bb => go-runtime_1.17.bb}
(100%)
rename meta/recipes-devtools/go/{go_1.16.5.bb => go_1.17.bb} (100%)
diff --git a/meta/conf/distro/include/tcmode-default.inc
b/meta/conf/distro/include/tcmode-default.inc
index 47f23f5c39..5b8a532943 100644
--- a/meta/conf/distro/include/tcmode-default.inc
+++ b/meta/conf/distro/include/tcmode-default.inc
@@ -23,7 +23,7 @@ GDBVERSION ?= "10.%"
GLIBCVERSION ?= "2.34"
LINUXLIBCVERSION ?= "5.13%"
QEMUVERSION ?= "6.0%"
-GOVERSION ?= "1.16%"
+GOVERSION ?= "1.17%"
# This can not use wildcards like 8.0.% since it is also used in mesa to
denote
# llvm version being used, so always bump it with llvm recipe version bump
LLVMVERSION ?= "12.0.1"
diff --git a/meta/recipes-devtools/go/go-1.16.5.inc
b/meta/recipes-devtools/go/go-1.17.inc
similarity index 85%
rename from meta/recipes-devtools/go/go-1.16.5.inc
rename to meta/recipes-devtools/go/go-1.17.inc
index 545aa0c828..6b412afe25 100644
--- a/meta/recipes-devtools/go/go-1.16.5.inc
+++ b/meta/recipes-devtools/go/go-1.17.inc
@@ -1,7 +1,7 @@
require go-common.inc
-GO_BASEVERSION = "1.16"
-PV = "1.16.5"
+GO_BASEVERSION = "1.17"
+PV = "1.17"
FILESEXTRAPATHS:prepend := "${FILE_DIRNAME}/go-${GO_BASEVERSION}:"
LIC_FILES_CHKSUM = "file://LICENSE;md5=5d4950ecb7b26d2c5e4e7b4e0dd74707"
@@ -17,4 +17,4 @@ SRC_URI += "\
file://0008-use-GOBUILDMODE-to-set-buildmode.patch \
file://0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch \
"
-SRC_URI[main.sha256sum] =
"7bfa7e5908c7cc9e75da5ddf3066d7cbcf3fd9fa51945851325eebc17f50ba80"
+SRC_URI[main.sha256sum] =
"3a70e5055509f347c0fb831ca07a2bf3b531068f349b14a3c652e9b5b67beb5d"
diff --git
a/meta/recipes-devtools/go/go-1.16/0001-allow-CC-and-CXX-to-have-multiple-words.patch
b/meta/recipes-devtools/go/go-1.17/0001-allow-CC-and-CXX-to-have-multiple-words.patch
similarity index 80%
rename from
Re: [OE-core] [PATCH] go: upgrade to 1.17 release
On Wed, Aug 25, 2021 at 1:21 PM Sakib Sajal wrote:
>
> go 1.17 includes small enhancements to the language.
> Release notes: https://golang.org/doc/go1.17
What testing has been done on this update ?
This is late in the current development cycle, and layers like
meta-virt take the brunt of the breakage when we update go. So it
would be good to document how this has been tested, and if any of the
ecosystem layers have been smoke (compile) tested.
Bruce
>
> Signed-off-by: Sakib Sajal
> ---
> meta/conf/distro/include/tcmode-default.inc | 2 +-
> .../go/{go-1.16.5.inc => go-1.17.inc} | 6 +-
> ...ow-CC-and-CXX-to-have-multiple-words.patch | 10 ++-
> ...ent-based-hash-generation-less-pedan.patch | 62 +++---
> ...-to-be-overridden-in-the-environment.patch | 18 --
> ...4-ld-add-soname-to-shareable-objects.patch | 13 ++--
> ...de-CC-when-building-dist-and-go_boot.patch | 15 +++--
> ...dist-separate-host-and-target-builds.patch | 64 ++-
> ...d-go-make-GOROOT-precious-by-default.patch | 21 --
> ...008-use-GOBUILDMODE-to-set-buildmode.patch | 9 ++-
> ...go-make-sure-CC-and-CXX-are-absolute.patch | 45 ++---
> ...ive_1.16.5.bb => go-binary-native_1.17.bb} | 4 +-
> ...an_1.16.5.bb => go-cross-canadian_1.17.bb} | 0
> .../{go-cross_1.16.5.bb => go-cross_1.17.bb} | 0
> ...crosssdk_1.16.5.bb => go-crosssdk_1.17.bb} | 0
> ...{go-native_1.16.5.bb => go-native_1.17.bb} | 0
> ...o-runtime_1.16.5.bb => go-runtime_1.17.bb} | 0
> .../go/{go_1.16.5.bb => go_1.17.bb} | 0
> 18 files changed, 163 insertions(+), 106 deletions(-)
> rename meta/recipes-devtools/go/{go-1.16.5.inc => go-1.17.inc} (85%)
> rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0001-allow-CC-and-CXX-to-have-multiple-words.patch (80%)
> rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0002-cmd-go-make-content-based-hash-generation-less-pedan.patch (80%)
> rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0003-allow-GOTOOLDIR-to-be-overridden-in-the-environment.patch (78%)
> rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0004-ld-add-soname-to-shareable-objects.patch (78%)
> rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0005-make.bash-override-CC-when-building-dist-and-go_boot.patch (76%)
> rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0006-cmd-dist-separate-host-and-target-builds.patch (90%)
> rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0007-cmd-go-make-GOROOT-precious-by-default.patch (78%)
> rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0008-use-GOBUILDMODE-to-set-buildmode.patch (84%)
> rename meta/recipes-devtools/go/{go-1.16 =>
> go-1.17}/0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch (75%)
> rename meta/recipes-devtools/go/{go-binary-native_1.16.5.bb =>
> go-binary-native_1.17.bb} (83%)
> rename meta/recipes-devtools/go/{go-cross-canadian_1.16.5.bb =>
> go-cross-canadian_1.17.bb} (100%)
> rename meta/recipes-devtools/go/{go-cross_1.16.5.bb => go-cross_1.17.bb}
> (100%)
> rename meta/recipes-devtools/go/{go-crosssdk_1.16.5.bb =>
> go-crosssdk_1.17.bb} (100%)
> rename meta/recipes-devtools/go/{go-native_1.16.5.bb => go-native_1.17.bb}
> (100%)
> rename meta/recipes-devtools/go/{go-runtime_1.16.5.bb => go-runtime_1.17.bb}
> (100%)
> rename meta/recipes-devtools/go/{go_1.16.5.bb => go_1.17.bb} (100%)
>
> diff --git a/meta/conf/distro/include/tcmode-default.inc
> b/meta/conf/distro/include/tcmode-default.inc
> index 47f23f5c39..5b8a532943 100644
> --- a/meta/conf/distro/include/tcmode-default.inc
> +++ b/meta/conf/distro/include/tcmode-default.inc
> @@ -23,7 +23,7 @@ GDBVERSION ?= "10.%"
> GLIBCVERSION ?= "2.34"
> LINUXLIBCVERSION ?= "5.13%"
> QEMUVERSION ?= "6.0%"
> -GOVERSION ?= "1.16%"
> +GOVERSION ?= "1.17%"
> # This can not use wildcards like 8.0.% since it is also used in mesa to
> denote
> # llvm version being used, so always bump it with llvm recipe version bump
> LLVMVERSION ?= "12.0.1"
> diff --git a/meta/recipes-devtools/go/go-1.16.5.inc
> b/meta/recipes-devtools/go/go-1.17.inc
> similarity index 85%
> rename from meta/recipes-devtools/go/go-1.16.5.inc
> rename to meta/recipes-devtools/go/go-1.17.inc
> index 545aa0c828..6b412afe25 100644
> --- a/meta/recipes-devtools/go/go-1.16.5.inc
> +++ b/meta/recipes-devtools/go/go-1.17.inc
> @@ -1,7 +1,7 @@
> require go-common.inc
>
> -GO_BASEVERSION = "1.16"
> -PV = "1.16.5"
> +GO_BASEVERSION = "1.17"
> +PV = "1.17"
> FILESEXTRAPATHS:prepend := "${FILE_DIRNAME}/go-${GO_BASEVERSION}:"
>
> LIC_FILES_CHKSUM = "file://LICENSE;md5=5d4950ecb7b26d2c5e4e7b4e0dd74707"
> @@ -17,4 +17,4 @@ SRC_URI += "\
> file://0008-use-GOBUILDMODE-to-set-buildmode.patch \
> file://0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch \
> "
> -SRC_URI[main.sha256sum] =
> "7bfa7e5908c7cc9e75da5ddf3066d7cbcf3fd9fa51945851325eebc17f50ba80"
> +SRC_URI[main.sha256sum] =
>
[OE-core] [PATCH] go: upgrade to 1.17 release
go 1.17 includes small enhancements to the language.
Release notes: https://golang.org/doc/go1.17
Signed-off-by: Sakib Sajal
---
meta/conf/distro/include/tcmode-default.inc | 2 +-
.../go/{go-1.16.5.inc => go-1.17.inc} | 6 +-
...ow-CC-and-CXX-to-have-multiple-words.patch | 10 ++-
...ent-based-hash-generation-less-pedan.patch | 62 +++---
...-to-be-overridden-in-the-environment.patch | 18 --
...4-ld-add-soname-to-shareable-objects.patch | 13 ++--
...de-CC-when-building-dist-and-go_boot.patch | 15 +++--
...dist-separate-host-and-target-builds.patch | 64 ++-
...d-go-make-GOROOT-precious-by-default.patch | 21 --
...008-use-GOBUILDMODE-to-set-buildmode.patch | 9 ++-
...go-make-sure-CC-and-CXX-are-absolute.patch | 45 ++---
...ive_1.16.5.bb => go-binary-native_1.17.bb} | 4 +-
...an_1.16.5.bb => go-cross-canadian_1.17.bb} | 0
.../{go-cross_1.16.5.bb => go-cross_1.17.bb} | 0
...crosssdk_1.16.5.bb => go-crosssdk_1.17.bb} | 0
...{go-native_1.16.5.bb => go-native_1.17.bb} | 0
...o-runtime_1.16.5.bb => go-runtime_1.17.bb} | 0
.../go/{go_1.16.5.bb => go_1.17.bb} | 0
18 files changed, 163 insertions(+), 106 deletions(-)
rename meta/recipes-devtools/go/{go-1.16.5.inc => go-1.17.inc} (85%)
rename meta/recipes-devtools/go/{go-1.16 =>
go-1.17}/0001-allow-CC-and-CXX-to-have-multiple-words.patch (80%)
rename meta/recipes-devtools/go/{go-1.16 =>
go-1.17}/0002-cmd-go-make-content-based-hash-generation-less-pedan.patch (80%)
rename meta/recipes-devtools/go/{go-1.16 =>
go-1.17}/0003-allow-GOTOOLDIR-to-be-overridden-in-the-environment.patch (78%)
rename meta/recipes-devtools/go/{go-1.16 =>
go-1.17}/0004-ld-add-soname-to-shareable-objects.patch (78%)
rename meta/recipes-devtools/go/{go-1.16 =>
go-1.17}/0005-make.bash-override-CC-when-building-dist-and-go_boot.patch (76%)
rename meta/recipes-devtools/go/{go-1.16 =>
go-1.17}/0006-cmd-dist-separate-host-and-target-builds.patch (90%)
rename meta/recipes-devtools/go/{go-1.16 =>
go-1.17}/0007-cmd-go-make-GOROOT-precious-by-default.patch (78%)
rename meta/recipes-devtools/go/{go-1.16 =>
go-1.17}/0008-use-GOBUILDMODE-to-set-buildmode.patch (84%)
rename meta/recipes-devtools/go/{go-1.16 =>
go-1.17}/0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch (75%)
rename meta/recipes-devtools/go/{go-binary-native_1.16.5.bb =>
go-binary-native_1.17.bb} (83%)
rename meta/recipes-devtools/go/{go-cross-canadian_1.16.5.bb =>
go-cross-canadian_1.17.bb} (100%)
rename meta/recipes-devtools/go/{go-cross_1.16.5.bb => go-cross_1.17.bb} (100%)
rename meta/recipes-devtools/go/{go-crosssdk_1.16.5.bb => go-crosssdk_1.17.bb}
(100%)
rename meta/recipes-devtools/go/{go-native_1.16.5.bb => go-native_1.17.bb}
(100%)
rename meta/recipes-devtools/go/{go-runtime_1.16.5.bb => go-runtime_1.17.bb}
(100%)
rename meta/recipes-devtools/go/{go_1.16.5.bb => go_1.17.bb} (100%)
diff --git a/meta/conf/distro/include/tcmode-default.inc
b/meta/conf/distro/include/tcmode-default.inc
index 47f23f5c39..5b8a532943 100644
--- a/meta/conf/distro/include/tcmode-default.inc
+++ b/meta/conf/distro/include/tcmode-default.inc
@@ -23,7 +23,7 @@ GDBVERSION ?= "10.%"
GLIBCVERSION ?= "2.34"
LINUXLIBCVERSION ?= "5.13%"
QEMUVERSION ?= "6.0%"
-GOVERSION ?= "1.16%"
+GOVERSION ?= "1.17%"
# This can not use wildcards like 8.0.% since it is also used in mesa to denote
# llvm version being used, so always bump it with llvm recipe version bump
LLVMVERSION ?= "12.0.1"
diff --git a/meta/recipes-devtools/go/go-1.16.5.inc
b/meta/recipes-devtools/go/go-1.17.inc
similarity index 85%
rename from meta/recipes-devtools/go/go-1.16.5.inc
rename to meta/recipes-devtools/go/go-1.17.inc
index 545aa0c828..6b412afe25 100644
--- a/meta/recipes-devtools/go/go-1.16.5.inc
+++ b/meta/recipes-devtools/go/go-1.17.inc
@@ -1,7 +1,7 @@
require go-common.inc
-GO_BASEVERSION = "1.16"
-PV = "1.16.5"
+GO_BASEVERSION = "1.17"
+PV = "1.17"
FILESEXTRAPATHS:prepend := "${FILE_DIRNAME}/go-${GO_BASEVERSION}:"
LIC_FILES_CHKSUM = "file://LICENSE;md5=5d4950ecb7b26d2c5e4e7b4e0dd74707"
@@ -17,4 +17,4 @@ SRC_URI += "\
file://0008-use-GOBUILDMODE-to-set-buildmode.patch \
file://0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch \
"
-SRC_URI[main.sha256sum] =
"7bfa7e5908c7cc9e75da5ddf3066d7cbcf3fd9fa51945851325eebc17f50ba80"
+SRC_URI[main.sha256sum] =
"3a70e5055509f347c0fb831ca07a2bf3b531068f349b14a3c652e9b5b67beb5d"
diff --git
a/meta/recipes-devtools/go/go-1.16/0001-allow-CC-and-CXX-to-have-multiple-words.patch
b/meta/recipes-devtools/go/go-1.17/0001-allow-CC-and-CXX-to-have-multiple-words.patch
similarity index 80%
rename from
meta/recipes-devtools/go/go-1.16/0001-allow-CC-and-CXX-to-have-multiple-words.patch
rename to
meta/recipes-devtools/go/go-1.17/0001-allow-CC-and-CXX-to-have-multiple-words.patch
index 5f4823be22..8a833e05d3 100644
---
a/meta/recipes-devtools/go/go-1.16/0001-allow-CC-and-CXX-to-have-multiple-words.patch
[OE-core] [PATCH][dunfell] linux-yocto/5.4: update to v5.4.142
From: Bruce Ashfield
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
c15b830f7c1c Linux 5.4.142
a17f2f2c8949 KVM: nSVM: always intercept VMLOAD/VMSAVE when nested
(CVE-2021-3656)
7c1c96ffb658 KVM: nSVM: avoid picking up unsupported bits from L2 in
int_ctl (CVE-2021-3653)
456fd889227f iommu/vt-d: Fix agaw for a supported 48 bit guest address width
5b5f855a793c vmlinux.lds.h: Handle clang's module.{c,d}tor sections
e9b2b2b29ca8 ceph: take snap_empty_lock atomically with snaprealm refcount
change
95ff775df6ec ceph: clean up locking annotation for ceph_get_snap_realm and
__lookup_snap_realm
1d8c232afb03 ceph: add some lockdep assertions around snaprealm handling
a6ff0f3f9f90 KVM: VMX: Use current VMCS to query WAITPKG support for MSR
emulation
ec25d05e1893 PCI/MSI: Protect msi_desc::masked for multi-MSI
48d2439c6f2a PCI/MSI: Use msi_mask_irq() in pci_msi_shutdown()
386ead1d3598 PCI/MSI: Correct misleading comments
76d81dec16d0 PCI/MSI: Do not set invalid bits in MSI mask
6b4bcbf13390 PCI/MSI: Enforce MSI[X] entry updates to be visible
4495a41fbcd7 PCI/MSI: Enforce that MSI-X table entry is masked for update
1866c8f6d43c PCI/MSI: Mask all unused MSI-X entries
3b4220c2bf35 PCI/MSI: Enable and mask MSI-X early
0c8dea3fd55c genirq/timings: Prevent potential array overflow in
__irq_timings_store()
4dfe80927102 genirq/msi: Ensure deactivation on teardown
e3e54a930073 x86/resctrl: Fix default monitoring groups reporting
a6b594ad7419 x86/ioapic: Force affinity setup before startup
db5e2666946a x86/msi: Force affinity setup before startup
eda32c21882c genirq: Provide IRQCHIP_AFFINITY_PRE_STARTUP
06b347743608 x86/tools: Fix objdump version check again
74451dd8bfca powerpc/kprobes: Fix kprobe Oops happens in booke
b74145d858a8 nbd: Aovid double completion of a request
ad9550114d4c vsock/virtio: avoid potential deadlock when vsock device remove
b9cd73cce50a xen/events: Fix race in set_evtchn_to_irq
4d3c5c319b19 net: igmp: increase size of mr_ifc_count
721ff564cc6a tcp_bbr: fix u32 wrap bug in round logic if bbr_init() called
after 2B packets
2ce8a68a312c net: linkwatch: fix failure to restore device state across
suspend/resume
33597972a2e9 net: bridge: fix memleak in br_add_if()
f6eee53beb07 net: dsa: sja1105: fix broken backpressure in .port_fdb_dump
1e6a570d3786 net: dsa: lantiq: fix broken backpressure in .port_fdb_dump
564f6bbd0ed6 net: dsa: lan9303: fix broken backpressure in .port_fdb_dump
a9243455e874 net: igmp: fix data-race in igmp_ifc_timer_expire()
ed957c77b391 net: Fix memory leak in ieee802154_raw_deliver
13a381b8bc22 net: dsa: microchip: Fix ksz_read64()
991117e8 drm/meson: fix colour distortion from HDR set during vendor
u-boot
e114f15de881 net/mlx5: Fix return value from tracer initialization
f99aa76bb83c psample: Add a fwd declaration for skbuff
9dc8e396c12e iavf: Set RSS LUT and key in reset handle path
23436edae3c9 net: sched: act_mirred: Reset ct info when mirror/redirect skb
9636fbfe7bdd ppp: Fix generating ifname when empty IFLA_IFNAME is specified
1c31ee907fde net: phy: micrel: Fix link detection on ksz87xx switch"
dfeb64f6e2ce platform/x86: pcengines-apuv2: Add missing terminating entries
to gpio-lookup tables
699db2bb96ad platform/x86: pcengines-apuv2: revert wiring up simswitch GPIO
as LED
af7f1539cfb1 net: dsa: mt7530: add the missing RxUnicast MIB counter
d353a61860a2 ASoC: cs42l42: Fix LRCLK frame start edge
b036452082f3 netfilter: nf_conntrack_bridge: Fix memory leak when error
cd36a36ea4ea ASoC: cs42l42: Remove duplicate control for WNF filter
frequency
eb789cc9179f ASoC: cs42l42: Fix inversion of ADC Notch Switch control
6a3381336398 ASoC: cs42l42: Don't allow SND_SOC_DAIFMT_LEFT_J
55e86f07b85e ASoC: cs42l42: Correct definition of ADC Volume control
22d2e3c6a1b8 ieee802154: hwsim: fix GPF in hwsim_new_edge_nl
5bac8c2a3087 ieee802154: hwsim: fix GPF in hwsim_set_edge_lqi
ddcf807fbb70 libnvdimm/region: Fix label activation vs errors
bc97fde4c668 ACPI: NFIT: Fix support for virtual SPA ranges
a753e3f33405 ceph: reduce contention in ceph_check_delayed_caps()
aa04486c419d i2c: dev: zero out array used for i2c reads from userspace
c18b28e5ade8 ASoC: intel: atom: Fix reference to PCM buffer address
aab3fa544647 ASoC: xilinx: Fix reference to PCM buffer address
60e2854acf3b iio: adc: Fix incorrect exit of for-loop
bcac5225923b iio: humidity: hdc100x: Add margin to the conversion time
da7cb80905ec iio: adc: ti-ads7950: Ensure CS is deasserted after reading
channels
Signed-off-by: Bruce Ashfield
---
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-tiny_5.4.bb | 8 +++
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22
[OE-core] [PATCH 4/4] linux-yocto/5.10: update to v5.10.60
From: Bruce Ashfield
Updating linux-yocto/5.10 to the latest korg -stable release that comprises
the following commits:
2c5bd949b1df Linux 5.10.60
3a24e121304a net: dsa: microchip: ksz8795: Use software untagging on CPU
port
1e78179d75fb net: dsa: microchip: ksz8795: Fix VLAN untagged flag change on
deletion
5033d5e23155 net: dsa: microchip: ksz8795: Reject unsupported VLAN
configuration
60c007b52779 net: dsa: microchip: ksz8795: Fix PVID tag insertion
f365d53c8687 net: dsa: microchip: Fix probing KSZ87xx switch with DT node
for host port
3dc5666baf2a KVM: nSVM: always intercept VMLOAD/VMSAVE when nested
(CVE-2021-3656)
c0883f693187 KVM: nSVM: avoid picking up unsupported bits from L2 in
int_ctl (CVE-2021-3653)
b5f05bdfda28 vmlinux.lds.h: Handle clang's module.{c,d}tor sections
2fe07584a623 ceph: take snap_empty_lock atomically with snaprealm refcount
change
a23aced54c2c ceph: clean up locking annotation for ceph_get_snap_realm and
__lookup_snap_realm
b0efc93271ca ceph: add some lockdep assertions around snaprealm handling
dcdb587ac470 vboxsf: Add support for the atomic_open directory-inode op
7cd14c1a7fed vboxsf: Add vboxsf_[create|release]_sf_handle() helpers
433f0b31ebec KVM: nVMX: Use vmx_need_pf_intercept() when deciding if L0
wants a #PF
0ab67e3dfc4d KVM: VMX: Use current VMCS to query WAITPKG support for MSR
emulation
4a948c579ed6 efi/libstub: arm64: Double check image alignment at entry
fc7da433fa16 powerpc/smp: Fix OOPS in topology_init()
312730cd15e0 PCI/MSI: Protect msi_desc::masked for multi-MSI
724d0a985086 PCI/MSI: Use msi_mask_irq() in pci_msi_shutdown()
923368751866 PCI/MSI: Correct misleading comments
e42fb8e6161e PCI/MSI: Do not set invalid bits in MSI mask
042e03c9cdab PCI/MSI: Enforce MSI[X] entry updates to be visible
0b2509d7a90c PCI/MSI: Enforce that MSI-X table entry is masked for update
aa8092c1d1f1 PCI/MSI: Mask all unused MSI-X entries
7e90e81a4b59 PCI/MSI: Enable and mask MSI-X early
2d2c66848027 genirq/timings: Prevent potential array overflow in
__irq_timings_store()
355754194b48 genirq/msi: Ensure deactivation on teardown
f0736bed18fb x86/resctrl: Fix default monitoring groups reporting
25216ed97da8 x86/ioapic: Force affinity setup before startup
19fb5dabedca x86/msi: Force affinity setup before startup
4e52a4fe6f44 genirq: Provide IRQCHIP_AFFINITY_PRE_STARTUP
2a28b52306f2 x86/tools: Fix objdump version check again
4acc0d987141 powerpc/kprobes: Fix kprobe Oops happens in booke
015e2c900b5d efi/libstub: arm64: Relax 2M alignment again for relocatable
kernels
feb4a01d3ece efi/libstub: arm64: Force Image reallocation if BSS was not
reserved
afcb84e6cf8c arm64: efi: kaslr: Fix occasional random alloc (and boot)
failure
e0ee8d9c31b5 nbd: Aovid double completion of a request
f5cefe9a52a6 vsock/virtio: avoid potential deadlock when vsock device remove
dff830e5e723 xen/events: Fix race in set_evtchn_to_irq
65395b053d03 drm/i915: Only access SFC_DONE when media domain is not fused
off
430d91b3 net: igmp: increase size of mr_ifc_count
696afe28dc51 tcp_bbr: fix u32 wrap bug in round logic if bbr_init() called
after 2B packets
8976606ca347 net: linkwatch: fix failure to restore device state across
suspend/resume
4c2af90119ea net: bridge: fix memleak in br_add_if()
f333a5ca71c3 net: bridge: fix flags interpretation for extern learn fdb
entries
e3b949b86d09 net: bridge: validate the NUD_PERMANENT bit when adding an
extern_learn FDB entry
1cad01aca1fa net: dsa: sja1105: fix broken backpressure in .port_fdb_dump
56cc3408ff2a net: dsa: lantiq: fix broken backpressure in .port_fdb_dump
f7720b35cd32 net: dsa: lan9303: fix broken backpressure in .port_fdb_dump
24e1b7dbb174 net: igmp: fix data-race in igmp_ifc_timer_expire()
69b13167a636 net: Fix memory leak in ieee802154_raw_deliver
dbfaf7a6a23a net: dsa: microchip: ksz8795: Fix VLAN filtering
ccc1fe82c878 net: dsa: microchip: Fix ksz_read64()
558092b8ed31 drm/meson: fix colour distortion from HDR set during vendor
u-boot
6e1886465dea net/mlx5: Fix return value from tracer initialization
303ba011f5e1 net/mlx5: Synchronize correct IRQ when destroying CQ
00a0c11ddd72 bareudp: Fix invalid read beyond skb's linear data
30b1fc47f765 psample: Add a fwd declaration for skbuff
b3f0b170842c iavf: Set RSS LUT and key in reset handle path
a6192bae12e4 ice: don't remove netdev->dev_addr from uc sync list
bae5b521feaa ice: Prevent probing virtual functions
059238c52c61 net: sched: act_mirred: Reset ct info when mirror/redirect skb
f15f7716b047 net/smc: fix wait on already cleared link
51f4965d775e ppp: Fix generating ifname when empty IFLA_IFNAME is specified
046579c9fc28 net: phy: micrel: Fix link detection on ksz87xx switch"
e95620c3bdff bpf: Fix integer overflow
[OE-core] [PATCH 1/4] linux-yocto/5.13: update to v5.13.11
From: Bruce Ashfield Updating linux-yocto/5.13 to the latest korg -stable release that comprises the following commits: a3f1a03f54fc Linux 5.13.11 41812f4b8448 ovl: prevent private clone if bind mount is not allowed 2b187b56d531 ppp: Fix generating ppp unit id when ifname is not specified 9153106ca7e3 ALSA: hda: Add quirk for ASUS Flow x13 1252406498a6 ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 650 G8 Notebook PC c67b3ee8ca46 ALSA: pcm: Fix mmap breakage without explicit buffer setup 95421b33f9a2 bpf: Add lockdown check for probe_write_user helper ea56b15b909c firmware: tee_bnxt: Release TEE shm, session, and context during kexec a37da2be8e6c Linux 5.13.10 65485c34aa43 HID: ft260: fix device removal due to USB disconnect 6cf4cab9db7e platform/x86: gigabyte-wmi: add support for B550 Aorus Elite V2 37d363b3f6f7 drm/amdgpu/display: only enable aux backlight control for OLED panels 0505f8c628b9 smb3: rc uninitialized in one fallocate path b092186eb9e6 net/qla3xxx: fix schedule while atomic in ql_wait_for_drvr_lock and ql_adapter_reset 23f50e8ea008 alpha: Send stop IPI to send to online CPUs dd62ad1e49cc net: qede: Fix end of loop tests for list_for_each_entry f4c5021e7b3a virt_wifi: fix error on connect cd5a60de176c reiserfs: check directory items on read from disk 42b81b2b6766 reiserfs: add check for root_inode in reiserfs_fill_super aa54be4d1716 libata: fix ata_pio_sector for CONFIG_HIGHMEM fb9501ef203d riscv: dts: fix memory size for the SiFive HiFive Unmatched aa11124534b9 sched/rt: Fix double enqueue caused by rt_effective_prio bfdb06df02df perf/x86/amd: Don't touch the AMD64_EVENTSEL_HOSTONLY bit inside the guest 1de1a42a8590 soc: ixp4xx/qmgr: fix invalid __iomem access 8db20e539486 drm/i915: Correct SFC_DONE register offset 9f01d090be13 interconnect: qcom: icc-rpmh: Ensure floor BW is enforced for all nodes 019387e3c21f interconnect: Always call pre_aggregate before aggregate 39382972e727 interconnect: Zero initial BW after sync-state f2ca988aba4e spi: meson-spicc: fix memory leak in meson_spicc_remove e170a01152d2 usb: cdnsp: Fix incorrect supported maximum speed 95108645a282 usb: cdnsp: Fix the IMAN_IE_SET and IMAN_IE_CLEAR macro e9b413776d32 interconnect: Fix undersized devress_alloc allocation 6d74664e9843 soc: ixp4xx: fix printing resources 7a822dd050b1 KVM: x86/mmu: Fix per-cpu counter corruption on 32-bit builds 16375248cec6 KVM: Do not leak memory for duplicate debugfs directories 9a6772458f8e KVM: SVM: Fix off-by-one indexing when nullifying last used SEV VMCB 82c9a3098bbc KVM: x86: accept userspace interrupt only if no event is injected 642ffd390d67 s390/dasd: fix use after free in dasd path handling 6ed983ea4a12 io-wq: fix race between worker exiting and activating free worker 08ed8d676c94 md/raid10: properly indicate failure when ending a failed write request d6e1229a1bbb ARM: omap2+: hwmod: fix potential NULL pointer access b5f6bab9522e arm64: fix compat syscall return truncation a62784c80b1b Revert "gpio: mpc8xxx: change the gpio interrupt flags." 383d2836d2fa bus: ti-sysc: AM3: RNG is GP only 6e8de6c62763 selinux: correct the return value when loads initial sids f730f081a49b scsi: ibmvfc: Fix command state accounting and stale response detection 1cbbe89e6123 pcmcia: i82092: fix a null pointer dereference bug 60cd03514038 net/xfrm/compat: Copy xfrm_spdattr_type_t atributes d6bfaf682860 xfrm: Fix RCU vs hash_resize_mutex lock inversion 662a1fd0ec69 perf: Fix required permissions if sigtrap is requested 711f71b661ff virt: acrn: Do hcall_destroy_vm() before resource release 9ae78810a2b4 timers: Move clearing of base::timer_running under base:: Lock fafe9cf51f80 fpga: dfl: fme: Fix cpu hotplug issue in performance reporting 03d6da7c923f serial: 8250_pci: Avoid irq sharing for MSI(-X) interrupts. 134cbd486ac4 serial: 8250_pci: Enumerate Elkhart Lake UARTs via dedicated driver 9b2967bd9888 MIPS: Malta: Do not byte-swap accesses to the CBUS UART b321bb83a2c6 serial: 8250: fix handle_irq locking 979bd0e11d88 serial: 8250: Mask out floating 16/32-bit bus bits 19364aeb0b63 serial: 8250_mtk: fix uart corruption issue when rx power off b188f699e036 serial: tegra: Only print FIFO error message when an error occurs ddbd617df071 Revert "thunderbolt: Hide authorized attribute if router does not support PCIe tunnels" bc3c6b55a4ea ext4: fix potential htree corruption when growing large_dir directories e745e3033999 pipe: increase minimum default pipe size to 2 pages e58376a283bd media: rtl28xxu: fix zero-length control request e10d4de4ff5e drivers core: Fix oops when driver probe fails 9f57b942c4f3 staging: rtl8712: error handling refactoring e7565488445d staging: rtl8712: get rid of flush_scheduled_work
[OE-core] [PATCH 3/4] linux-yocto/5.13: update to v5.13.12
From: Bruce Ashfield Updating linux-yocto/5.13 to the latest korg -stable release that comprises the following commits: f428e49b8cb1 Linux 5.13.12 639a033fd765 KVM: nSVM: always intercept VMLOAD/VMSAVE when nested (CVE-2021-3656) a0949ee63cf9 KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl (CVE-2021-3653) 874213144352 kasan, slub: reset tag when printing address ac0e79584d41 ceph: take snap_empty_lock atomically with snaprealm refcount change dcd02a1248cc ceph: clean up locking annotation for ceph_get_snap_realm and __lookup_snap_realm 36b361cb1966 ceph: add some lockdep assertions around snaprealm handling 90d215367156 KVM: x86/mmu: Protect marking SPs unsync when using TDP MMU with spinlock 0f4bf029494d KVM: x86/mmu: Don't leak non-leaf SPTEs when zapping all SPTEs bd043e754f4d KVM: nVMX: Use vmx_need_pf_intercept() when deciding if L0 wants a #PF 1163cd462e1f KVM: VMX: Use current VMCS to query WAITPKG support for MSR emulation a3040e7e9ff2 locking/rtmutex: Use the correct rtmutex debugging config option b636a0d1e5c8 efi/libstub: arm64: Double check image alignment at entry 0e1d1392f381 powerpc/32: Fix critical and debug interrupts on BOOKE 4ce6f022df43 powerpc/xive: Do not skip CPU-less nodes when creating the IPIs 3b1700551dee powerpc/smp: Fix OOPS in topology_init() 115ff78c3a03 powerpc/32s: Fix napping restore in data storage interrupt (DSI) 3eda59bcee6e powerpc/pseries: Fix update of LPAR security flavor after LPM 33971cedf1d9 powerpc/interrupt: Do not call single_step_exception() from other exceptions 11aa5db61e9b PCI/MSI: Protect msi_desc::masked for multi-MSI b82047e5d807 PCI/MSI: Use msi_mask_irq() in pci_msi_shutdown() 849b6a5bde32 PCI/MSI: Correct misleading comments ea6cc94e8807 PCI/MSI: Do not set invalid bits in MSI mask 78225ed700df PCI/MSI: Enforce MSI[X] entry updates to be visible 0b51d4c16a27 PCI/MSI: Enforce that MSI-X table entry is masked for update 6c971252f090 PCI/MSI: Mask all unused MSI-X entries f800bb380fea PCI/MSI: Enable and mask MSI-X early 73d8b5769514 powerpc/interrupt: Fix OOPS by not calling do_IRQ() from timer_interrupt() 9dac5f65caaf genirq/timings: Prevent potential array overflow in __irq_timings_store() 0c081d4a6a13 genirq/msi: Ensure deactivation on teardown 0abb63311246 x86/resctrl: Fix default monitoring groups reporting 55cd80f4928c x86/ioapic: Force affinity setup before startup 067ef0204880 x86/msi: Force affinity setup before startup 24ed8f291d59 genirq: Provide IRQCHIP_AFFINITY_PRE_STARTUP 560051d8f439 x86/tools: Fix objdump version check again d8f9d8c4be6e i2c: iproc: fix race between client unreg and tasklet daf371e74d36 powerpc/kprobes: Fix kprobe Oops happens in booke 2bfb303470e0 efi/libstub: arm64: Relax 2M alignment again for relocatable kernels bfc48d02d915 efi/libstub: arm64: Force Image reallocation if BSS was not reserved f3409e925da2 KVM: arm64: Fix off-by-one in range_is_memory 14034883d058 arm64: efi: kaslr: Fix occasional random alloc (and boot) failure 98f73989055f nbd: Aovid double completion of a request 09625c5badd2 vsock/virtio: avoid potential deadlock when vsock device remove 128e480afe78 xen/events: Fix race in set_evtchn_to_irq 950429a4d346 drm/i915: Only access SFC_DONE when media domain is not fused off 9977d0baadc8 net: igmp: increase size of mr_ifc_count 4391389526a1 tcp_bbr: fix u32 wrap bug in round logic if bbr_init() called after 2B packets 53201f2902ee net: linkwatch: fix failure to restore device state across suspend/resume 59cabc513b8a net: bridge: fix memleak in br_add_if() ff6c9aad3599 net: bridge: fix flags interpretation for extern learn fdb entries c7c9cc4a6016 pinctrl: sunxi: Don't underestimate number of functions 735e90f3efa6 net: dsa: sja1105: fix broken backpressure in .port_fdb_dump 8398aab49ba3 net: dsa: lantiq: fix broken backpressure in .port_fdb_dump c6cbf5672cc0 net: dsa: lan9303: fix broken backpressure in .port_fdb_dump 22ecb3423f9c net: dsa: hellcreek: fix broken backpressure in .port_fdb_dump 52133524d807 net: igmp: fix data-race in igmp_ifc_timer_expire() 44c8aa996911 net: Fix memory leak in ieee802154_raw_deliver 74b264b342a5 net: dsa: microchip: ksz8795: Don't use phy_port_cnt in VLAN table lookup 1c4f28207fab net: dsa: microchip: ksz8795: Fix VLAN filtering 3cc015794dab net: dsa: microchip: ksz8795: Use software untagging on CPU port 9674dc6724c5 net: dsa: microchip: ksz8795: Fix VLAN untagged flag change on deletion 159948c423aa net: dsa: microchip: ksz8795: Reject unsupported VLAN configuration 3149f9edddf9 net: dsa: microchip: ksz8795: Fix PVID tag insertion 8154453a4be5 net: dsa: microchip: Fix ksz_read64() 037570c9adab bpf: Fix potentially incorrect results with bpf_get_local_storage()
[OE-core] [PATCH 2/4] linux-yocto/5.10: update to v5.10.59
From: Bruce Ashfield Updating linux-yocto/5.10 to the latest korg -stable release that comprises the following commits: 5805e5eec901 Linux 5.10.59 25cff25ec606 net: xilinx_emaclite: Do not print real IOMEM pointer 6a002d48a660 ovl: prevent private clone if bind mount is not allowed bffead8d3648 ppp: Fix generating ppp unit id when ifname is not specified 5df85901fe45 ALSA: hda: Add quirk for ASUS Flow x13 8930f2c60a45 ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 650 G8 Notebook PC 98c3fa3a9d7a ALSA: pcm: Fix mmap breakage without explicit buffer setup cc1a4dff23a4 USB:ehci:fix Kunpeng920 ehci hardware problem bd909fd3878d vboxsf: Make vboxsf_dir_create() return the handle for the created file 971703fc19cf vboxsf: Honor excl flag to the dir-inode create op 96b2232cb7e5 arm64: dts: renesas: beacon: Fix USB ref clock references e0dd4a0ab072 arm64: dts: renesas: beacon: Fix USB extal reference 0f47027d1b9b arm64: dts: renesas: rzg2: Add usb2_clksel to RZ/G2 M/N/H eaa7feecd366 mm: make zone_to_nid() and zone_set_nid() available for DISCONTIGMEM 0e709390372f Revert "selftests/resctrl: Use resctrl/info for feature detection" d8c38598701f bpf: Add lockdown check for probe_write_user helper 5b5064ea9a94 firmware: tee_bnxt: Release TEE shm, session, and context during kexec c5a625c6a4ac tee: Correct inappropriate usage of TEE_SHM_DMA_BUF flag 9f105d2d4f6c KVM: SVM: Fix off-by-one indexing when nullifying last used SEV VMCB 132a8267adab Linux 5.10.58 3d7d1b0f5f41 arm64: fix compat syscall return truncation bb65051dcd1f drm/amdgpu/display: only enable aux backlight control for OLED panels c8b7cfa674ee smb3: rc uninitialized in one fallocate path 8cfdd039ca18 net/qla3xxx: fix schedule while atomic in ql_wait_for_drvr_lock and ql_adapter_reset fbbb209268e5 alpha: Send stop IPI to send to online CPUs 13d0a9b3b917 net: qede: Fix end of loop tests for list_for_each_entry 1478e902bcbc virt_wifi: fix error on connect ecd8614809eb reiserfs: check directory items on read from disk dbe4f82fedc6 reiserfs: add check for root_inode in reiserfs_fill_super 0f05e0ffa247 libata: fix ata_pio_sector for CONFIG_HIGHMEM 11891adab23d drm/i915: avoid uninitialised var in eb_parse() a3e6bd0c71bb sched/rt: Fix double enqueue caused by rt_effective_prio c797b8872bb9 perf/x86/amd: Don't touch the AMD64_EVENTSEL_HOSTONLY bit inside the guest 2d94cffc94a5 soc: ixp4xx/qmgr: fix invalid __iomem access 7397034905ac drm/i915: Correct SFC_DONE register offset 16aecf1e36d9 interconnect: qcom: icc-rpmh: Ensure floor BW is enforced for all nodes 22b4917c85af interconnect: Always call pre_aggregate before aggregate ccfe4f62ff9f interconnect: Zero initial BW after sync-state 05565b469358 spi: meson-spicc: fix memory leak in meson_spicc_remove 1a084e78217d interconnect: Fix undersized devress_alloc allocation dcc23e58511b soc: ixp4xx: fix printing resources 37cbd27ef4b2 arm64: vdso: Avoid ISB after reading from cntvct_el0 7a2b5bb00f54 KVM: x86/mmu: Fix per-cpu counter corruption on 32-bit builds 32f55c25ee29 KVM: Do not leak memory for duplicate debugfs directories 309a31127bef KVM: x86: accept userspace interrupt only if no event is injected a786282b55b4 md/raid10: properly indicate failure when ending a failed write request 3d7d2d2b069b ARM: omap2+: hwmod: fix potential NULL pointer access 9851ad2f7107 Revert "gpio: mpc8xxx: change the gpio interrupt flags." 57c44e7ac788 bus: ti-sysc: AM3: RNG is GP only f4984f60acc7 selinux: correct the return value when loads initial sids 100f8396d154 pcmcia: i82092: fix a null pointer dereference bug afcd5a0e015f net/xfrm/compat: Copy xfrm_spdattr_type_t atributes f08b2d078cbb xfrm: Fix RCU vs hash_resize_mutex lock inversion 23e36a8610ca timers: Move clearing of base::timer_running under base:: Lock 9a69d0d24d69 fpga: dfl: fme: Fix cpu hotplug issue in performance reporting bfb5f1a12325 serial: 8250_pci: Avoid irq sharing for MSI(-X) interrupts. 0f30fedced7c serial: 8250_pci: Enumerate Elkhart Lake UARTs via dedicated driver 17f3c64f707b MIPS: Malta: Do not byte-swap accesses to the CBUS UART 8a1624f4a8d3 serial: 8250: Mask out floating 16/32-bit bus bits c03cef67157a serial: 8250_mtk: fix uart corruption issue when rx power off a4f8bfc919ee serial: tegra: Only print FIFO error message when an error occurs cc7300776808 ext4: fix potential htree corruption when growing large_dir directories 6b5a3d2c2b89 pipe: increase minimum default pipe size to 2 pages 556e7f204d34 media: rtl28xxu: fix zero-length control request 551e0c5d6b2e drivers core: Fix oops when driver probe fails faec2c68ea5f staging: rtl8712: error handling refactoring e468a357af68 staging: rtl8712: get rid of flush_scheduled_work 369101e39911 staging:
[OE-core] [PATCH 0/4] kernel-yocto: -stable version bumps
From: Bruce Ashfield Richard, Nothing too exciting here. These have all build locally and I haven't picked up any issues (I've stayed off the AB, due to the extra load you mentioned it has been under). Cheers, Bruce The following changes since commit c3e72164e7a0c51de04a9295e5f50c2e233965f7: libjitterentropy: remove contaminated hashequiv entry (2021-08-24 09:37:22 +0100) are available in the Git repository at: git://git.yoctoproject.org/poky-contrib zedd/kernel http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel Bruce Ashfield (4): linux-yocto/5.13: update to v5.13.11 linux-yocto/5.10: update to v5.10.59 linux-yocto/5.13: update to v5.13.12 linux-yocto/5.10: update to v5.10.60 .../linux/linux-yocto-rt_5.10.bb | 6 ++--- .../linux/linux-yocto-rt_5.13.bb | 6 ++--- .../linux/linux-yocto-tiny_5.10.bb| 8 +++--- .../linux/linux-yocto-tiny_5.13.bb| 8 +++--- meta/recipes-kernel/linux/linux-yocto_5.10.bb | 24 - meta/recipes-kernel/linux/linux-yocto_5.13.bb | 26 +-- 6 files changed, 39 insertions(+), 39 deletions(-) -- 2.19.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#155306): https://lists.openembedded.org/g/openembedded-core/message/155306 Mute This Topic: https://lists.openembedded.org/mt/85139175/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [hardknott][PATCH] openssl: upgrade from 1.1.1k to 1.1.1l
Includes fixes for:
CVE: CVE-2021-3711
CVE: CVE-2021-3712
as described by:
https://www.openssl.org/news/secadv/20210824.txt
Ptest results on qemux86-64 with kvm:
All tests successful.
Files=158, Tests=2532, 93 wallclock secs \
( 1.31 usr 0.14 sys + 73.43 cusr 12.65 csys = 87.53 CPU)
Result: PASS
DURATION: 93
Signed-off-by: Randy MacLeod
---
.../openssl/{openssl_1.1.1k.bb => openssl_1.1.1l.bb}| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-connectivity/openssl/{openssl_1.1.1k.bb =>
openssl_1.1.1l.bb} (98%)
diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.1k.bb
b/meta/recipes-connectivity/openssl/openssl_1.1.1l.bb
similarity index 98%
rename from meta/recipes-connectivity/openssl/openssl_1.1.1k.bb
rename to meta/recipes-connectivity/openssl/openssl_1.1.1l.bb
index e518cb6a02..9ea5c4c81f 100644
--- a/meta/recipes-connectivity/openssl/openssl_1.1.1k.bb
+++ b/meta/recipes-connectivity/openssl/openssl_1.1.1l.bb
@@ -28,7 +28,7 @@ SRC_URI_append_riscv32 = " \
file://0004-Fixup-support-for-io_pgetevents_time64-syscall.patch \
"
-SRC_URI[sha256sum] =
"892a0875b9872acd04a9fde79b1f943075d5ea162415de3047c327df33fbaee5"
+SRC_URI[sha256sum] =
"0b7a3e5e59c34827fe0c3a74b7ec8baef302b98fa80088d7f9153aa16fa76bd1"
inherit lib_package multilib_header multilib_script ptest
MULTILIB_SCRIPTS = "${PN}-bin:${bindir}/c_rehash"
--
2.30.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155305):
https://lists.openembedded.org/g/openembedded-core/message/155305
Mute This Topic: https://lists.openembedded.org/mt/85139043/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [oe-core][hardknott][PATCH 1/1] icu: increase pkgdata command buffer size
On 2021-08-24 1:01 p.m., Slater, Joseph wrote:
https://unicode-org.atlassian.net/browse/ICU-21702 has been accepted. My patch
just mitigates the problem but does not take care of issues around lack of
error reporting.
Joe
That's good. Can you update the patch to include that link
and pick a different Upstream-Status: such as "Submitted"
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status
so that when we eventually update we know where to check if the
change was made.
Thanks,
../Randy
-Original Message-
From: Mittal, Anuj
Sent: Monday, August 23, 2021 9:04 PM
To: Slater, Joseph ; openembedded-
c...@lists.openembedded.org
Cc: MacLeod, Randy
Subject: Re: [oe-core][hardknott][PATCH 1/1] icu: increase pkgdata command
buffer size
Hi Joe,
On Mon, 2021-08-23 at 14:29 -0700, Joe Slater wrote:
Mitigate pathname truncation when installing in a project with a very
long pathname. The patch is on the master branch, but they have moved
to a later version of icu so we cannot cherry-pick.
Signed-off-by: Joe Slater
---
...pkgdata-increase-command-buffer-size.patch | 43
+++
meta/recipes-support/icu/icu_68.2.bb | 1 +
2 files changed, 44 insertions(+)
create mode 100644
meta/recipes-support/icu/icu/0001-pkgdata-increase-
command-buffer-size.patch
diff --git a/meta/recipes-support/icu/icu/0001-pkgdata-increase-
command-buffer-size.patch b/meta/recipes-support/icu/icu/0001-pkgdata-
increase-command-buffer-size.patch
new file mode 100644
index 00..ea68e4be9f
--- /dev/null
+++ b/meta/recipes-support/icu/icu/0001-pkgdata-increase-command-
buffer-size.patch
@@ -0,0 +1,43 @@
+From ab6b1acdeed76899f8227c38ab7e7675c7673ff1 Mon Sep 17 00:00:00
+2001
+From: Joe Slater
+Date: Thu, 5 Aug 2021 09:23:48 -0700
+Subject: [PATCH 1/1] pkgdata: increase command buffer size
+
+Make cmd LARGE_BUFFER_SIZE to avoid pathname truncation when install
+paths are longer than about 150 characters.
+
+Upstream-Status: Pending
I think there was a comment from Alex on the original patch for master
requesting this be sent upstream first. Can you do that please?
Thanks,
Anuj
+
+Signed-off-by: Joe Slater
+---
+ source/tools/pkgdata/pkgdata.cpp | 6 +++---
+ 1 file changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/source/tools/pkgdata/pkgdata.cpp
b/source/tools/pkgdata/pkgdata.cpp
+index 5ab682e..d4b70ef 100644
+--- a/tools/pkgdata/pkgdata.cpp
b/tools/pkgdata/pkgdata.cpp
+@@ -1131,17 +1131,17 @@ normal_symlink_mode:
+
+ static int32_t pkg_installLibrary(const char *installDir, const char
*targetDir, UBool noVersion) {
+ int32_t result = 0;
+- char cmd[SMALL_BUFFER_MAX_SIZE];
++ char cmd[LARGE_BUFFER_MAX_SIZE];
+
+ auto ret = snprintf(cmd,
+- SMALL_BUFFER_MAX_SIZE,
++ LARGE_BUFFER_MAX_SIZE,
+ "cd %s && %s %s %s%s%s",
+ targetDir,
+ pkgDataFlags[INSTALL_CMD],
+ libFileNames[LIB_FILE_VERSION],
+ installDir, PKGDATA_FILE_SEP_STRING,
libFileNames[LIB_FILE_VERSION]);
+ (void)ret;
+- U_ASSERT(0 <= ret && ret < SMALL_BUFFER_MAX_SIZE);
++ U_ASSERT(0 <= ret && ret < LARGE_BUFFER_MAX_SIZE);
+
+ result = runCommand(cmd);
+
+--
+2.29.2
+
diff --git a/meta/recipes-support/icu/icu_68.2.bb b/meta/recipes-
support/icu/icu_68.2.bb index 1ca87feee4..130212d245 100644
--- a/meta/recipes-support/icu/icu_68.2.bb
+++ b/meta/recipes-support/icu/icu_68.2.bb
@@ -107,6 +107,7 @@ SRC_URI = "${BASE_SRC_URI};name=code \
file://filter.json \
file://fix-install-manx.patch \
file://0001-icu-Added-armeb-support.patch \
+ file://0001-pkgdata-increase-command-buffer-size.patch \
"
SRC_URI_append_class-target = "\
--
# Randy MacLeod
# Wind River Linux
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155304):
https://lists.openembedded.org/g/openembedded-core/message/155304
Mute This Topic: https://lists.openembedded.org/mt/85096835/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH] libcgroup: remove static pam library
On 8/25/21 1:10 AM, kai wrote:
From: Kai Kang
libpam disables static build by default, so remove static pam library of
libcgroup. Otherwise it complains QA issue:
| ERROR: libcgroup-2.0-r0 do_package: QA Issue: libcgroup:
Files/directories were installed but not shipped in any package:
| /lib/security/pam_cgroup.a
Signed-off-by: Kai Kang
---
meta/recipes-core/libcgroup/libcgroup_2.0.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/libcgroup/libcgroup_2.0.bb
b/meta/recipes-core/libcgroup/libcgroup_2.0.bb
index bc0a75d46c..f48b8ece9b 100644
--- a/meta/recipes-core/libcgroup/libcgroup_2.0.bb
+++ b/meta/recipes-core/libcgroup/libcgroup_2.0.bb
@@ -31,4 +31,5 @@ FILES:${PN}-dev += "${base_libdir}/security/*.la"
do_install:append() {
# Until we ship the test suite, this library isn't useful
rm -f ${D}${libdir}/libcgroupfortesting.*
+ rm -f ${D}${base_libdir}/security/pam_cgroup.a
}
should this be simply packaged into FILES_${PN}-staticdev instead ?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155303):
https://lists.openembedded.org/g/openembedded-core/message/155303
Mute This Topic: https://lists.openembedded.org/mt/85130950/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCHv2] lttng-modules: Make it build when CONFIG_TRACEPOINTS is not enabled again
Hello Peter,
On Wed, Aug 25, 2021 at 3:21 PM Peter Kjellerstedt
wrote:
>
> Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch was updated
> with the 2.13.0 update (commit 5dad15af), but unfortunately it no
> longer did what it was intended to do. There is also
> 0001-src-Kbuild-change-missing-CONFIG_TRACEPOINTS-to-warn.patch, which
> was based on the former patch, but it too does not solve the problem.
>
> Unify the two patches, and actually disable building of the kernel
> module if CONFIG_TRACEPOINTS is not enabled, the way it was intended.
>
> Signed-off-by: Peter Kjellerstedt
> ---
>
> PATCHv2: Unify
> Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch and
> 0001-src-Kbuild-change-missing-CONFIG_TRACEPOINTS-to-warn.patch into
> the latter, and use that both with and without devupstream.
I've tried the patch on my end, but it seems as if it does not resolve
the build issue entirely.
Compile stage is skipped with the message:
"lttng-modules-2.13.0/src/Kbuild:5: The option CONFIG_TRACEPOINTS
needs to be enabled in your kernel configuration"
which is totally fine.
However, the install fails due to the do_install:append in recipe
contains following:
do_install:append() {
# Delete empty directories to avoid QA failures if no modules were built
find ${D}/${nonarch_base_libdir} -depth -type d -empty -exec rmdir {} \;
}
Since there was no module produced by do_compile() -
${D}/${nonarch_base_libdir} is non-existent, and find fails.
I was wondering if you've seen the same build failure on your end?
Also, if I explicitly check for folder existence like following:
do_install:append() {
# Delete empty directories to avoid QA failures if no modules were built
if [ -d ${D}/${nonarch_base_libdir} ]; then
find ${D}/${nonarch_base_libdir} -depth -type d -empty
-exec rmdir {} \;
fi
}
then package is built fine.
Wonder if you would want to apply it in your patch set?
>
> ...e-missing-CONFIG_TRACEPOINTS-to-warn.patch | 25 +
> ...fail-if-CONFIG_TRACEPOINTS-is-not-en.patch | 37 ---
> .../lttng/lttng-modules_2.13.0.bb | 10 ++---
> 3 files changed, 21 insertions(+), 51 deletions(-)
> delete mode 100644
> meta/recipes-kernel/lttng/lttng-modules/Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch
>
--
Regards,
Andrey.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155302):
https://lists.openembedded.org/g/openembedded-core/message/155302
Mute This Topic: https://lists.openembedded.org/mt/85135221/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] How to build a devupstream variant of a recipe?
On Wed, Aug 25, 2021 at 9:51 AM Peter Kjellerstedt wrote: > > As I was recently looking at lttng-modules, which supports devupstream, I > wanted to try to build the devupstream variant. However, neither the > information in devupstream.bbclass nor the documentation in the manual were > of any help. Since it uses the BBCLASSEXTEND mechanism, I thought it would be > as simple as doing `bitbake lttng-modules-devupstream`, but that did not > work. So what is the correct way to build a devupstream variant of a recipe? Assuming that the devupstream variant/override doesn't modify PN (like we do in linux-yocto_5.13.bb), then it is selected by setting the preferred version to match the devupstream version. i.e. I have this in my local.conf for when I'm working on lttng devupstream: # this picks the devupstream version #PREFERRED_VERSION_lttng-modules = "2.13.0-rc2+git%" (and adjust the version to suit). Bruce > > //Peter > > > > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#155301): https://lists.openembedded.org/g/openembedded-core/message/155301 Mute This Topic: https://lists.openembedded.org/mt/85135811/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] How to build a devupstream variant of a recipe?
As I was recently looking at lttng-modules, which supports devupstream, I wanted to try to build the devupstream variant. However, neither the information in devupstream.bbclass nor the documentation in the manual were of any help. Since it uses the BBCLASSEXTEND mechanism, I thought it would be as simple as doing `bitbake lttng-modules-devupstream`, but that did not work. So what is the correct way to build a devupstream variant of a recipe? //Peter -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#155300): https://lists.openembedded.org/g/openembedded-core/message/155300 Mute This Topic: https://lists.openembedded.org/mt/85135811/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH] lttng-modules: Make it build when CONFIG_TRACEPOINTS is not enabled again
On Wed, Aug 25, 2021 at 9:40 AM Peter Kjellerstedt
wrote:
>
> > -Original Message-
> > From: Bruce Ashfield
> > Sent: den 25 augusti 2021 15:18
> > To: Peter Kjellerstedt
> > Cc: Andrey Zhizhikin ; OE Core mailing list
> >
> > Subject: Re: [OE-core] [PATCH] lttng-modules: Make it build when
> > CONFIG_TRACEPOINTS is not enabled again
> >
> > On Wed, Aug 25, 2021 at 8:57 AM Peter Kjellerstedt
> > wrote:
> > >
> > > > -Original Message-
> > > > From: Andrey Zhizhikin
> > > > Sent: den 25 augusti 2021 12:20
> > > > To: Peter Kjellerstedt
> > > > Cc: Bruce Ashfield ; OE Core mailing list
> > > >
> > > > Subject: Re: [OE-core] [PATCH] lttng-modules: Make it build when
> > > > CONFIG_TRACEPOINTS is not enabled again
> > > >
> > > > Hello Peter,
> > > >
> > > > On Wed, Aug 25, 2021 at 11:41 AM Peter Kjellerstedt
> > > > wrote:
> > > > >
> > > > > Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch was
> > updated
> > > > > with the 2.13.0 update (commit 5dad15af), but unfortunately it no
> > longer
> > > > > did what it was intended to do.
> > > > >
> > > > > Signed-off-by: Peter Kjellerstedt
> > > > > ---
> > > > > ...fail-if-CONFIG_TRACEPOINTS-is-not-en.patch | 42 +++-
> > ---
> > > > > 1 file changed, 25 insertions(+), 17 deletions(-)
> > > > >
> > > > > diff --git a/meta/recipes-kernel/lttng/lttng-modules/Makefile-Do-
> > not-
> > > > fail-if-CONFIG_TRACEPOINTS-is-not-en.patch b/meta/recipes-
> > > > kernel/lttng/lttng-modules/Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-
> > is-
> > > > not-en.patch
> > > >
> > > > I guess the patch you've refreshed is not a correct one...
> > > >
> > > > There is another patch introduced by Bruce in the commit 18bf7b0
> > > > ("lttng-modules: update devupstream to v2.13-rc "), namely
> > > > 0001-src-Kbuild-change-missing-CONFIG_TRACEPOINTS-to-warn.patch
> > > >
> > > > It make sense to refresh rather that one instead of the Makefile one,
> > > > and have it included in the SRC_URI (see discussion in
> > > > https://lists.openembedded.org/g/openembedded-
> > core/topic/84950303#154888).
> > > >
> > > > --
> > > > Regards,
> > > > Andrey.
> > >
> > > Right, I had missed that there were two patches doing the same thing
> > > (though neither actually solved the problem after the update to 2.13.0).
> > > I will send an updated review unifying the patches and adding my
> > solution
> > > to disable building the module when CONFIG_TRACEPOINTS is not enabled.
> > >
> >
> > We really should stop dragging these patches along at all.
> >
> > I have a unified set of patches here as well, but continuing to allow
> > lttng modules to build in configurations like these, just doesn't make
> > sense (which is why I haven't sent them).
> >
> > We should have a distro feature, and simply drop it from package lists
> > when appropriate.
> >
> > Bruce
> >
> > > //Peter
>
> I know nothing about lttng myself, but has passed on your concerns to our
> maintainer for the functionality. Unfortunately he is on vacation for a
> couple of weeks more, so I do not know when I can expect an answer from
> him.
>
No worries.
> So for now I hope we can update the recipe per my patches so that it
> continues to work as before, and then we can take the discussion of
> whether it should be possible to build lttng-modules without
> CONFIG_TRACEPOINTS enabled separately.
Agreed.
I've chucked my patches that fixed the build here as well, since they
were very similar to yours.
I'll continue creating a dummy package / distro feature option here,
since pulling those patches along is a particular pain point for me, as
I continually hit lttng issues as I work through new kernels :D
Bruce
>
> //Peter
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155299):
https://lists.openembedded.org/g/openembedded-core/message/155299
Mute This Topic: https://lists.openembedded.org/mt/85131925/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH] lttng-modules: Make it build when CONFIG_TRACEPOINTS is not enabled again
> -Original Message-
> From: Bruce Ashfield
> Sent: den 25 augusti 2021 15:18
> To: Peter Kjellerstedt
> Cc: Andrey Zhizhikin ; OE Core mailing list
>
> Subject: Re: [OE-core] [PATCH] lttng-modules: Make it build when
> CONFIG_TRACEPOINTS is not enabled again
>
> On Wed, Aug 25, 2021 at 8:57 AM Peter Kjellerstedt
> wrote:
> >
> > > -Original Message-
> > > From: Andrey Zhizhikin
> > > Sent: den 25 augusti 2021 12:20
> > > To: Peter Kjellerstedt
> > > Cc: Bruce Ashfield ; OE Core mailing list
> > >
> > > Subject: Re: [OE-core] [PATCH] lttng-modules: Make it build when
> > > CONFIG_TRACEPOINTS is not enabled again
> > >
> > > Hello Peter,
> > >
> > > On Wed, Aug 25, 2021 at 11:41 AM Peter Kjellerstedt
> > > wrote:
> > > >
> > > > Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch was
> updated
> > > > with the 2.13.0 update (commit 5dad15af), but unfortunately it no
> longer
> > > > did what it was intended to do.
> > > >
> > > > Signed-off-by: Peter Kjellerstedt
> > > > ---
> > > > ...fail-if-CONFIG_TRACEPOINTS-is-not-en.patch | 42 +++-
> ---
> > > > 1 file changed, 25 insertions(+), 17 deletions(-)
> > > >
> > > > diff --git a/meta/recipes-kernel/lttng/lttng-modules/Makefile-Do-
> not-
> > > fail-if-CONFIG_TRACEPOINTS-is-not-en.patch b/meta/recipes-
> > > kernel/lttng/lttng-modules/Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-
> is-
> > > not-en.patch
> > >
> > > I guess the patch you've refreshed is not a correct one...
> > >
> > > There is another patch introduced by Bruce in the commit 18bf7b0
> > > ("lttng-modules: update devupstream to v2.13-rc "), namely
> > > 0001-src-Kbuild-change-missing-CONFIG_TRACEPOINTS-to-warn.patch
> > >
> > > It make sense to refresh rather that one instead of the Makefile one,
> > > and have it included in the SRC_URI (see discussion in
> > > https://lists.openembedded.org/g/openembedded-
> core/topic/84950303#154888).
> > >
> > > --
> > > Regards,
> > > Andrey.
> >
> > Right, I had missed that there were two patches doing the same thing
> > (though neither actually solved the problem after the update to 2.13.0).
> > I will send an updated review unifying the patches and adding my
> solution
> > to disable building the module when CONFIG_TRACEPOINTS is not enabled.
> >
>
> We really should stop dragging these patches along at all.
>
> I have a unified set of patches here as well, but continuing to allow
> lttng modules to build in configurations like these, just doesn't make
> sense (which is why I haven't sent them).
>
> We should have a distro feature, and simply drop it from package lists
> when appropriate.
>
> Bruce
>
> > //Peter
I know nothing about lttng myself, but has passed on your concerns to our
maintainer for the functionality. Unfortunately he is on vacation for a
couple of weeks more, so I do not know when I can expect an answer from
him.
So for now I hope we can update the recipe per my patches so that it
continues to work as before, and then we can take the discussion of
whether it should be possible to build lttng-modules without
CONFIG_TRACEPOINTS enabled separately.
//Peter
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155298):
https://lists.openembedded.org/g/openembedded-core/message/155298
Mute This Topic: https://lists.openembedded.org/mt/85131925/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCHv2] lttng-modules: Make it build when CONFIG_TRACEPOINTS is not enabled again
Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch was updated with the 2.13.0 update (commit 5dad15af), but unfortunately it no longer did what it was intended to do. There is also 0001-src-Kbuild-change-missing-CONFIG_TRACEPOINTS-to-warn.patch, which was based on the former patch, but it too does not solve the problem. Unify the two patches, and actually disable building of the kernel module if CONFIG_TRACEPOINTS is not enabled, the way it was intended. Signed-off-by: Peter Kjellerstedt --- PATCHv2: Unify Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch and 0001-src-Kbuild-change-missing-CONFIG_TRACEPOINTS-to-warn.patch into the latter, and use that both with and without devupstream. ...e-missing-CONFIG_TRACEPOINTS-to-warn.patch | 25 + ...fail-if-CONFIG_TRACEPOINTS-is-not-en.patch | 37 --- .../lttng/lttng-modules_2.13.0.bb | 10 ++--- 3 files changed, 21 insertions(+), 51 deletions(-) delete mode 100644 meta/recipes-kernel/lttng/lttng-modules/Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch diff --git a/meta/recipes-kernel/lttng/lttng-modules/0001-src-Kbuild-change-missing-CONFIG_TRACEPOINTS-to-warn.patch b/meta/recipes-kernel/lttng/lttng-modules/0001-src-Kbuild-change-missing-CONFIG_TRACEPOINTS-to-warn.patch index 6d81c81efe..76a5787c37 100644 --- a/meta/recipes-kernel/lttng/lttng-modules/0001-src-Kbuild-change-missing-CONFIG_TRACEPOINTS-to-warn.patch +++ b/meta/recipes-kernel/lttng/lttng-modules/0001-src-Kbuild-change-missing-CONFIG_TRACEPOINTS-to-warn.patch @@ -1,4 +1,4 @@ -From 0287f5c32b9fd99078e71c22ca679343d18f1513 Mon Sep 17 00:00:00 2001 +From 878f89b6136ff7b870a19e04901cc6f316bbe10a Mon Sep 17 00:00:00 2001 From: Bruce Ashfield Date: Sat, 15 May 2021 10:26:38 -0400 Subject: [PATCH] src/Kbuild: change missing CONFIG_TRACEPOINTS to warning @@ -16,22 +16,31 @@ Upstream-Status: Inappropriate [embedded specific] Signed-off-by: Bruce Ashfield --- - src/Kbuild | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) + src/Kbuild | 7 ++- + 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/src/Kbuild b/src/Kbuild -index 7137874f..18a43b50 100644 +index 7137874..04eb5c9 100644 --- a/src/Kbuild +++ b/src/Kbuild -@@ -2,7 +2,7 @@ +@@ -2,10 +2,13 @@ ifdef CONFIG_LOCALVERSION # Check if dot-config is included. ifeq ($(CONFIG_TRACEPOINTS),) -$(error The option CONFIG_TRACEPOINTS needs to be enabled in your kernel configuration) +$(warning The option CONFIG_TRACEPOINTS needs to be enabled in your kernel configuration) ++DISABLE_MODULE = y endif # CONFIG_TRACEPOINTS endif # ifdef CONFIG_LOCALVERSION --- -2.19.1 - ++ifneq ($(DISABLE_MODULE),y) ++ + TOP_LTTNG_MODULES_DIR := $(shell dirname $(lastword $(MAKEFILE_LIST)))/.. + + lttng_check_linux_version = $(shell pwd)/include/linux/version.h +@@ -150,3 +153,5 @@ lttng-statedump-objs := lttng-statedump-impl.o + obj-$(CONFIG_LTTNG) += probes/ + obj-$(CONFIG_LTTNG) += lib/ + obj-$(CONFIG_LTTNG) += tests/ ++ ++endif # DISABLE_MODULE diff --git a/meta/recipes-kernel/lttng/lttng-modules/Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch b/meta/recipes-kernel/lttng/lttng-modules/Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch deleted file mode 100644 index a852834344..00 --- a/meta/recipes-kernel/lttng/lttng-modules/Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch +++ /dev/null @@ -1,37 +0,0 @@ -From 1b0e574d680101105a6c1e8931c78824f5a97a42 Mon Sep 17 00:00:00 2001 -From: Otavio Salvador -Date: Mon, 5 Sep 2016 17:08:56 + -Subject: [PATCH] Makefile: Do not fail if CONFIG_TRACEPOINTS is not enabled -Organization: O.S. Systems Software LTDA. - -The lttng-modules are being pulled by the tools-profile image feature, -however, not every kernel has the CONFIG_TRACEPOINTS feature enabled. - -This change makes the build do not fail when CONFIG_TRACEPOINTS is not -available, allowing it to be kept being pulled by default. - -Upstream-Status: Inappropriate [embedded specific] - -Signed-off-by: Otavio Salvador -[bva: modified for lttng-modules 2.13+ context] -Signed-off-by: Bruce Ashfield - Makefile | 9 + - 1 file changed, 5 insertions(+), 4 deletions(-) - -Index: lttng-modules-2.13.0/Makefile -=== lttng-modules-2.13.0.orig/Makefile -+++ lttng-modules-2.13.0/Makefile -@@ -7,6 +7,11 @@ - - obj-$(CONFIG_LTTNG) += src/ - -+ ifdef CONFIG_LOCALVERSION # Check if dot-config is included. -+ifneq ($(CONFIG_TRACEPOINTS),) -+ $(warning The option CONFIG_TRACEPOINTS needs to be enabled in your kernel configuration) -+endif # CONFIG_TRACEPOINTS -+ endif # ifdef CONFIG_LOCALVERSION - else # KERNELRELEASE - - # This part of the Makefile is used when the 'make' command is runned in the diff --git a/meta/recipes-kernel/lttng/lttng-modules_2.13.0.bb b/meta/recipes-kernel/lttng/lttng-modules_2.13.0.bb
Re: [OE-core] [PATCH] lttng-modules: Make it build when CONFIG_TRACEPOINTS is not enabled again
On Wed, Aug 25, 2021 at 8:57 AM Peter Kjellerstedt
wrote:
>
> > -Original Message-
> > From: Andrey Zhizhikin
> > Sent: den 25 augusti 2021 12:20
> > To: Peter Kjellerstedt
> > Cc: Bruce Ashfield ; OE Core mailing list
> >
> > Subject: Re: [OE-core] [PATCH] lttng-modules: Make it build when
> > CONFIG_TRACEPOINTS is not enabled again
> >
> > Hello Peter,
> >
> > On Wed, Aug 25, 2021 at 11:41 AM Peter Kjellerstedt
> > wrote:
> > >
> > > Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch was updated
> > > with the 2.13.0 update (commit 5dad15af), but unfortunately it no longer
> > > did what it was intended to do.
> > >
> > > Signed-off-by: Peter Kjellerstedt
> > > ---
> > > ...fail-if-CONFIG_TRACEPOINTS-is-not-en.patch | 42 +++
> > > 1 file changed, 25 insertions(+), 17 deletions(-)
> > >
> > > diff --git a/meta/recipes-kernel/lttng/lttng-modules/Makefile-Do-not-
> > fail-if-CONFIG_TRACEPOINTS-is-not-en.patch b/meta/recipes-
> > kernel/lttng/lttng-modules/Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-
> > not-en.patch
> >
> > I guess the patch you've refreshed is not a correct one...
> >
> > There is another patch introduced by Bruce in the commit 18bf7b0
> > ("lttng-modules: update devupstream to v2.13-rc "), namely
> > 0001-src-Kbuild-change-missing-CONFIG_TRACEPOINTS-to-warn.patch
> >
> > It make sense to refresh rather that one instead of the Makefile one,
> > and have it included in the SRC_URI (see discussion in
> > https://lists.openembedded.org/g/openembedded-core/topic/84950303#154888).
> >
> > --
> > Regards,
> > Andrey.
>
> Right, I had missed that there were two patches doing the same thing
> (though neither actually solved the problem after the update to 2.13.0).
> I will send an updated review unifying the patches and adding my solution
> to disable building the module when CONFIG_TRACEPOINTS is not enabled.
>
We really should stop dragging these patches along at all.
I have a unified set of patches here as well, but continuing to allow
lttng modules to build in configurations like these, just doesn't make
sense (which is why I haven't sent them).
We should have a distro feature, and simply drop it from package lists
when appropriate.
Bruce
> //Peter
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155296):
https://lists.openembedded.org/g/openembedded-core/message/155296
Mute This Topic: https://lists.openembedded.org/mt/85131925/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH] lttng-modules: Make it build when CONFIG_TRACEPOINTS is not enabled again
> -Original Message-
> From: Andrey Zhizhikin
> Sent: den 25 augusti 2021 12:20
> To: Peter Kjellerstedt
> Cc: Bruce Ashfield ; OE Core mailing list
>
> Subject: Re: [OE-core] [PATCH] lttng-modules: Make it build when
> CONFIG_TRACEPOINTS is not enabled again
>
> Hello Peter,
>
> On Wed, Aug 25, 2021 at 11:41 AM Peter Kjellerstedt
> wrote:
> >
> > Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch was updated
> > with the 2.13.0 update (commit 5dad15af), but unfortunately it no longer
> > did what it was intended to do.
> >
> > Signed-off-by: Peter Kjellerstedt
> > ---
> > ...fail-if-CONFIG_TRACEPOINTS-is-not-en.patch | 42 +++
> > 1 file changed, 25 insertions(+), 17 deletions(-)
> >
> > diff --git a/meta/recipes-kernel/lttng/lttng-modules/Makefile-Do-not-
> fail-if-CONFIG_TRACEPOINTS-is-not-en.patch b/meta/recipes-
> kernel/lttng/lttng-modules/Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-
> not-en.patch
>
> I guess the patch you've refreshed is not a correct one...
>
> There is another patch introduced by Bruce in the commit 18bf7b0
> ("lttng-modules: update devupstream to v2.13-rc "), namely
> 0001-src-Kbuild-change-missing-CONFIG_TRACEPOINTS-to-warn.patch
>
> It make sense to refresh rather that one instead of the Makefile one,
> and have it included in the SRC_URI (see discussion in
> https://lists.openembedded.org/g/openembedded-core/topic/84950303#154888).
>
> --
> Regards,
> Andrey.
Right, I had missed that there were two patches doing the same thing
(though neither actually solved the problem after the update to 2.13.0).
I will send an updated review unifying the patches and adding my solution
to disable building the module when CONFIG_TRACEPOINTS is not enabled.
//Peter
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155295):
https://lists.openembedded.org/g/openembedded-core/message/155295
Mute This Topic: https://lists.openembedded.org/mt/85131925/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] should "${D}${systemd_unitdir}/system" => "${D}${systemd_system_unitdir}"?
> -Original Message-
> From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Robert P. J. Day
> Sent: den 25 augusti 2021 14:42
> To: Ross Burton
> Cc: OE Core mailing list
> Subject: Re: [OE-core] should "${D}${systemd_unitdir}/system" =>
> "${D}${systemd_system_unitdir}"?
>
> On Wed, 18 Aug 2021, Ross Burton wrote:
>
> > No, yes. systemd_system_unitdir is newer so it's used less.
> >
> > Ross
> >
> > On Wed, 18 Aug 2021 at 08:48, Robert P. J. Day
> wrote:
> > >
> > >
> > > i've (so far) run across a small number of OE recipes that use the
> > > identifier "${D}${systemd_unitdir}/system", which appears(?) to be
> > > equivalent to "${D}${systemd_system_unitdir}". is there any potential
> > > functional difference, or should this be standardized?
>
> please help me with basic REs ... i want to run a single perl
> command of the form
>
> $ perl -pi -e 's|...|...|' $(all the relevant files)
>
> to change "${D}${systemd_unitdir}/system" ->
> "${D}${systemd_system_unitdir}"
>
> and then eyeball it afterwards to make sure it's sane, but i can't get
> the proper combination of quotes versus backslashes. i can generate
> the list of appropriate files with:
>
> $ grep -rl '${systemd_unitdir}/system' *
>
> but it's the perl expression that is defeating me. help.
>
> rday
Just use sed, it's what it's there for:
sed -ri -e 's|\$\{systemd_unitdir\}/system|${systemd_system_unitdir}|g' **/*(.)
(the **/*(.) part only works if you use zsh, for bash you will have
to use find and xargs instead).
//Peter
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155294):
https://lists.openembedded.org/g/openembedded-core/message/155294
Mute This Topic: https://lists.openembedded.org/mt/84967618/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] should "${D}${systemd_unitdir}/system" => "${D}${systemd_system_unitdir}"?
On Wed, 18 Aug 2021, Ross Burton wrote:
> No, yes. systemd_system_unitdir is newer so it's used less.
>
> Ross
>
> On Wed, 18 Aug 2021 at 08:48, Robert P. J. Day wrote:
> >
> >
> > i've (so far) run across a small number of OE recipes that use the
> > identifier "${D}${systemd_unitdir}/system", which appears(?) to be
> > equivalent to "${D}${systemd_system_unitdir}". is there any potential
> > functional difference, or should this be standardized?
please help me with basic REs ... i want to run a single perl
command of the form
$ perl -pi -e 's|...|...|' $(all the relevant files)
to change "${D}${systemd_unitdir}/system" -> "${D}${systemd_system_unitdir}"
and then eyeball it afterwards to make sure it's sane, but i can't get
the proper combination of quotes versus backslashes. i can generate
the list of appropriate files with:
$ grep -rl '${systemd_unitdir}/system' *
but it's the perl expression that is defeating me. help.
rday
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155293):
https://lists.openembedded.org/g/openembedded-core/message/155293
Mute This Topic: https://lists.openembedded.org/mt/84967618/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 16/16] harfbuzz: upgrade 2.8.2 -> 2.9.0
Signed-off-by: Alexander Kanavin
---
.../harfbuzz/{harfbuzz_2.8.2.bb => harfbuzz_2.9.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/harfbuzz/{harfbuzz_2.8.2.bb => harfbuzz_2.9.0.bb}
(95%)
diff --git a/meta/recipes-graphics/harfbuzz/harfbuzz_2.8.2.bb
b/meta/recipes-graphics/harfbuzz/harfbuzz_2.9.0.bb
similarity index 95%
rename from meta/recipes-graphics/harfbuzz/harfbuzz_2.8.2.bb
rename to meta/recipes-graphics/harfbuzz/harfbuzz_2.9.0.bb
index 48b0c7724a..bc91a8c03c 100644
--- a/meta/recipes-graphics/harfbuzz/harfbuzz_2.8.2.bb
+++ b/meta/recipes-graphics/harfbuzz/harfbuzz_2.9.0.bb
@@ -12,7 +12,7 @@ UPSTREAM_CHECK_URI =
"https://github.com/${BPN}/${BPN}/releases;
UPSTREAM_CHECK_REGEX = "harfbuzz-(?P\d+(\.\d+)+).tar"
SRC_URI =
"https://github.com/${BPN}/${BPN}/releases/download/${PV}/${BPN}-${PV}.tar.xz;
-SRC_URI[sha256sum] =
"d58461395ce28b9dc03903254374dd70c38c8c28c5046db123c08f7ab9417be7"
+SRC_URI[sha256sum] =
"3e1c2e1d2c65d56364fd16d1c41a06b2a35795496f78dfff635c2b7414b54c5a"
inherit meson pkgconfig lib_package gtk-doc gobject-introspection
--
2.31.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155292):
https://lists.openembedded.org/g/openembedded-core/message/155292
Mute This Topic: https://lists.openembedded.org/mt/85133329/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 15/16] json-glib: upgrade 1.6.2 -> 1.6.4
Upstream has converted from gtk-doc to gi-docgen.
Signed-off-by: Alexander Kanavin
---
.../json-glib/{json-glib_1.6.2.bb => json-glib_1.6.4.bb} | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
rename meta/recipes-gnome/json-glib/{json-glib_1.6.2.bb => json-glib_1.6.4.bb}
(77%)
diff --git a/meta/recipes-gnome/json-glib/json-glib_1.6.2.bb
b/meta/recipes-gnome/json-glib/json-glib_1.6.4.bb
similarity index 77%
rename from meta/recipes-gnome/json-glib/json-glib_1.6.2.bb
rename to meta/recipes-gnome/json-glib/json-glib_1.6.4.bb
index 3f3707805b..072c2406c7 100644
--- a/meta/recipes-gnome/json-glib/json-glib_1.6.2.bb
+++ b/meta/recipes-gnome/json-glib/json-glib_1.6.4.bb
@@ -12,15 +12,14 @@ LIC_FILES_CHKSUM =
"file://COPYING;md5=7fbc338309ac38fefcd64b04bb903e34"
DEPENDS = "glib-2.0"
GNOMEBASEBUILDCLASS = "meson"
-inherit gnomebase lib_package gobject-introspection gtk-doc gettext
ptest-gnome manpages upstream-version-is-even
+inherit gnomebase lib_package gobject-introspection gi-docgen gettext
ptest-gnome manpages upstream-version-is-even
GIR_MESON_ENABLE_FLAG = 'enabled'
GIR_MESON_DISABLE_FLAG = 'disabled'
-GTKDOC_MESON_OPTION = "gtk_doc"
-GTKDOC_MESON_ENABLE_FLAG = 'enabled'
-GTKDOC_MESON_DISABLE_FLAG = 'disabled'
+GIDOCGEN_MESON_ENABLE_FLAG = 'enabled'
+GIDOCGEN_MESON_DISABLE_FLAG = 'disabled'
SRC_URI += " file://run-ptest"
-SRC_URI[archive.sha256sum] =
"a33d66c6d038bda46b910c6c6d59c4e15db014e363dc997a0414c2e07d134f24"
+SRC_URI[archive.sha256sum] =
"b1f6a7930808f77a827f3b397a04bb89d4c0c0b2550885d4a5e4c411dfa13f5f"
PACKAGECONFIG ??= "${@bb.utils.contains('PTEST_ENABLED', '1', 'tests', '', d)}"
PACKAGECONFIG[manpages] = "-Dman=true,-Dman=false,libxslt-native xmlto-native"
--
2.31.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155291):
https://lists.openembedded.org/g/openembedded-core/message/155291
Mute This Topic: https://lists.openembedded.org/mt/85133328/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 14/16] gi-docgen: upgrade 2021.6 -> 2021.7
Signed-off-by: Alexander Kanavin
---
meta/recipes-gnome/gi-docgen/gi-docgen_git.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-gnome/gi-docgen/gi-docgen_git.bb
b/meta/recipes-gnome/gi-docgen/gi-docgen_git.bb
index 8f33bec8da..f319f96b0e 100644
--- a/meta/recipes-gnome/gi-docgen/gi-docgen_git.bb
+++ b/meta/recipes-gnome/gi-docgen/gi-docgen_git.bb
@@ -10,8 +10,8 @@ LIC_FILES_CHKSUM =
"file://gi-docgen.py;beginline=1;endline=5;md5=2dc0f1f0120247
SRC_URI =
"git://gitlab.gnome.org/GNOME/gi-docgen.git;protocol=https;branch=main"
-PV = "2021.6"
-SRCREV = "cb76996ba9ef7a1634ab9bde30c77c3bbb47c8db"
+PV = "2021.7"
+SRCREV = "8401357079fdd2f61bff0e110d7379635b73ead8"
S = "${WORKDIR}/git"
--
2.31.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155290):
https://lists.openembedded.org/g/openembedded-core/message/155290
Mute This Topic: https://lists.openembedded.org/mt/85133326/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 13/16] libnsl2: upgrade 1.3.0 -> 2.0.0
Signed-off-by: Alexander Kanavin --- meta/recipes-extended/libnsl/libnsl2_git.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/recipes-extended/libnsl/libnsl2_git.bb b/meta/recipes-extended/libnsl/libnsl2_git.bb index badb71d977..53be67fe85 100644 --- a/meta/recipes-extended/libnsl/libnsl2_git.bb +++ b/meta/recipes-extended/libnsl/libnsl2_git.bb @@ -10,9 +10,9 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=4fbd65380cdd255951079008b364516c" SECTION = "libs" DEPENDS = "libtirpc" -PV = "1.3.0" +PV = "2.0.0" -SRCREV = "fbad7b36acaa89a54023930af70805649f962999" +SRCREV = "82245c0c58add79a8e34ab0917358217a70e5100" SRC_URI = "git://github.com/thkukuk/libnsl \ " -- 2.31.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#155289): https://lists.openembedded.org/g/openembedded-core/message/155289 Mute This Topic: https://lists.openembedded.org/mt/85133325/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 12/16] vala: upgrade 0.52.4 -> 0.52.5
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/vala/{vala_0.52.4.bb => vala_0.52.5.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/vala/{vala_0.52.4.bb => vala_0.52.5.bb} (50%)
diff --git a/meta/recipes-devtools/vala/vala_0.52.4.bb
b/meta/recipes-devtools/vala/vala_0.52.5.bb
similarity index 50%
rename from meta/recipes-devtools/vala/vala_0.52.4.bb
rename to meta/recipes-devtools/vala/vala_0.52.5.bb
index 8e2869d408..2f78c4a447 100644
--- a/meta/recipes-devtools/vala/vala_0.52.4.bb
+++ b/meta/recipes-devtools/vala/vala_0.52.5.bb
@@ -2,4 +2,4 @@ require ${BPN}.inc
SRC_URI += " file://0001-vapigen.m4-use-PKG_CONFIG_SYSROOT_DIR.patch"
-SRC_URI[sha256sum] =
"ecde520e5160e659ee699f8b1cdc96065edbd44bbd08eb48ef5f2506751fdf31"
+SRC_URI[sha256sum] =
"84a1bb312b3e5dcae4b7b25c45598d375e2cb69233cefb59a15d2350c76bdd91"
--
2.31.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155288):
https://lists.openembedded.org/g/openembedded-core/message/155288
Mute This Topic: https://lists.openembedded.org/mt/85133324/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 09/16] openssh: upgrade 8.6p1 -> 8.7p1
Signed-off-by: Alexander Kanavin
---
.../openssh/{openssh_8.6p1.bb => openssh_8.7p1.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-connectivity/openssh/{openssh_8.6p1.bb =>
openssh_8.7p1.bb} (98%)
diff --git a/meta/recipes-connectivity/openssh/openssh_8.6p1.bb
b/meta/recipes-connectivity/openssh/openssh_8.7p1.bb
similarity index 98%
rename from meta/recipes-connectivity/openssh/openssh_8.6p1.bb
rename to meta/recipes-connectivity/openssh/openssh_8.7p1.bb
index 093214cbfc..c4a08f71d6 100644
--- a/meta/recipes-connectivity/openssh/openssh_8.6p1.bb
+++ b/meta/recipes-connectivity/openssh/openssh_8.7p1.bb
@@ -25,7 +25,7 @@ SRC_URI =
"http://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-${PV}.tar
file://sshd_check_keys \
file://add-test-support-for-busybox.patch \
"
-SRC_URI[sha256sum] =
"c3e6e4da1621762c850d03b47eed1e48dff4cc9608ddeb547202a234df8ed7ae"
+SRC_URI[sha256sum] =
"7ca34b8bb24ae9e50f33792b7091b3841d7e1b440ff57bc9fabddf01e2ed1e24"
# This CVE is specific to OpenSSH with the pam opie which we don't build/use
here
CVE_CHECK_WHITELIST += "CVE-2007-2768"
--
2.31.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155285):
https://lists.openembedded.org/g/openembedded-core/message/155285
Mute This Topic: https://lists.openembedded.org/mt/85133321/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 11/16] python3-mako: upgrade 1.1.4 -> 1.1.5
Signed-off-by: Alexander Kanavin
---
.../python/{python3-mako_1.1.4.bb => python3-mako_1.1.5.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-mako_1.1.4.bb =>
python3-mako_1.1.5.bb} (82%)
diff --git a/meta/recipes-devtools/python/python3-mako_1.1.4.bb
b/meta/recipes-devtools/python/python3-mako_1.1.5.bb
similarity index 82%
rename from meta/recipes-devtools/python/python3-mako_1.1.4.bb
rename to meta/recipes-devtools/python/python3-mako_1.1.5.bb
index 21ce33b808..f8be44a837 100644
--- a/meta/recipes-devtools/python/python3-mako_1.1.4.bb
+++ b/meta/recipes-devtools/python/python3-mako_1.1.5.bb
@@ -8,7 +8,7 @@ PYPI_PACKAGE = "Mako"
inherit pypi setuptools3
-SRC_URI[sha256sum] =
"17831f0b7087c313c0ffae2bcbbd3c1d5ba9eeac9c38f2eb7b50e8c99fe9d5ab"
+SRC_URI[sha256sum] =
"169fa52af22a91900d852e937400e79f535496191c63712e3b9fda5a9bed6fc3"
RDEPENDS:${PN} = "${PYTHON_PN}-html \
${PYTHON_PN}-netclient \
--
2.31.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155287):
https://lists.openembedded.org/g/openembedded-core/message/155287
Mute This Topic: https://lists.openembedded.org/mt/85133323/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 10/16] ell: upgrade 0.42 -> 0.43
Signed-off-by: Alexander Kanavin
---
meta/recipes-core/ell/{ell_0.42.bb => ell_0.43.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-core/ell/{ell_0.42.bb => ell_0.43.bb} (90%)
diff --git a/meta/recipes-core/ell/ell_0.42.bb
b/meta/recipes-core/ell/ell_0.43.bb
similarity index 90%
rename from meta/recipes-core/ell/ell_0.42.bb
rename to meta/recipes-core/ell/ell_0.43.bb
index 7d021c5e3c..3d3ef82668 100644
--- a/meta/recipes-core/ell/ell_0.42.bb
+++ b/meta/recipes-core/ell/ell_0.43.bb
@@ -17,7 +17,7 @@ inherit autotools pkgconfig
SRC_URI =
"https://mirrors.edge.kernel.org/pub/linux/libs/${BPN}/${BPN}-${PV}.tar.xz \
file://0001-pem.c-do-not-use-rawmemchr.patch \
"
-SRC_URI[sha256sum] =
"8b926eebb053f545a03349c0e3d02be586f5aa041f5660b6ced85b55fc531bb7"
+SRC_URI[sha256sum] =
"b6c75895ad64bf78f5b5c464de871048d02f9403be518084e0d64b58f508c9fc"
do_configure:prepend () {
mkdir -p ${S}/build-aux
--
2.31.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155286):
https://lists.openembedded.org/g/openembedded-core/message/155286
Mute This Topic: https://lists.openembedded.org/mt/85133322/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 08/16] bluez5: upgrade 5.60 -> 5.61
Signed-off-by: Alexander Kanavin
---
.../bluez5/{bluez5_5.60.bb => bluez5_5.61.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-connectivity/bluez5/{bluez5_5.60.bb => bluez5_5.61.bb}
(95%)
diff --git a/meta/recipes-connectivity/bluez5/bluez5_5.60.bb
b/meta/recipes-connectivity/bluez5/bluez5_5.61.bb
similarity index 95%
rename from meta/recipes-connectivity/bluez5/bluez5_5.60.bb
rename to meta/recipes-connectivity/bluez5/bluez5_5.61.bb
index defa0c15cd..b2e5dd66a9 100644
--- a/meta/recipes-connectivity/bluez5/bluez5_5.60.bb
+++ b/meta/recipes-connectivity/bluez5/bluez5_5.61.bb
@@ -1,6 +1,6 @@
require bluez5.inc
-SRC_URI[sha256sum] =
"710999580d01ee59ec585e5e7c07fd94eddedc001aa26fe7464c546f9d945304"
+SRC_URI[sha256sum] =
"83afd6c52179554bfeabbcb538fec2eb6be90a8ac3c40871b49d7ad8b49c423b"
# These issues have kernel fixes rather than bluez fixes so exclude here
CVE_CHECK_WHITELIST += "CVE-2020-12352 CVE-2020-24490"
--
2.31.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155284):
https://lists.openembedded.org/g/openembedded-core/message/155284
Mute This Topic: https://lists.openembedded.org/mt/85133320/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 07/16] bind: upgrade 9.16.19 -> 9.16.20
Signed-off-by: Alexander Kanavin
---
.../0001-avoid-start-failure-with-bind-user.patch | 0
.../0001-named-lwresd-V-and-start-log-hide-build-options.patch | 0
.../bind-ensure-searching-for-json-headers-searches-sysr.patch | 0
.../bind/{bind-9.16.19 => bind-9.16.20}/bind9 | 0
.../bind/{bind-9.16.19 => bind-9.16.20}/conf.patch | 0
.../bind/{bind-9.16.19 => bind-9.16.20}/generate-rndc-key.sh| 0
.../init.d-add-support-for-read-only-rootfs.patch | 0
.../make-etc-initd-bind-stop-work.patch | 0
.../bind/{bind-9.16.19 => bind-9.16.20}/named.service | 0
.../bind/{bind_9.16.19.bb => bind_9.16.20.bb} | 2 +-
10 files changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-connectivity/bind/{bind-9.16.19 =>
bind-9.16.20}/0001-avoid-start-failure-with-bind-user.patch (100%)
rename meta/recipes-connectivity/bind/{bind-9.16.19 =>
bind-9.16.20}/0001-named-lwresd-V-and-start-log-hide-build-options.patch (100%)
rename meta/recipes-connectivity/bind/{bind-9.16.19 =>
bind-9.16.20}/bind-ensure-searching-for-json-headers-searches-sysr.patch (100%)
rename meta/recipes-connectivity/bind/{bind-9.16.19 => bind-9.16.20}/bind9
(100%)
rename meta/recipes-connectivity/bind/{bind-9.16.19 =>
bind-9.16.20}/conf.patch (100%)
rename meta/recipes-connectivity/bind/{bind-9.16.19 =>
bind-9.16.20}/generate-rndc-key.sh (100%)
rename meta/recipes-connectivity/bind/{bind-9.16.19 =>
bind-9.16.20}/init.d-add-support-for-read-only-rootfs.patch (100%)
rename meta/recipes-connectivity/bind/{bind-9.16.19 =>
bind-9.16.20}/make-etc-initd-bind-stop-work.patch (100%)
rename meta/recipes-connectivity/bind/{bind-9.16.19 =>
bind-9.16.20}/named.service (100%)
rename meta/recipes-connectivity/bind/{bind_9.16.19.bb => bind_9.16.20.bb}
(98%)
diff --git
a/meta/recipes-connectivity/bind/bind-9.16.19/0001-avoid-start-failure-with-bind-user.patch
b/meta/recipes-connectivity/bind/bind-9.16.20/0001-avoid-start-failure-with-bind-user.patch
similarity index 100%
rename from
meta/recipes-connectivity/bind/bind-9.16.19/0001-avoid-start-failure-with-bind-user.patch
rename to
meta/recipes-connectivity/bind/bind-9.16.20/0001-avoid-start-failure-with-bind-user.patch
diff --git
a/meta/recipes-connectivity/bind/bind-9.16.19/0001-named-lwresd-V-and-start-log-hide-build-options.patch
b/meta/recipes-connectivity/bind/bind-9.16.20/0001-named-lwresd-V-and-start-log-hide-build-options.patch
similarity index 100%
rename from
meta/recipes-connectivity/bind/bind-9.16.19/0001-named-lwresd-V-and-start-log-hide-build-options.patch
rename to
meta/recipes-connectivity/bind/bind-9.16.20/0001-named-lwresd-V-and-start-log-hide-build-options.patch
diff --git
a/meta/recipes-connectivity/bind/bind-9.16.19/bind-ensure-searching-for-json-headers-searches-sysr.patch
b/meta/recipes-connectivity/bind/bind-9.16.20/bind-ensure-searching-for-json-headers-searches-sysr.patch
similarity index 100%
rename from
meta/recipes-connectivity/bind/bind-9.16.19/bind-ensure-searching-for-json-headers-searches-sysr.patch
rename to
meta/recipes-connectivity/bind/bind-9.16.20/bind-ensure-searching-for-json-headers-searches-sysr.patch
diff --git a/meta/recipes-connectivity/bind/bind-9.16.19/bind9
b/meta/recipes-connectivity/bind/bind-9.16.20/bind9
similarity index 100%
rename from meta/recipes-connectivity/bind/bind-9.16.19/bind9
rename to meta/recipes-connectivity/bind/bind-9.16.20/bind9
diff --git a/meta/recipes-connectivity/bind/bind-9.16.19/conf.patch
b/meta/recipes-connectivity/bind/bind-9.16.20/conf.patch
similarity index 100%
rename from meta/recipes-connectivity/bind/bind-9.16.19/conf.patch
rename to meta/recipes-connectivity/bind/bind-9.16.20/conf.patch
diff --git a/meta/recipes-connectivity/bind/bind-9.16.19/generate-rndc-key.sh
b/meta/recipes-connectivity/bind/bind-9.16.20/generate-rndc-key.sh
similarity index 100%
rename from meta/recipes-connectivity/bind/bind-9.16.19/generate-rndc-key.sh
rename to meta/recipes-connectivity/bind/bind-9.16.20/generate-rndc-key.sh
diff --git
a/meta/recipes-connectivity/bind/bind-9.16.19/init.d-add-support-for-read-only-rootfs.patch
b/meta/recipes-connectivity/bind/bind-9.16.20/init.d-add-support-for-read-only-rootfs.patch
similarity index 100%
rename from
meta/recipes-connectivity/bind/bind-9.16.19/init.d-add-support-for-read-only-rootfs.patch
rename to
meta/recipes-connectivity/bind/bind-9.16.20/init.d-add-support-for-read-only-rootfs.patch
diff --git
a/meta/recipes-connectivity/bind/bind-9.16.19/make-etc-initd-bind-stop-work.patch
b/meta/recipes-connectivity/bind/bind-9.16.20/make-etc-initd-bind-stop-work.patch
similarity index 100%
rename from
meta/recipes-connectivity/bind/bind-9.16.19/make-etc-initd-bind-stop-work.patch
rename to
meta/recipes-connectivity/bind/bind-9.16.20/make-etc-initd-bind-stop-work.patch
diff --git a/meta/recipes-connectivity/bind/bind-9.16.19/named.service
[OE-core] [PATCH 04/16] util-linux: upgrade 2.37.1 -> 2.37.2
Signed-off-by: Alexander Kanavin
---
...2.37.1.bb => util-linux-libuuid_2.37.2.bb} | 0
meta/recipes-core/util-linux/util-linux.inc | 3 +-
.../util-linux/CVE-2021-37600.patch | 33 ---
...l-linux_2.37.1.bb => util-linux_2.37.2.bb} | 0
4 files changed, 1 insertion(+), 35 deletions(-)
rename meta/recipes-core/util-linux/{util-linux-libuuid_2.37.1.bb =>
util-linux-libuuid_2.37.2.bb} (100%)
delete mode 100644 meta/recipes-core/util-linux/util-linux/CVE-2021-37600.patch
rename meta/recipes-core/util-linux/{util-linux_2.37.1.bb =>
util-linux_2.37.2.bb} (100%)
diff --git a/meta/recipes-core/util-linux/util-linux-libuuid_2.37.1.bb
b/meta/recipes-core/util-linux/util-linux-libuuid_2.37.2.bb
similarity index 100%
rename from meta/recipes-core/util-linux/util-linux-libuuid_2.37.1.bb
rename to meta/recipes-core/util-linux/util-linux-libuuid_2.37.2.bb
diff --git a/meta/recipes-core/util-linux/util-linux.inc
b/meta/recipes-core/util-linux/util-linux.inc
index 0f17c73e86..1e3cd28801 100644
--- a/meta/recipes-core/util-linux/util-linux.inc
+++ b/meta/recipes-core/util-linux/util-linux.inc
@@ -35,7 +35,6 @@ SRC_URI =
"${KERNELORG_MIRROR}/linux/utils/util-linux/v${MAJOR_VERSION}/util-lin
file://run-ptest \
file://display_testname_for_subtest.patch \
file://avoid_parallel_tests.patch \
- file://CVE-2021-37600.patch \
"
-SRC_URI[sha256sum] =
"8e4bd42053b726cf86eb4d13a73bc1d9225a2c2e1a2e0d2a891f1020f83e6b76"
+SRC_URI[sha256sum] =
"6a0764c1aae7fb607ef8a6dd2c0f6c47d5e5fd27aa08820abaad9ec14e28e9d9"
diff --git a/meta/recipes-core/util-linux/util-linux/CVE-2021-37600.patch
b/meta/recipes-core/util-linux/util-linux/CVE-2021-37600.patch
deleted file mode 100644
index 2b306c435b..00
--- a/meta/recipes-core/util-linux/util-linux/CVE-2021-37600.patch
+++ /dev/null
@@ -1,33 +0,0 @@
-From 1c9143d0c1f979c3daf10e1c37b5b1e916c22a1c Mon Sep 17 00:00:00 2001
-From: Karel Zak
-Date: Tue, 27 Jul 2021 11:58:31 +0200
-Subject: [PATCH] sys-utils/ipcutils: be careful when call calloc() for uint64
- nmembs
-
-Fix: https://github.com/karelzak/util-linux/issues/1395
-Signed-off-by: Karel Zak
-
-CVE: CVE-2021-37600
-Upstream-Status: Backport [1c9143d0c1f979c3daf10e1c37b5b1e916c22a1c]
-
-Signed-off-by: Dragos-Marian Panait
- sys-utils/ipcutils.c | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/sys-utils/ipcutils.c b/sys-utils/ipcutils.c
-index e784c4dcb..18868cfd3 100644
a/sys-utils/ipcutils.c
-+++ b/sys-utils/ipcutils.c
-@@ -218,7 +218,7 @@ static void get_sem_elements(struct sem_data *p)
- {
- size_t i;
-
-- if (!p || !p->sem_nsems || p->sem_perm.id < 0)
-+ if (!p || !p->sem_nsems || p->sem_nsems > SIZE_MAX || p->sem_perm.id <
0)
- return;
-
- p->elements = xcalloc(p->sem_nsems, sizeof(struct sem_elem));
---
-2.25.1
-
diff --git a/meta/recipes-core/util-linux/util-linux_2.37.1.bb
b/meta/recipes-core/util-linux/util-linux_2.37.2.bb
similarity index 100%
rename from meta/recipes-core/util-linux/util-linux_2.37.1.bb
rename to meta/recipes-core/util-linux/util-linux_2.37.2.bb
--
2.31.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155280):
https://lists.openembedded.org/g/openembedded-core/message/155280
Mute This Topic: https://lists.openembedded.org/mt/85133315/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 06/16] git: upgrade 2.32.0 -> 2.33.0
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/git/{git_2.32.0.bb => git_2.33.0.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/git/{git_2.32.0.bb => git_2.33.0.bb} (51%)
diff --git a/meta/recipes-devtools/git/git_2.32.0.bb
b/meta/recipes-devtools/git/git_2.33.0.bb
similarity index 51%
rename from meta/recipes-devtools/git/git_2.32.0.bb
rename to meta/recipes-devtools/git/git_2.33.0.bb
index f45737b096..f8d4dacdbf 100644
--- a/meta/recipes-devtools/git/git_2.32.0.bb
+++ b/meta/recipes-devtools/git/git_2.33.0.bb
@@ -5,5 +5,5 @@ EXTRA_OECONF += "ac_cv_snprintf_returns_bogus=no \
"
EXTRA_OEMAKE += "NO_GETTEXT=1"
-SRC_URI[tarball.sha256sum] =
"6038f06d396ba9dab2eee541c7db6e7f9f847f181ec62f3d8441893f8c469398"
-SRC_URI[manpages.sha256sum] =
"b5533c40ea1688231c0e2df51cc0d1c0272e17fe78a45ba6e60cb8f61fa4a53c"
+SRC_URI[tarball.sha256sum] =
"02d909d0bba560d3a1008bd00dd577621ffb57401b09175fab2bf6da0e9704ae"
+SRC_URI[manpages.sha256sum] =
"ba9cd0f29a3632a3b78f8ed2389f0780aa6e8fcbe258259d7c584920d19ed1f7"
--
2.31.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155282):
https://lists.openembedded.org/g/openembedded-core/message/155282
Mute This Topic: https://lists.openembedded.org/mt/85133317/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 05/16] ccache: upgrade 4.3 -> 4.4
License-Update: formatting
Signed-off-by: Alexander Kanavin
---
.../recipes-devtools/ccache/{ccache_4.3.bb => ccache_4.4.bb} | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/ccache/{ccache_4.3.bb => ccache_4.4.bb} (73%)
diff --git a/meta/recipes-devtools/ccache/ccache_4.3.bb
b/meta/recipes-devtools/ccache/ccache_4.4.bb
similarity index 73%
rename from meta/recipes-devtools/ccache/ccache_4.3.bb
rename to meta/recipes-devtools/ccache/ccache_4.4.bb
index 53a0bcf7ae..203be8c92d 100644
--- a/meta/recipes-devtools/ccache/ccache_4.3.bb
+++ b/meta/recipes-devtools/ccache/ccache_4.4.bb
@@ -7,12 +7,12 @@ HOMEPAGE = "http://ccache.samba.org;
SECTION = "devel"
LICENSE = "GPLv3+"
-LIC_FILES_CHKSUM = "file://LICENSE.adoc;md5=698a26b57e513d678e1e7727bf56395b"
+LIC_FILES_CHKSUM = "file://LICENSE.adoc;md5=73963d63171ecbdf2d25274de67c68c5"
DEPENDS = "zstd"
SRC_URI =
"https://github.com/ccache/ccache/releases/download/v${PV}/${BP}.tar.gz;
-SRC_URI[sha256sum] =
"b9789c42e52c73e99428f311a34def9ffec3462736439afd12dbacc7987c1533"
+SRC_URI[sha256sum] =
"61a993d62216aff35722a8d0e8ffef9b677fc3f6accd8944ffc2a6db98fb3142"
UPSTREAM_CHECK_URI = "https://github.com/ccache/ccache/releases/;
@@ -23,3 +23,4 @@ PATCHTOOL = "patch"
BBCLASSEXTEND = "native nativesdk"
PACKAGECONFIG[docs] =
"-DENABLE_DOCUMENTATION=ON,-DENABLE_DOCUMENTATION=OFF,asciidoc"
+PACKAGECONFIG[redis] =
"-DREDIS_STORAGE_BACKEND=ON,-DREDIS_STORAGE_BACKEND=OFF,hiredis"
--
2.31.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155281):
https://lists.openembedded.org/g/openembedded-core/message/155281
Mute This Topic: https://lists.openembedded.org/mt/85133316/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 03/16] glib-2.0: upgrade 2.68.3 -> 2.68.4
Drop merged 0001-correctly-use-3-parameters-for-close_range.patch
Signed-off-by: Alexander Kanavin
---
...tly-use-3-parameters-for-close_range.patch | 29 ---
.../glib-2.0/glib-2.0/relocate-modules.patch | 2 +-
...{glib-2.0_2.68.3.bb => glib-2.0_2.68.4.bb} | 3 +-
3 files changed, 2 insertions(+), 32 deletions(-)
delete mode 100644
meta/recipes-core/glib-2.0/glib-2.0/0001-correctly-use-3-parameters-for-close_range.patch
rename meta/recipes-core/glib-2.0/{glib-2.0_2.68.3.bb => glib-2.0_2.68.4.bb}
(93%)
diff --git
a/meta/recipes-core/glib-2.0/glib-2.0/0001-correctly-use-3-parameters-for-close_range.patch
b/meta/recipes-core/glib-2.0/glib-2.0/0001-correctly-use-3-parameters-for-close_range.patch
deleted file mode 100644
index 6ff25fc535..00
---
a/meta/recipes-core/glib-2.0/glib-2.0/0001-correctly-use-3-parameters-for-close_range.patch
+++ /dev/null
@@ -1,29 +0,0 @@
-From b71117d89434db83d34bc1b981ca03d4be299576 Mon Sep 17 00:00:00 2001
-From: Khem Raj
-Date: Thu, 8 Jul 2021 17:26:43 -0700
-Subject: [PATCH] correctly use 3 parameters for close_range
-
-libc implementation has 3 parameter e.g.
-https://www.freebsd.org/cgi/man.cgi?query=close_range=2=html
-
-Upstream-Status: Submitted
[https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2180]
-Signed-off-by: Khem Raj
- glib/gspawn.c | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/glib/gspawn.c b/glib/gspawn.c
-index 899647c2f..3073a10a4 100644
a/glib/gspawn.c
-+++ b/glib/gspawn.c
-@@ -1520,7 +1520,7 @@ safe_closefrom (int lowfd)
-*
-* Handle ENOSYS in case it’s supported in libc but not the kernel; if so,
-* fall back to safe_fdwalk(). */
-- if (close_range (lowfd, G_MAXUINT) != 0 && errno == ENOSYS)
-+ if (close_range (lowfd, G_MAXUINT, 0) != 0 && errno == ENOSYS)
- #endif /* HAVE_CLOSE_RANGE */
- (void) safe_fdwalk (close_func, GINT_TO_POINTER (lowfd));
- #endif
---
-2.32.0
diff --git a/meta/recipes-core/glib-2.0/glib-2.0/relocate-modules.patch
b/meta/recipes-core/glib-2.0/glib-2.0/relocate-modules.patch
index f34f30bb3c..846c8d62b6 100644
--- a/meta/recipes-core/glib-2.0/glib-2.0/relocate-modules.patch
+++ b/meta/recipes-core/glib-2.0/glib-2.0/relocate-modules.patch
@@ -1,4 +1,4 @@
-From e56cdb8c343dd6a6ed3b10bd54e353d633ad6158 Mon Sep 17 00:00:00 2001
+From dac2bdeea38388e069412aa27eff8f1eff0440e5 Mon Sep 17 00:00:00 2001
From: Ross Burton
Date: Fri, 11 Mar 2016 15:35:55 +
Subject: [PATCH] glib-2.0: relocate the GIO module directory for native builds
diff --git a/meta/recipes-core/glib-2.0/glib-2.0_2.68.3.bb
b/meta/recipes-core/glib-2.0/glib-2.0_2.68.4.bb
similarity index 93%
rename from meta/recipes-core/glib-2.0/glib-2.0_2.68.3.bb
rename to meta/recipes-core/glib-2.0/glib-2.0_2.68.4.bb
index c71dc81202..cd789de3c0 100644
--- a/meta/recipes-core/glib-2.0/glib-2.0_2.68.3.bb
+++ b/meta/recipes-core/glib-2.0/glib-2.0_2.68.4.bb
@@ -18,11 +18,10 @@ SRC_URI =
"${GNOME_MIRROR}/glib/${SHRT_VER}/glib-${PV}.tar.xz \
file://0001-gio-tests-resources.c-comment-out-a-build-host-only-.patch \
file://0001-gio-tests-codegen.py-bump-timeout-to-100-seconds.patch \
file://time-test.patch \
- file://0001-correctly-use-3-parameters-for-close_range.patch \
"
SRC_URI:append:class-native = " file://relocate-modules.patch"
-SRC_URI[sha256sum] =
"e7e1a3c20c026109c45c9ec4a31d8dcebc22e86c69486993e565817d64be3138"
+SRC_URI[sha256sum] =
"62fd061d08a75492617e625a73e2c05e259f831acbb8e1f8b9c81f23f7993a3b"
# Find any meson cross files in FILESPATH that are relevant for the current
# build (using siteinfo) and add them to EXTRA_OEMESON.
--
2.31.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155279):
https://lists.openembedded.org/g/openembedded-core/message/155279
Mute This Topic: https://lists.openembedded.org/mt/85133312/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 01/16] binutils: drop target flex/bison from build dependencies
This lengthens dependency chains unnecessarily;
also -native versions are already included in DEPENDS via binutils.inc:
DEPENDS = "flex-native bison-native zlib-native gnu-config-native
autoconf-native"
I have also checked that nothing in binutils needs anything from target
sysroots of flex/bison:
https://lists.openembedded.org/g/openembedded-core/message/155131
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/binutils/binutils_2.37.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/binutils/binutils_2.37.bb
b/meta/recipes-devtools/binutils/binutils_2.37.bb
index ff9377049b..7430bf1342 100644
--- a/meta/recipes-devtools/binutils/binutils_2.37.bb
+++ b/meta/recipes-devtools/binutils/binutils_2.37.bb
@@ -1,7 +1,7 @@
require binutils.inc
require binutils-${PV}.inc
-DEPENDS += "flex bison zlib"
+DEPENDS += "zlib"
EXTRA_OECONF += "--with-sysroot=/ \
--enable-install-libbfd \
--
2.31.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155277):
https://lists.openembedded.org/g/openembedded-core/message/155277
Mute This Topic: https://lists.openembedded.org/mt/85133309/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 02/16] gnu-efi: update 3.0.13 -> 3.0.14
Removed non-existent header from licensing.
Signed-off-by: Alexander Kanavin
---
.../gnu-efi/{gnu-efi_3.0.13.bb => gnu-efi_3.0.14.bb} | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
rename meta/recipes-bsp/gnu-efi/{gnu-efi_3.0.13.bb => gnu-efi_3.0.14.bb} (93%)
diff --git a/meta/recipes-bsp/gnu-efi/gnu-efi_3.0.13.bb
b/meta/recipes-bsp/gnu-efi/gnu-efi_3.0.14.bb
similarity index 93%
rename from meta/recipes-bsp/gnu-efi/gnu-efi_3.0.13.bb
rename to meta/recipes-bsp/gnu-efi/gnu-efi_3.0.14.bb
index ef3061c067..04dadc39d4 100644
--- a/meta/recipes-bsp/gnu-efi/gnu-efi_3.0.13.bb
+++ b/meta/recipes-bsp/gnu-efi/gnu-efi_3.0.14.bb
@@ -6,7 +6,6 @@ LICENSE = "GPLv2+ | BSD-2-Clause"
LIC_FILES_CHKSUM =
"file://gnuefi/crt0-efi-arm.S;beginline=4;endline=16;md5=e582764a4776e60c95bf9ab617343d36
\
file://gnuefi/crt0-efi-aarch64.S;beginline=4;endline=16;md5=e582764a4776e60c95bf9ab617343d36
\
file://inc/efishellintf.h;beginline=13;endline=20;md5=202766b79d708eff3cc70fce15fb80c7
\
-
file://inc/efishellparm.h;beginline=4;endline=11;md5=468b1231b05bbc84bae3a0d5774e3bb5
\
file://lib/arm/math.c;beginline=2;endline=15;md5=8ed772501da77b2b3345aa6df8744c9e
\
file://lib/arm/initplat.c;beginline=2;endline=15;md5=8ed772501da77b2b3345aa6df8744c9e
\
file://lib/aarch64/math.c;beginline=2;endline=15;md5=8ed772501da77b2b3345aa6df8744c9e
\
@@ -19,7 +18,7 @@ SRC_URI = "${SOURCEFORGE_MIRROR}/${BPN}/files/${BP}.tar.bz2 \
file://gnu-efi-3.0.9-fix-clang-build.patch \
"
-SRC_URI[sha256sum] =
"2fccf715279c46ee69c4859186af8150d07a13f4d19876e5459cd65be82d3b7d"
+SRC_URI[sha256sum] =
"b73b643a0d5697d1f396d7431448e886dd805668789578e3e1a28277c9528435"
COMPATIBLE_HOST = "(x86_64.*|i.86.*|aarch64.*|arm.*)-linux"
COMPATIBLE_HOST:armv4 = 'null'
--
2.31.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155278):
https://lists.openembedded.org/g/openembedded-core/message/155278
Mute This Topic: https://lists.openembedded.org/mt/85133310/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH] lttng-modules: Make it build when CONFIG_TRACEPOINTS is not enabled again
Hello Peter,
On Wed, Aug 25, 2021 at 11:41 AM Peter Kjellerstedt
wrote:
>
> Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch was updated
> with the 2.13.0 update (commit 5dad15af), but unfortunately it no longer
> did what it was intended to do.
>
> Signed-off-by: Peter Kjellerstedt
> ---
> ...fail-if-CONFIG_TRACEPOINTS-is-not-en.patch | 42 +++
> 1 file changed, 25 insertions(+), 17 deletions(-)
>
> diff --git
> a/meta/recipes-kernel/lttng/lttng-modules/Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch
>
> b/meta/recipes-kernel/lttng/lttng-modules/Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch
I guess the patch you've refreshed is not a correct one...
There is another patch introduced by Bruce in the commit 18bf7b0
("lttng-modules: update devupstream to v2.13-rc "), namely
0001-src-Kbuild-change-missing-CONFIG_TRACEPOINTS-to-warn.patch
It make sense to refresh rather that one instead of the Makefile one,
and have it included in the SRC_URI (see discussion in
https://lists.openembedded.org/g/openembedded-core/topic/84950303#154888).
--
Regards,
Andrey.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155276):
https://lists.openembedded.org/g/openembedded-core/message/155276
Mute This Topic: https://lists.openembedded.org/mt/85131925/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH] lttng-modules: Make it build when CONFIG_TRACEPOINTS is not enabled again
Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch was updated with the 2.13.0 update (commit 5dad15af), but unfortunately it no longer did what it was intended to do. Signed-off-by: Peter Kjellerstedt --- ...fail-if-CONFIG_TRACEPOINTS-is-not-en.patch | 42 +++ 1 file changed, 25 insertions(+), 17 deletions(-) diff --git a/meta/recipes-kernel/lttng/lttng-modules/Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch b/meta/recipes-kernel/lttng/lttng-modules/Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch index a852834344..4fb55270f5 100644 --- a/meta/recipes-kernel/lttng/lttng-modules/Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch +++ b/meta/recipes-kernel/lttng/lttng-modules/Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch @@ -1,8 +1,7 @@ -From 1b0e574d680101105a6c1e8931c78824f5a97a42 Mon Sep 17 00:00:00 2001 +From 885926e62f32a29b185dcfe738e61a2358a6b615 Mon Sep 17 00:00:00 2001 From: Otavio Salvador Date: Mon, 5 Sep 2016 17:08:56 + Subject: [PATCH] Makefile: Do not fail if CONFIG_TRACEPOINTS is not enabled -Organization: O.S. Systems Software LTDA. The lttng-modules are being pulled by the tools-profile image feature, however, not every kernel has the CONFIG_TRACEPOINTS feature enabled. @@ -16,22 +15,31 @@ Signed-off-by: Otavio Salvador [bva: modified for lttng-modules 2.13+ context] Signed-off-by: Bruce Ashfield --- - Makefile | 9 + - 1 file changed, 5 insertions(+), 4 deletions(-) + src/Kbuild | 7 ++- + 1 file changed, 6 insertions(+), 1 deletion(-) -Index: lttng-modules-2.13.0/Makefile -=== lttng-modules-2.13.0.orig/Makefile -+++ lttng-modules-2.13.0/Makefile -@@ -7,6 +7,11 @@ +diff --git a/src/Kbuild b/src/Kbuild +index 7137874..04eb5c9 100644 +--- a/src/Kbuild b/src/Kbuild +@@ -2,10 +2,13 @@ - obj-$(CONFIG_LTTNG) += src/ + ifdef CONFIG_LOCALVERSION # Check if dot-config is included. + ifeq ($(CONFIG_TRACEPOINTS),) +-$(error The option CONFIG_TRACEPOINTS needs to be enabled in your kernel configuration) ++$(warning The option CONFIG_TRACEPOINTS needs to be enabled in your kernel configuration) ++DISABLE_MODULE = y + endif # CONFIG_TRACEPOINTS + endif # ifdef CONFIG_LOCALVERSION -+ ifdef CONFIG_LOCALVERSION # Check if dot-config is included. -+ifneq ($(CONFIG_TRACEPOINTS),) -+ $(warning The option CONFIG_TRACEPOINTS needs to be enabled in your kernel configuration) -+endif # CONFIG_TRACEPOINTS -+ endif # ifdef CONFIG_LOCALVERSION - else # KERNELRELEASE ++ifneq ($(DISABLE_MODULE),y) ++ + TOP_LTTNG_MODULES_DIR := $(shell dirname $(lastword $(MAKEFILE_LIST)))/.. - # This part of the Makefile is used when the 'make' command is runned in the + lttng_check_linux_version = $(shell pwd)/include/linux/version.h +@@ -150,3 +153,5 @@ lttng-statedump-objs := lttng-statedump-impl.o + obj-$(CONFIG_LTTNG) += probes/ + obj-$(CONFIG_LTTNG) += lib/ + obj-$(CONFIG_LTTNG) += tests/ ++ ++endif # DISABLE_MODULE -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#155275): https://lists.openembedded.org/g/openembedded-core/message/155275 Mute This Topic: https://lists.openembedded.org/mt/85131925/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH] libcgroup: remove static pam library
From: Kai Kang
libpam disables static build by default, so remove static pam library of
libcgroup. Otherwise it complains QA issue:
| ERROR: libcgroup-2.0-r0 do_package: QA Issue: libcgroup:
Files/directories were installed but not shipped in any package:
| /lib/security/pam_cgroup.a
Signed-off-by: Kai Kang
---
meta/recipes-core/libcgroup/libcgroup_2.0.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/libcgroup/libcgroup_2.0.bb
b/meta/recipes-core/libcgroup/libcgroup_2.0.bb
index bc0a75d46c..f48b8ece9b 100644
--- a/meta/recipes-core/libcgroup/libcgroup_2.0.bb
+++ b/meta/recipes-core/libcgroup/libcgroup_2.0.bb
@@ -31,4 +31,5 @@ FILES:${PN}-dev += "${base_libdir}/security/*.la"
do_install:append() {
# Until we ship the test suite, this library isn't useful
rm -f ${D}${libdir}/libcgroupfortesting.*
+ rm -f ${D}${base_libdir}/security/pam_cgroup.a
}
--
2.17.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155274):
https://lists.openembedded.org/g/openembedded-core/message/155274
Mute This Topic: https://lists.openembedded.org/mt/85130950/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] oFono Version 1.31 ofonod crash
Hi Sergei,
Thanks for the advice, the latest ofono in oe-core master is 1.32, but
I am in branch Hardknott, so I copied ofono 1.32 from master to my
layer running Hardknott branch, but I could not build ofono 1.32 in
Hardknott:
ERROR: ParseError at
/build/oe-cor/../meta-solar/recipes-connectivity/ofono/ofono_1.32.bb:22:
unparsed line: 'SYSTEMD_SERVICE:${PN} = "ofono.service"'
I used ofono 1.30 and connman 1.37 in Zeus, both worked fine , but
both connman 1.39 and ofono 1.31 failed to work properly in oe-core
Hardknott branch, to narrow down if it is ofono issue or Yocto OE
build or other library issue, I was able to build ofono 1.30 for
Hardknott, I can confirm that ofono 1.30 failed just like the 1.31
stuck at the statement add_serial_device.
ofonod[2806]: ../ofono-1.30/plugins/udevng.c:add_serial_device()
Device is missing required OFONO_DRIVER property
ofonod[2806]: ../ofono-1.30/plugins/udevng.c:add_serial_device()
Device is missing required OFONO_DRIVER property
ofonod[2806]: ../ofono-1.30/plugins/udevng.c:add_serial_device()
Device is missing required OFONO_DRIVER property
If I run ofono 1.30 built from Zeus build, the ofonod would pass
missing OFONO_DRIVER property and kept it work:
..
ofonod[3712]: ../ofono-1.30/plugins/udevng.c:add_serial_device()
Device is missing required OFONO_DRIVER property
ofonod[3712]: ../ofono-1.30/plugins/udevng.c:create_modem()
/sys/devices/soc0/soc/210.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1
ofonod[3712]: ../ofono-1.30/plugins/udevng.c:create_modem() driver=ubloxqmi
ofonod[3712]: ../ofono-1.30/src/modem.c:ofono_modem_create() name:
(null), type: ubloxqmi
ofonod[3712]: ../ofono-1.30/plugins/udevng.c:setup_ubloxqmi()
/sys/devices/soc0/soc/210.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1
.
So I don't think it is an oFono issue, but rather an OE Yocto build or
library issue, can anyone run oFono in oe-core Hardknott branch?
Thank you.
Kind regards,
- jupiter
On 8/22/21, Sergei Golubtsov wrote:
> Hi jupiter,
>
> Please try to update ofono to the latest release. Seems to be a library
> incompatibility issue or something like that.
>
> Yours sincerely,
> Sergei Golubtsov.
>
>
> On Sat, Aug 21, 2021 at 4:09 AM Jupiter wrote:
>
>> Hi,
>>
>> I build ofono v1.31 from git://git.yoctoproject.org/poky branch
>> hardknott,
>>
>> $ cat meta/recipes-connectivity/ofono/ofono_1.31.bb
>>
>> SUMMARY = "open source telephony"
>> DESCRIPTION = "oFono is a stack for mobile telephony devices on Linux.
>> oFono supports speaking to telephony devices through specific drivers,
>> or with generic AT commands."
>> HOMEPAGE = "http://www.ofono.org;
>> BUGTRACKER = "https://01.org/jira/browse/OF;
>> LICENSE = "GPLv2"
>> LIC_FILES_CHKSUM = "file://COPYING;md5=eb723b61539feef013de476e68b5c50a \
>>
>>
>> file://src/ofono.h;beginline=1;endline=20;md5=3ce17d5978ef3445def265b98899c2ee"
>> DEPENDS = "dbus glib-2.0 udev mobile-broadband-provider-info ell"
>>
>> SRC_URI = "\
>> ${KERNELORG_MIRROR}/linux/network/${BPN}/${BP}.tar.xz \
>> file://ofono \
>> file://0001-mbim-add-an-optional-TEMP_FAILURE_RETRY-macro-copy.patch
>> \
>> "
>> SRC_URI[md5sum] = "1c26340e3c6ed132cc812595081bb3dc"
>> SRC_URI[sha256sum] =
>> "a15c5d28096c10eb30e47a68b6dc2e7c4a5a99d7f4cfedf0b69624f33d859e9b"
>>
>> inherit autotools pkgconfig update-rc.d systemd
>> gobject-introspection-data
>>
>> INITSCRIPT_NAME = "ofono"
>> INITSCRIPT_PARAMS = "defaults 22"
>> SYSTEMD_SERVICE_${PN} = "ofono.service"
>>
>> PACKAGECONFIG ??= "\
>> ${@bb.utils.filter('DISTRO_FEATURES', 'systemd', d)} \
>> ${@bb.utils.contains('DISTRO_FEATURES', 'bluetooth', 'bluez', '', d)}
>> \
>> "
>> PACKAGECONFIG[systemd] =
>> "--with-systemdunitdir=${systemd_unitdir}/system/,--with-systemdunitdir="
>> PACKAGECONFIG[bluez] = "--enable-bluetooth, --disable-bluetooth, bluez5"
>>
>> EXTRA_OECONF += "--enable-test --enable-external-ell"
>>
>> do_install_append() {
>> install -d ${D}${sysconfdir}/init.d/
>> install -m 0755 ${WORKDIR}/ofono ${D}${sysconfdir}/init.d/ofono
>> }
>>
>> PACKAGES =+ "${PN}-tests"
>>
>> FILES_${PN} += "${systemd_unitdir}"
>> FILES_${PN}-tests = "${libdir}/${BPN}/test"
>>
>> RDEPENDS_${PN} += "dbus"
>> RDEPENDS_${PN}-tests = "\
>> python3-core \
>> python3-dbus \
>> ${@bb.utils.contains('GI_DATA_ENABLED', 'True',
>> 'python3-pygobject', '', d)} \
>> "
>>
>> RRECOMMENDS_${PN} += "kernel-module-tun mobile-broadband-provider-info"
>>
>> The build was fine, but running the v1.31 ofono.service crashed at
>> udevng.c missing OFONO_DRIVER property, the ofono.service was repeated
>> to be restarted every 6 seconds:
>>
>> .
>>
>> ofonod[9005]: ../ofono-1.31/plugins/udevng.c:add_serial_device()
>> Device is missing required OFONO_DRIVER property
>> ofonod[9005]: ../ofono-1.31/plugins/udevng.c:add_serial_device()
>> Device is missing required OFONO_DRIVER property
>> ..
>>
>> I am not quite sure if it is ofono 1.31 problem or oe-core
>> ofono_1.31.bb problem, could anyone have
