Re: [OE-core] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.20.rc2)
Hi All, QA for yocto- 3.1.20.rc2 is completed. This is the full report for this release: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults === Summary No high milestone defects. No new issue found. Thanks, Jing Hui > -Original Message- > From: qa-build-notificat...@lists.yoctoproject.org notificat...@lists.yoctoproject.org> On Behalf Of Pokybuild User > Sent: Tuesday, 11 October, 2022 1:53 AM > To: yo...@lists.yoctoproject.org > Cc: qa-build-notificat...@lists.yoctoproject.org > Subject: [qa-build-notification] QA notification for completed autobuilder > build (yocto-3.1.20.rc2) > > > A build flagged for QA (yocto-3.1.20.rc2) was completed on the autobuilder > and is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-3.1.20.rc2 > > > Build hash information: > > bitbake: 048d682b031644fb9f0d41a489bacb873aa27bd7 > meta-agl: da4775d226b2a231e27e8c8995c20fdd3c73f08a > meta-arm: 08c44df351ae1913f41de8388981b03e21235f09 > meta-aws: 052c9a5f8532ed96487df37bae2f598c129d7d01 > meta-gplv2: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac > meta-intel: ed616c50ea329ba6fe68642cfc8bf8c6b8b61beb > meta-mingw: 524de686205b5d6736661d4532f5f98fee8589b7 > meta-openembedded: 6792ebdd966aa0fb662989529193a0940fbfee00 > meta-virtualization: beea119eb529b4a11f266004aee8b548427aea39 > oecore: dbad46a0079843b380cf3dda6008b12ab9526688 > poky: 7f9b7f912e13451a4cd03b10a8090a5def68dc39 > > > > This is an automated message from the Yocto Project Autobuilder > Git: git://git.yoctoproject.org/yocto-autobuilder2 > Email: richard.pur...@linuxfoundation.org > > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171723): https://lists.openembedded.org/g/openembedded-core/message/171723 Mute This Topic: https://lists.openembedded.org/mt/94251909/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] gcc: Allow -Wno-error=poison-system-directories to take effect
On Thu, Oct 13, 2022 at 2:21 PM Peter Kjellerstedt wrote: > > > -Original Message- > > From: Khem Raj > > Sent: den 13 oktober 2022 17:41 > > To: Peter Kjellerstedt > > Cc: Ross Burton ; Patches and discussions about the > > oe-core layer > > Subject: Re: [OE-core] [PATCH] gcc: Allow -Wno-error=poison-system- > > directories to take effect > > > > On Thu, Oct 13, 2022 at 7:38 AM Peter Kjellerstedt > > wrote: > > > > > > > -Original Message- > > > > From: Ross Burton > > > > Sent: den 13 oktober 2022 16:05 > > > > To: Peter Kjellerstedt > > > > Cc: Patches and discussions about the oe-core layer > > > c...@lists.openembedded.org> > > > > Subject: Re: [OE-core] [PATCH] gcc: Allow -Wno-error=poison-system- > > > > directories to take effect > > > > > > > > Whilst this is a good fix, I’m horrified to ask why you need it… > > > > > > We have a recipe for skia. Somewhere in that mess of a build > > > system it uses (gn), something adds -I/usr/include/freetype2, > > > which results in an error with -Werror=poison-system-directories > > > enabled (as it should). Now, to work around that problem, the > > > recipe currently adds -I=/usr/include/freetype2, which means we > > > know that the correct path is used. However, since the original > > > -I/usr/include/freetype2 is still in the list of options, the > > > error still triggers. > > > > > > Now, to fix the problem properly, skias's build files should be > > > patched, but that is not my job. What I am working on is to get > > > our recipes to build with Langdale. This means I can cut some > > > corners and, e.g., disable errors and then hand off to the > > > responsible team to fix the underlying problem at a time that > > > suits them. Thus in this case I wanted to add > > > -Wno-error=poison-system-directories for skia, which I then, to > > > my surprise, noticed had no effect... > > > > from gcc recipe point of view, this fix is fine. however your use of > > this seems to be a workaround that perhaps is better fixed in skia > > Oh, I'm well aware of that. As I said, my job at this stage is to get > everything building with Langdale. And to achieve that, it is perfectly > fine for me to, e.g., disable compiler errors. Once the platform > builds, the respective code owners have the responsibility to actually > correct their code to not generate the errors in the first place. I hope you will inform the responsible and ask them to fix the problem. > > > because = syntax for sysroot works with gcc but may not work with > > clang e.g. so you are being lucky here. > > We don't use clang so that is not a problem for us. > > > > //Peter > > > > > > > Ross > > //Peter > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171722): https://lists.openembedded.org/g/openembedded-core/message/171722 Mute This Topic: https://lists.openembedded.org/mt/94303421/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] gcc: Allow -Wno-error=poison-system-directories to take effect
> -Original Message- > From: Khem Raj > Sent: den 13 oktober 2022 17:41 > To: Peter Kjellerstedt > Cc: Ross Burton ; Patches and discussions about the > oe-core layer > Subject: Re: [OE-core] [PATCH] gcc: Allow -Wno-error=poison-system- > directories to take effect > > On Thu, Oct 13, 2022 at 7:38 AM Peter Kjellerstedt > wrote: > > > > > -Original Message- > > > From: Ross Burton > > > Sent: den 13 oktober 2022 16:05 > > > To: Peter Kjellerstedt > > > Cc: Patches and discussions about the oe-core layer > > c...@lists.openembedded.org> > > > Subject: Re: [OE-core] [PATCH] gcc: Allow -Wno-error=poison-system- > > > directories to take effect > > > > > > Whilst this is a good fix, I’m horrified to ask why you need it… > > > > We have a recipe for skia. Somewhere in that mess of a build > > system it uses (gn), something adds -I/usr/include/freetype2, > > which results in an error with -Werror=poison-system-directories > > enabled (as it should). Now, to work around that problem, the > > recipe currently adds -I=/usr/include/freetype2, which means we > > know that the correct path is used. However, since the original > > -I/usr/include/freetype2 is still in the list of options, the > > error still triggers. > > > > Now, to fix the problem properly, skias's build files should be > > patched, but that is not my job. What I am working on is to get > > our recipes to build with Langdale. This means I can cut some > > corners and, e.g., disable errors and then hand off to the > > responsible team to fix the underlying problem at a time that > > suits them. Thus in this case I wanted to add > > -Wno-error=poison-system-directories for skia, which I then, to > > my surprise, noticed had no effect... > > from gcc recipe point of view, this fix is fine. however your use of > this seems to be a workaround that perhaps is better fixed in skia Oh, I'm well aware of that. As I said, my job at this stage is to get everything building with Langdale. And to achieve that, it is perfectly fine for me to, e.g., disable compiler errors. Once the platform builds, the respective code owners have the responsibility to actually correct their code to not generate the errors in the first place. > because = syntax for sysroot works with gcc but may not work with > clang e.g. so you are being lucky here. We don't use clang so that is not a problem for us. > > //Peter > > > > > Ross //Peter -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171721): https://lists.openembedded.org/g/openembedded-core/message/171721 Mute This Topic: https://lists.openembedded.org/mt/94303421/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 1/2] oeqa/selftest/archiver: Add multiconfig test for shared recipes
Test that the shared recipes in original mode with diff enabled works in
multiconfig,
otherwise it will not build when using the same TMP dir.
The test can be run with:
oe-selftest -r
archiver.Archiver.test_archiver_multiconfig_shared_unpack_and_patch
| oe-selftest - INFO - test_archiver_multiconfig_shared_unpack_and_patch
(archiver.Archiver)
| oe-selftest - INFO - ... ok
| oe-selftest - INFO -
--
| oe-selftest - INFO - Ran 1 test in 199.710s
| oe-selftest - INFO - OK
| oe-selftest - INFO - RESULTS:
| oe-selftest - INFO - RESULTS -
archiver.Archiver.test_archiver_multiconfig_shared_unpack_and_patch: PASSED
(192.24s)
| oe-selftest - INFO - SUMMARY:
| oe-selftest - INFO - oe-selftest () - Ran 1 test in 199.711s
| oe-selftest - INFO - oe-selftest - OK - All required tests passed
(successes=1, skipped=0, failures=0, errors=0)
Signed-off-by: Jose Quaresma
---
meta/lib/oeqa/selftest/cases/archiver.py | 29
1 file changed, 29 insertions(+)
diff --git a/meta/lib/oeqa/selftest/cases/archiver.py
b/meta/lib/oeqa/selftest/cases/archiver.py
index ffdea832be..1d4985dacf 100644
--- a/meta/lib/oeqa/selftest/cases/archiver.py
+++ b/meta/lib/oeqa/selftest/cases/archiver.py
@@ -6,6 +6,7 @@
import os
import glob
+import re
from oeqa.utils.commands import bitbake, get_bb_vars
from oeqa.selftest.case import OESelftestTestCase
@@ -119,7 +120,35 @@ class Archiver(OESelftestTestCase):
excluded_present = len(glob.glob(src_path_target + '/%s-*/*' %
target_recipes[1]))
self.assertFalse(excluded_present, 'Recipe %s was not excluded.' %
target_recipes[1])
+def test_archiver_multiconfig_shared_unpack_and_patch(self):
+"""
+Test that shared recipes in original mode with diff enabled works in
multiconfig,
+otherwise it will not build when using the same TMP dir.
+"""
+
+features = 'BBMULTICONFIG = "mc1 mc2"\n'
+features += 'INHERIT += "archiver"\n'
+features += 'ARCHIVER_MODE[src] = "original"\n'
+features += 'ARCHIVER_MODE[diff] = "1"\n'
+self.write_config(features)
+
+# We can use any machine in multiconfig as long as they are different
+self.write_config('MACHINE = "qemuarm"\n', 'mc1')
+self.write_config('MACHINE = "qemux86"\n', 'mc2')
+
+task = 'do_unpack_and_patch'
+# Use gcc-source as it is a shared recipe (appends the pv to the pn)
+pn = 'gcc-source-%s' % get_bb_vars(['PV'], 'gcc')['PV']
+
+# Generate the tasks signatures
+bitbake('mc:mc1:%s mc:mc2:%s --runonly=%s --dump-signatures=none' %
(pn, pn, task))
+# Check the tasks signatures
+# To be machine agnostic the tasks needs to generate the same
signature for each machine
+locked_sigs = open("%s/locked-sigs.inc" % self.builddir).read()
+task_sigs = re.findall(r"%s:%s:.*" % (pn, task), locked_sigs)
+uniq_sigs = set(task_sigs)
+self.assertFalse(len(uniq_sigs) - 1, 'The task "%s" of the recipe "%s"
has diferent signatures for each machine in multiconfig' % (task, pn))
def test_archiver_srpm_mode(self):
"""
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171719):
https://lists.openembedded.org/g/openembedded-core/message/171719
Mute This Topic: https://lists.openembedded.org/mt/94312275/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 2/2] archiver: avoid using machine variable as it breaks multiconfig
STAGING_KERNEL_DIR uses the MACHINE name so it breaks the multiconfig
and in this cases it will run the shared recipes twice, one for each
machine.
STAGING_KERNEL_DIR it's been introduced in commit 5487dee2e1
Signed-off-by: Jose Quaresma
---
meta/classes/archiver.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/archiver.bbclass b/meta/classes/archiver.bbclass
index 0710c1ec5e..4049694d85 100644
--- a/meta/classes/archiver.bbclass
+++ b/meta/classes/archiver.bbclass
@@ -465,7 +465,7 @@ def is_work_shared(d):
pn = d.getVar('PN')
return pn.startswith('gcc-source') or \
bb.data.inherits_class('kernel', d) or \
-(bb.data.inherits_class('kernelsrc', d) and d.getVar('S') ==
d.getVar('STAGING_KERNEL_DIR'))
+(bb.data.inherits_class('kernelsrc', d) and
d.expand("${TMPDIR}/work-shared") in d.getVar('S'))
# Run do_unpack and do_patch
python do_unpack_and_patch() {
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171720):
https://lists.openembedded.org/g/openembedded-core/message/171720
Mute This Topic: https://lists.openembedded.org/mt/94312276/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] wic: honor the SOURCE_DATE_EPOCH in case of updated fstab
From: Sergei Zhmylev
In case user requested to build a binary repeatable package,
it's required to honor the SOURCE_DATE_EPOCH environment
variable. So forcefully set mtime inside all the routines
which modify fstab in case it is updated.
Signed-off-by: Sergei Zhmylev
---
scripts/lib/wic/partition.py | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/scripts/lib/wic/partition.py b/scripts/lib/wic/partition.py
index e50871b8d7..cac1bab4dd 100644
--- a/scripts/lib/wic/partition.py
+++ b/scripts/lib/wic/partition.py
@@ -291,6 +291,9 @@ class Partition():
if self.updated_fstab_path and self.has_fstab and not
self.no_fstab_update:
debugfs_script_path = os.path.join(cr_workdir, "debugfs_script")
with open(debugfs_script_path, "w") as f:
+if os.getenv('SOURCE_DATE_EPOCH'):
+fstab_time = int(os.getenv('SOURCE_DATE_EPOCH'))
+f.write("set_current_time %s\n" % (fstab_time))
f.write("cd etc\n")
f.write("rm fstab\n")
f.write("write %s fstab\n" % (self.updated_fstab_path))
@@ -353,7 +356,7 @@ class Partition():
exec_native_cmd(mcopy_cmd, native_sysroot)
if self.updated_fstab_path and self.has_fstab and not
self.no_fstab_update:
-mcopy_cmd = "mcopy -i %s %s ::/etc/fstab" % (rootfs,
self.updated_fstab_path)
+mcopy_cmd = "mcopy -m -i %s %s ::/etc/fstab" % (rootfs,
self.updated_fstab_path)
exec_native_cmd(mcopy_cmd, native_sysroot)
chmod_cmd = "chmod 644 %s" % rootfs
--
2.37.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171718):
https://lists.openembedded.org/g/openembedded-core/message/171718
Mute This Topic: https://lists.openembedded.org/mt/94308156/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][dunfell 9/9] qemu: Avoid accidental librdmacm linkage
From: Richard Purdie
Avoid accidentally linking to the rdma library from the host by
adding a PACKAGECONFIG for the option. This was found on new
Fedora 36 autobuilder workers.
Signed-off-by: Richard Purdie
(cherry picked from commit 2a0f3cb225e4d5471155abbcd05d09bd6bf1620f)
Signed-off-by: Steve Sakoman
---
meta/recipes-devtools/qemu/qemu.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-devtools/qemu/qemu.inc
b/meta/recipes-devtools/qemu/qemu.inc
index d85db8f800..28caefef07 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -277,6 +277,7 @@ PACKAGECONFIG[libnfs] =
"--enable-libnfs,--disable-libnfs,libnfs"
PACKAGECONFIG[brlapi] = "--enable-brlapi,--disable-brlapi"
PACKAGECONFIG[vde] = "--enable-vde,--disable-vde"
PACKAGECONFIG[rbd] = "--enable-rbd,--disable-rbd"
+PACKAGECONFIG[rdma] = "--enable-rdma,--disable-rdma"
INSANE_SKIP_${PN} = "arch"
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171717):
https://lists.openembedded.org/g/openembedded-core/message/171717
Mute This Topic: https://lists.openembedded.org/mt/94308075/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][dunfell 8/9] qemu: Add PACKAGECONFIG for rbd
Avoid accidentally linking to the rbd library from the host by
adding a PACKAGECONFIG for the option.
Signed-off-by: Steve Sakoman
---
meta/recipes-devtools/qemu/qemu.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-devtools/qemu/qemu.inc
b/meta/recipes-devtools/qemu/qemu.inc
index cdd615997f..d85db8f800 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -276,6 +276,7 @@ PACKAGECONFIG[capstone] =
"--enable-capstone,--disable-capstone"
PACKAGECONFIG[libnfs] = "--enable-libnfs,--disable-libnfs,libnfs"
PACKAGECONFIG[brlapi] = "--enable-brlapi,--disable-brlapi"
PACKAGECONFIG[vde] = "--enable-vde,--disable-vde"
+PACKAGECONFIG[rbd] = "--enable-rbd,--disable-rbd"
INSANE_SKIP_${PN} = "arch"
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171716):
https://lists.openembedded.org/g/openembedded-core/message/171716
Mute This Topic: https://lists.openembedded.org/mt/94308074/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][dunfell 7/9] qemu: Avoid accidental libvdeplug linkage
Avoid accidentally linking to the vde library from the host by
adding a PACKAGECONFIG for the option.
Signed-off-by: Steve Sakoman
Signed-off-by: Richard Purdie
(cherry picked from commit 8839e9540528b0b46c4fb4f95e508f038bcef8b9)
Signed-off-by: Steve Sakoman
---
meta/recipes-devtools/qemu/qemu.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-devtools/qemu/qemu.inc
b/meta/recipes-devtools/qemu/qemu.inc
index 3c0b34d851..cdd615997f 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -275,6 +275,7 @@ PACKAGECONFIG[capstone] =
"--enable-capstone,--disable-capstone"
# libnfs is currently provided by meta-kodi
PACKAGECONFIG[libnfs] = "--enable-libnfs,--disable-libnfs,libnfs"
PACKAGECONFIG[brlapi] = "--enable-brlapi,--disable-brlapi"
+PACKAGECONFIG[vde] = "--enable-vde,--disable-vde"
INSANE_SKIP_${PN} = "arch"
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171715):
https://lists.openembedded.org/g/openembedded-core/message/171715
Mute This Topic: https://lists.openembedded.org/mt/94308072/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][dunfell 6/9] externalsrc: git submodule--helper list unsupported
From: John Edward Broadbent
Git has removed support for "git submodule--helper list".
https://github.com/git/git/commit/31955475d1c283120d5d84247eb3fd55d9f5fdd9
This change provides an alternate method for gathering the submodules
information.
Tested:
Build recipes with and without submodules
Signed-off-by: Carson Labrado
Signed-off-by: John Edward Broadbent
Signed-off-by: Richard Purdie
(cherry picked from commit 6d9364e5f3535954f65cbbc694ee7933ac1d664f)
Signed-off-by: Steve Sakoman
---
meta/classes/externalsrc.bbclass | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/meta/classes/externalsrc.bbclass b/meta/classes/externalsrc.bbclass
index 0e0a3ae89c..291fcf5653 100644
--- a/meta/classes/externalsrc.bbclass
+++ b/meta/classes/externalsrc.bbclass
@@ -225,15 +225,16 @@ def srctree_hash_files(d, srcdir=None):
env['GIT_INDEX_FILE'] = tmp_index.name
subprocess.check_output(['git', 'add', '-A', '.'], cwd=s_dir,
env=env)
git_sha1 = subprocess.check_output(['git', 'write-tree'],
cwd=s_dir, env=env).decode("utf-8")
-submodule_helper = subprocess.check_output(['git',
'submodule--helper', 'list'], cwd=s_dir, env=env).decode("utf-8")
-for line in submodule_helper.splitlines():
-module_dir = os.path.join(s_dir, line.rsplit(maxsplit=1)[1])
-if os.path.isdir(module_dir):
-proc = subprocess.Popen(['git', 'add', '-A', '.'],
cwd=module_dir, env=env, stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL)
-proc.communicate()
-proc = subprocess.Popen(['git', 'write-tree'],
cwd=module_dir, env=env, stdout=subprocess.PIPE, stderr=subprocess.DEVNULL)
-stdout, _ = proc.communicate()
-git_sha1 += stdout.decode("utf-8")
+if os.path.exists(".gitmodules"):
+submodule_helper = subprocess.check_output(["git", "config",
"--file", ".gitmodules", "--get-regexp", "path"], cwd=s_dir,
env=env).decode("utf-8")
+for line in submodule_helper.splitlines():
+module_dir = os.path.join(s_dir,
line.rsplit(maxsplit=1)[1])
+if os.path.isdir(module_dir):
+proc = subprocess.Popen(['git', 'add', '-A', '.'],
cwd=module_dir, env=env, stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL)
+proc.communicate()
+proc = subprocess.Popen(['git', 'write-tree'],
cwd=module_dir, env=env, stdout=subprocess.PIPE, stderr=subprocess.DEVNULL)
+stdout, _ = proc.communicate()
+git_sha1 += stdout.decode("utf-8")
sha1 = hashlib.sha1(git_sha1.encode("utf-8")).hexdigest()
with open(oe_hash_file, 'w') as fobj:
fobj.write(sha1)
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171714):
https://lists.openembedded.org/g/openembedded-core/message/171714
Mute This Topic: https://lists.openembedded.org/mt/94308071/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][dunfell 5/9] uninative: Upgrade to 3.7 to work with glibc 2.36
From: Michael Halstead
Update uninative to work with the new glibc 2.36 version
Signed-off-by: Michael Halstead
Signed-off-by: Richard Purdie
(cherry picked from commit 410226b053e14e32add1f9b4b811f84a1c445a7c)
Signed-off-by: Steve Sakoman
---
meta/conf/distro/include/yocto-uninative.inc | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/meta/conf/distro/include/yocto-uninative.inc
b/meta/conf/distro/include/yocto-uninative.inc
index 411fe45a24..7012db441b 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -6,10 +6,10 @@
# to the distro running on the build machine.
#
-UNINATIVE_MAXGLIBCVERSION = "2.35"
-UNINATIVE_VERSION = "3.6"
+UNINATIVE_MAXGLIBCVERSION = "2.36"
+UNINATIVE_VERSION = "3.7"
UNINATIVE_URL ?=
"http://downloads.yoctoproject.org/releases/uninative/${UNINATIVE_VERSION}/;
-UNINATIVE_CHECKSUM[aarch64] ?=
"d64831cf2792c8e470c2e42230660e1a8e5de56a579cdd59978791f663c2f3ed"
-UNINATIVE_CHECKSUM[i686] ?=
"2f0ee9b66b1bb2c85e2b592fb3c9c7f5d77399fa638d74961330cdb8de34ca3b"
-UNINATIVE_CHECKSUM[x86_64] ?=
"9bfc4c970495b3716b2f9e52c4df9f968c02463a9a95000f6657fbc3fde1f098"
+UNINATIVE_CHECKSUM[aarch64] ?=
"6a29bcae4b5b716d2d520e18800b33943b65f8a835eac1ff8793fc5ee65b4be6"
+UNINATIVE_CHECKSUM[i686] ?=
"3f6d52e64996570c716108d49f8108baccf499a283bbefae438c7266b7a93305"
+UNINATIVE_CHECKSUM[x86_64] ?=
"b110bf2e10fe420f5ca2f3ec55f048ee5f0a54c7e34856a3594e51eb2aea0570"
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171713):
https://lists.openembedded.org/g/openembedded-core/message/171713
Mute This Topic: https://lists.openembedded.org/mt/94308070/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][dunfell 4/9] selftest: skip virgl test on ubuntu 22.04
This test will fail any time the host has libdrm > 2.4.107
Signed-off-by: Steve Sakoman
---
meta/lib/oeqa/selftest/cases/runtime_test.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/lib/oeqa/selftest/cases/runtime_test.py
b/meta/lib/oeqa/selftest/cases/runtime_test.py
index df11984713..399727de49 100644
--- a/meta/lib/oeqa/selftest/cases/runtime_test.py
+++ b/meta/lib/oeqa/selftest/cases/runtime_test.py
@@ -191,6 +191,8 @@ class TestImage(OESelftestTestCase):
self.skipTest('virgl isn\'t working with Fedora 36')
if distro and distro == 'opensuseleap-15.0':
self.skipTest('virgl isn\'t working with Opensuse 15.0')
+if distro and distro == 'ubuntu-22.04':
+self.skipTest('virgl isn\'t working with Ubuntu 22.04')
qemu_packageconfig = get_bb_var('PACKAGECONFIG', 'qemu-system-native')
sdl_packageconfig = get_bb_var('PACKAGECONFIG', 'libsdl2-native')
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171712):
https://lists.openembedded.org/g/openembedded-core/message/171712
Mute This Topic: https://lists.openembedded.org/mt/94308068/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][dunfell 3/9] python3: upgrade 3.8.13 -> 3.8.14
From: Tim Orling
Security and bug fixes.
* Drop CVE-2021-28861.patch as it was merged in 3.8.14 release.
Fixes:
* CVE-2020-10735
https://nvd.nist.gov/vuln/detail/CVE-2020-10735
* CVE-2021-28861
https://nvd.nist.gov/vuln/detail/CVE-2021-28861
* CVE-2018-25032
https://nvd.nist.gov/vuln/detail/CVE-2018-25032
Python 3.8.14
Release Date: Sept. 6, 2022
This is a security release of Python 3.8
Note: The release you're looking at is Python 3.8.14, a security bugfix
release for the legacy 3.8 series. Python 3.10 is now the latest
feature release series of Python 3.
Security content in this release
CVE-2020-10735: converting between int and str in bases other than
2 (binary), 4, 8 (octal), 16 (hexadecimal), or 32 such as base
10 (decimal) now raises a ValueError if the number of digits in string
form is above a limit to avoid potential denial of service attacks due
to the algorithmic complexity.
gh-87389: http.server: Fix an open redirection vulnerability in the HTTP
server when an URI path starts with //.
gh-93065: Fix contextvars HAMT implementation to handle iteration over
deep trees to avoid a potential crash of the interpreter.
gh-90355: Fix ensurepip environment isolation for the subprocess running
pip.
gh-80254: Raise ProgrammingError instead of segfaulting on recursive usage
of cursors in sqlite3 converters.
Signed-off-by: Tim Orling
Signed-off-by: Steve Sakoman
---
.../python/python3/CVE-2021-28861.patch | 135 --
.../{python3_3.8.13.bb => python3_3.8.14.bb} | 5 +-
2 files changed, 2 insertions(+), 138 deletions(-)
delete mode 100644 meta/recipes-devtools/python/python3/CVE-2021-28861.patch
rename meta/recipes-devtools/python/{python3_3.8.13.bb => python3_3.8.14.bb}
(98%)
diff --git a/meta/recipes-devtools/python/python3/CVE-2021-28861.patch
b/meta/recipes-devtools/python/python3/CVE-2021-28861.patch
deleted file mode 100644
index dc97c6b4eb..00
--- a/meta/recipes-devtools/python/python3/CVE-2021-28861.patch
+++ /dev/null
@@ -1,135 +0,0 @@
-From 4dc2cae3abd75f386374d0635d00443b897d0672 Mon Sep 17 00:00:00 2001
-From: "Miss Islington (bot)"
- <31488909+miss-isling...@users.noreply.github.com>
-Date: Wed, 22 Jun 2022 01:42:52 -0700
-Subject: [PATCH] gh-87389: Fix an open redirection vulnerability in
- http.server. (GH-93879) (GH-94094)
-
-Fix an open redirection vulnerability in the `http.server` module when
-an URI path starts with `//` that could produce a 301 Location header
-with a misleading target. Vulnerability discovered, and logic fix
-proposed, by Hamza Avvan (@hamzaavvan).
-
-Test and comments authored by Gregory P. Smith [Google].
-(cherry picked from commit 4abab6b603dd38bec1168e9a37c40a48ec89508e)
-
-Co-authored-by: Gregory P. Smith
-
-Signed-off-by: Riyaz Khan
-
-CVE: CVE-2021-28861
-
-Upstream-Status: Backport
[https://github.com/python/cpython/commit/4dc2cae3abd75f386374d0635d00443b897d0672]
-
- Lib/http/server.py| 7 +++
- Lib/test/test_httpservers.py | 53 ++-
- ...2-06-15-20-09-23.gh-issue-87389.QVaC3f.rst | 3 ++
- 3 files changed, 61 insertions(+), 2 deletions(-)
- create mode 100644
Misc/NEWS.d/next/Security/2022-06-15-20-09-23.gh-issue-87389.QVaC3f.rst
-
-diff --git a/Lib/http/server.py b/Lib/http/server.py
-index 38f7accad7a3..39de35458c38 100644
a/Lib/http/server.py
-+++ b/Lib/http/server.py
-@@ -332,6 +332,13 @@ def parse_request(self):
- return False
- self.command, self.path = command, path
-
-+# gh-87389: The purpose of replacing '//' with '/' is to protect
-+# against open redirect attacks possibly triggered if the path starts
-+# with '//' because http clients treat //path as an absolute URI
-+# without scheme (similar to http://path) rather than a path.
-+if self.path.startswith('//'):
-+self.path = '/' + self.path.lstrip('/') # Reduce to a single /
-+
- # Examine the headers and look for a Connection directive.
- try:
- self.headers = http.client.parse_headers(self.rfile,
-diff --git a/Lib/test/test_httpservers.py b/Lib/test/test_httpservers.py
-index 87d4924a34b3..fb026188f0b4 100644
a/Lib/test/test_httpservers.py
-+++ b/Lib/test/test_httpservers.py
-@@ -330,7 +330,7 @@ class request_handler(NoLogRequestHandler,
SimpleHTTPRequestHandler):
- pass
-
- def setUp(self):
--BaseTestCase.setUp(self)
-+super().setUp()
- self.cwd = os.getcwd()
- basetempdir = tempfile.gettempdir()
- os.chdir(basetempdir)
-@@ -358,7 +358,7 @@ def tearDown(self):
- except:
- pass
- finally:
--BaseTestCase.tearDown(self)
-+super().tearDown()
-
- def check_status_and_reason(self, response, status, data=None):
- def close_conn():
-@@ -414,6 +414,55 @@ def test_undecodable_filename(self):
-
[OE-core][dunfell 1/9] dhcp: Fix CVE-2022-2928 & CVE-2022-2929
From: Hitendra Prajapati
Source: https://downloads.isc.org/isc/dhcp
MR: 122797, 122812
Type: Security Fix
Disposition: Backport from https://downloads.isc.org/isc/dhcp/4.4.3-P1/patches/
ChangeID: 31490133cae8fc9c77073f9023955d3ff39c0b6e
Description:
Fixed CVEs:
1. CVE-2022-2928
2. CVE-2022-2929
Signed-off-by: Hitendra Prajapati
Signed-off-by: Steve Sakoman
---
.../dhcp/dhcp/CVE-2022-2928.patch | 120 ++
.../dhcp/dhcp/CVE-2022-2929.patch | 40 ++
meta/recipes-connectivity/dhcp/dhcp_4.4.2.bb | 2 +
3 files changed, 162 insertions(+)
create mode 100644 meta/recipes-connectivity/dhcp/dhcp/CVE-2022-2928.patch
create mode 100644 meta/recipes-connectivity/dhcp/dhcp/CVE-2022-2929.patch
diff --git a/meta/recipes-connectivity/dhcp/dhcp/CVE-2022-2928.patch
b/meta/recipes-connectivity/dhcp/dhcp/CVE-2022-2928.patch
new file mode 100644
index 00..11f162cbda
--- /dev/null
+++ b/meta/recipes-connectivity/dhcp/dhcp/CVE-2022-2928.patch
@@ -0,0 +1,120 @@
+From 8a5d739eea10ee6e193f053b1662142d5657cbc6 Mon Sep 17 00:00:00 2001
+From: Hitendra Prajapati
+Date: Thu, 6 Oct 2022 09:39:18 +0530
+Subject: [PATCH] CVE-2022-2928
+
+Upstream-Status: Backport
[https://downloads.isc.org/isc/dhcp/4.4.3-P1/patches/]
+CVE: CVE-2022-2928
+Signed-off-by: Hitendra Prajapati
+---
+ common/options.c | 7 +
+ common/tests/option_unittest.c | 54 ++
+ 2 files changed, 61 insertions(+)
+
+diff --git a/common/options.c b/common/options.c
+index a7ed84c..4e53bb4 100644
+--- a/common/options.c
b/common/options.c
+@@ -4452,6 +4452,8 @@ add_option(struct option_state *options,
+ if (!option_cache_allocate(, MDL)) {
+ log_error("No memory for option cache adding %s (option %d).",
+ option->name, option_num);
++ /* Get rid of reference created during hash lookup. */
++ option_dereference(, MDL);
+ return 0;
+ }
+
+@@ -4463,6 +4465,8 @@ add_option(struct option_state *options,
+MDL)) {
+ log_error("No memory for constant data adding %s (option %d).",
+ option->name, option_num);
++ /* Get rid of reference created during hash lookup. */
++ option_dereference(, MDL);
+ option_cache_dereference(, MDL);
+ return 0;
+ }
+@@ -4471,6 +4475,9 @@ add_option(struct option_state *options,
+ save_option(_universe, options, oc);
+ option_cache_dereference(, MDL);
+
++ /* Get rid of reference created during hash lookup. */
++ option_dereference(, MDL);
++
+ return 1;
+ }
+
+diff --git a/common/tests/option_unittest.c b/common/tests/option_unittest.c
+index cd52cfb..690704d 100644
+--- a/common/tests/option_unittest.c
b/common/tests/option_unittest.c
+@@ -130,6 +130,59 @@ ATF_TC_BODY(pretty_print_option, tc)
+ }
+
+
++ATF_TC(add_option_ref_cnt);
++
++ATF_TC_HEAD(add_option_ref_cnt, tc)
++{
++atf_tc_set_md_var(tc, "descr",
++"Verify add_option() does not leak option ref counts.");
++}
++
++ATF_TC_BODY(add_option_ref_cnt, tc)
++{
++struct option_state *options = NULL;
++struct option *option = NULL;
++unsigned int cid_code = DHO_DHCP_CLIENT_IDENTIFIER;
++char *cid_str = "1234";
++int refcnt_before = 0;
++
++// Look up the option we're going to add.
++initialize_common_option_spaces();
++if (!option_code_hash_lookup(, dhcp_universe.code_hash,
++ _code, 0, MDL)) {
++atf_tc_fail("cannot find option definition?");
++}
++
++// Get the option's reference count before we call add_options.
++refcnt_before = option->refcnt;
++
++// Allocate a option_state to which to add an option.
++if (!option_state_allocate(, MDL)) {
++ atf_tc_fail("cannot allocat options state");
++}
++
++// Call add_option() to add the option to the option state.
++if (!add_option(options, cid_code, cid_str, strlen(cid_str))) {
++ atf_tc_fail("add_option returned 0");
++}
++
++// Verify that calling add_option() only adds 1 to the option ref count.
++if (option->refcnt != (refcnt_before + 1)) {
++atf_tc_fail("after add_option(), count is wrong, before %d, after:
%d",
++refcnt_before, option->refcnt);
++}
++
++// Derefrence the option_state, this should reduce the ref count to
++// it's starting value.
++option_state_dereference(, MDL);
++
++// Verify that dereferencing option_state restores option ref count.
++if (option->refcnt != refcnt_before) {
++atf_tc_fail("after state deref, count is wrong, before %d, after: %d",
++refcnt_before, option->refcnt);
++}
++}
++
+ /* This macro defines main() method that will call specified
+test cases. tp and simple_test_case names can be whatever you want
[OE-core][dunfell 2/9] qemu: CVE-2021-3750 hcd-ehci: DMA reentrancy issue leads to use-after-free
From: Hitendra Prajapati
Source: https://git.qemu.org/?p=qemu.git
MR: 117886
Type: Security Fix
Disposition: Backport from
https://git.qemu.org/?p=qemu.git;a=commit;h=b9d383ab797f54ae5fa8746117770709921dc529
&&
https://git.qemu.org/?p=qemu.git;a=commit;h=3ab6fdc91b72e156da22848f0003ff4225690ced
&&
https://git.qemu.org/?p=qemu.git;a=commit;h=58e74682baf4e1ad26b064d8c02e5bc99c75c5d9
ChangeID: 3af901d20ad8ff389468eda2c53b4943e3a77bb8
Description:
CVE-2021-3750 QEMU: hcd-ehci: DMA reentrancy issue leads to
use-after-free.
Signed-off-by: Hitendra Prajapati
Signed-off-by: Steve Sakoman
---
meta/recipes-devtools/qemu/qemu.inc | 1 +
.../qemu/qemu/CVE-2021-3750.patch | 180 ++
2 files changed, 181 insertions(+)
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2021-3750.patch
diff --git a/meta/recipes-devtools/qemu/qemu.inc
b/meta/recipes-devtools/qemu/qemu.inc
index 368be9979a..3c0b34d851 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -111,6 +111,7 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \
file://CVE-2021-4207.patch \
file://CVE-2022-0216-1.patch \
file://CVE-2022-0216-2.patch \
+ file://CVE-2021-3750.patch \
"
UPSTREAM_CHECK_REGEX = "qemu-(?P\d+(\.\d+)+)\.tar"
diff --git a/meta/recipes-devtools/qemu/qemu/CVE-2021-3750.patch
b/meta/recipes-devtools/qemu/qemu/CVE-2021-3750.patch
new file mode 100644
index 00..43630e71fb
--- /dev/null
+++ b/meta/recipes-devtools/qemu/qemu/CVE-2021-3750.patch
@@ -0,0 +1,180 @@
+From 1938fbc7ec197e2612ab2ce36dd69bff19208aa5 Mon Sep 17 00:00:00 2001
+From: Hitendra Prajapati
+Date: Mon, 10 Oct 2022 17:44:41 +0530
+Subject: [PATCH] CVE-2021-3750
+
+Upstream-Status: Backport
[https://git.qemu.org/?p=qemu.git;a=commit;h=b9d383ab797f54ae5fa8746117770709921dc529
&&
https://git.qemu.org/?p=qemu.git;a=commit;h=3ab6fdc91b72e156da22848f0003ff4225690ced
&&
https://git.qemu.org/?p=qemu.git;a=commit;h=58e74682baf4e1ad26b064d8c02e5bc99c75c5d9]
+CVE: CVE-2021-3750
+Signed-off-by: Hitendra Prajapati
+---
+ exec.c | 55 +++---
+ hw/intc/arm_gicv3_redist.c | 4 +--
+ include/exec/memattrs.h| 9 +++
+ 3 files changed, 56 insertions(+), 12 deletions(-)
+
+diff --git a/exec.c b/exec.c
+index 1360051a..10581d8d 100644
+--- a/exec.c
b/exec.c
+@@ -39,6 +39,7 @@
+ #include "qemu/config-file.h"
+ #include "qemu/error-report.h"
+ #include "qemu/qemu-print.h"
++#include "qemu/log.h"
+ #if defined(CONFIG_USER_ONLY)
+ #include "qemu.h"
+ #else /* !CONFIG_USER_ONLY */
+@@ -3118,6 +3119,33 @@ static bool prepare_mmio_access(MemoryRegion *mr)
+ return release_lock;
+ }
+
++/**
+++ * flatview_access_allowed
+++ * @mr: #MemoryRegion to be accessed
+++ * @attrs: memory transaction attributes
+++ * @addr: address within that memory region
+++ * @len: the number of bytes to access
+++ *
+++ * Check if a memory transaction is allowed.
+++ *
+++ * Returns: true if transaction is allowed, false if denied.
+++ */
++static bool flatview_access_allowed(MemoryRegion *mr, MemTxAttrs attrs,
++hwaddr addr, hwaddr len)
++{
++if (likely(!attrs.memory)) {
++return true;
++}
++if (memory_region_is_ram(mr)) {
++return true;
++}
++qemu_log_mask(LOG_GUEST_ERROR,
++ "Invalid access to non-RAM device at "
++ "addr 0x%" HWADDR_PRIX ", size %" HWADDR_PRIu ", "
++ "region '%s'\n", addr, len, memory_region_name(mr));
++return false;
++}
++
+ /* Called within RCU critical section. */
+ static MemTxResult flatview_write_continue(FlatView *fv, hwaddr addr,
+MemTxAttrs attrs,
+@@ -3131,7 +3159,10 @@ static MemTxResult flatview_write_continue(FlatView
*fv, hwaddr addr,
+ bool release_lock = false;
+
+ for (;;) {
+-if (!memory_access_is_direct(mr, true)) {
++ if (!flatview_access_allowed(mr, attrs, addr1, l)) {
++result |= MEMTX_ACCESS_ERROR;
++/* Keep going. */
++} else if (!memory_access_is_direct(mr, true)) {
+ release_lock |= prepare_mmio_access(mr);
+ l = memory_access_size(mr, l, addr1);
+ /* XXX: could force current_cpu to NULL to avoid
+@@ -3173,14 +3204,14 @@ static MemTxResult flatview_write(FlatView *fv, hwaddr
addr, MemTxAttrs attrs,
+ hwaddr l;
+ hwaddr addr1;
+ MemoryRegion *mr;
+-MemTxResult result = MEMTX_OK;
+
+ l = len;
+ mr = flatview_translate(fv, addr, , , true, attrs);
+-result = flatview_write_continue(fv, addr, attrs, buf, len,
+- addr1, l, mr);
+-
+-return result;
++if (!flatview_access_allowed(mr, attrs, addr, len)) {
++return MEMTX_ACCESS_ERROR;
++}
++return flatview_write_continue(fv, addr, attrs,
[OE-core][dunfell 0/9] Patch review
Please review this set of patches for dunfell and have comments back by
end of day Monday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/4330
The following changes since commit dbad46a0079843b380cf3dda6008b12ab9526688:
build-appliance-image: Update to dunfell head revision (2022-10-06 23:23:20
+0100)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/dunfell-nut
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-nut
Hitendra Prajapati (2):
dhcp: Fix CVE-2022-2928 & CVE-2022-2929
qemu: CVE-2021-3750 hcd-ehci: DMA reentrancy issue leads to
use-after-free
John Edward Broadbent (1):
externalsrc: git submodule--helper list unsupported
Michael Halstead (1):
uninative: Upgrade to 3.7 to work with glibc 2.36
Richard Purdie (1):
qemu: Avoid accidental librdmacm linkage
Steve Sakoman (3):
selftest: skip virgl test on ubuntu 22.04
qemu: Avoid accidental libvdeplug linkage
qemu: Add PACKAGECONFIG for rbd
Tim Orling (1):
python3: upgrade 3.8.13 -> 3.8.14
meta/classes/externalsrc.bbclass | 19 +-
meta/conf/distro/include/yocto-uninative.inc | 10 +-
meta/lib/oeqa/selftest/cases/runtime_test.py | 2 +
.../dhcp/dhcp/CVE-2022-2928.patch | 120
.../dhcp/dhcp/CVE-2022-2929.patch | 40
meta/recipes-connectivity/dhcp/dhcp_4.4.2.bb | 2 +
.../python/python3/CVE-2021-28861.patch | 135 -
.../{python3_3.8.13.bb => python3_3.8.14.bb} | 5 +-
meta/recipes-devtools/qemu/qemu.inc | 4 +
.../qemu/qemu/CVE-2021-3750.patch | 180 ++
10 files changed, 365 insertions(+), 152 deletions(-)
create mode 100644 meta/recipes-connectivity/dhcp/dhcp/CVE-2022-2928.patch
create mode 100644 meta/recipes-connectivity/dhcp/dhcp/CVE-2022-2929.patch
delete mode 100644 meta/recipes-devtools/python/python3/CVE-2021-28861.patch
rename meta/recipes-devtools/python/{python3_3.8.13.bb => python3_3.8.14.bb}
(98%)
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2021-3750.patch
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171708):
https://lists.openembedded.org/g/openembedded-core/message/171708
Mute This Topic: https://lists.openembedded.org/mt/94308059/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] gcc: Allow -Wno-error=poison-system-directories to take effect
On Thu, Oct 13, 2022 at 7:38 AM Peter Kjellerstedt
wrote:
>
> > -Original Message-
> > From: Ross Burton
> > Sent: den 13 oktober 2022 16:05
> > To: Peter Kjellerstedt
> > Cc: Patches and discussions about the oe-core layer > c...@lists.openembedded.org>
> > Subject: Re: [OE-core] [PATCH] gcc: Allow -Wno-error=poison-system-
> > directories to take effect
> >
> > Whilst this is a good fix, I’m horrified to ask why you need it…
>
> We have a recipe for skia. Somewhere in that mess of a build
> system it uses (gn), something adds -I/usr/include/freetype2,
> which results in an error with -Werror=poison-system-directories
> enabled (as it should). Now, to work around that problem, the
> recipe currently adds -I=/usr/include/freetype2, which means we
> know that the correct path is used. However, since the original
> -I/usr/include/freetype2 is still in the list of options, the
> error still triggers.
>
> Now, to fix the problem properly, skias's build files should be
> patched, but that is not my job. What I am working on is to get
> our recipes to build with Langdale. This means I can cut some
> corners and, e.g., disable errors and then hand off to the
> responsible team to fix the underlying problem at a time that
> suits them. Thus in this case I wanted to add
> -Wno-error=poison-system-directories for skia, which I then, to
> my surprise, noticed had no effect...
from gcc recipe point of view, this fix is fine. however your use of
this seems to be a workaround that perhaps is better fixed in skia
because = syntax for sysroot works with gcc but may not work with
clang e.g. so you are being lucky here.
>
> //Peter
>
> >
> > Ross
> >
> > > On 13 Oct 2022, at 14:29, Peter Kjellerstedt via lists.openembedded.org
> > wrote:
> > >
> > > The change in commit e903b29f (gcc-cross: pass
> > > -Werror=poison-system-directories to compiler stages) made it impossible
> > > to disable the error using -Wno-error=poison-system-directories.
> > >
> > > Signed-off-by: Peter Kjellerstedt
> > > ---
> > > .../0002-gcc-poison-system-directories.patch | 36 +--
> > > 1 file changed, 18 insertions(+), 18 deletions(-)
> > >
> > > diff --git a/meta/recipes-devtools/gcc/gcc/0002-gcc-poison-system-
> > directories.patch b/meta/recipes-devtools/gcc/gcc/0002-gcc-poison-system-
> > directories.patch
> > > index bfec4477c1..5aa635b3d4 100644
> > > --- a/meta/recipes-devtools/gcc/gcc/0002-gcc-poison-system-
> > directories.patch
> > > +++ b/meta/recipes-devtools/gcc/gcc/0002-gcc-poison-system-
> > directories.patch
> > > @@ -1,4 +1,4 @@
> > > -From e1dbdcd0ea667bab4b551294354e04c6fe288ab6 Mon Sep 17 00:00:00 2001
> > > +From 99f1e61b2957226254a116fde7fd73bf07034012 Mon Sep 17 00:00:00 2001
> > > From: Khem Raj
> > > Date: Mon, 8 Mar 2021 16:04:20 -0800
> > > Subject: [PATCH] gcc: poison-system-directories
> > > @@ -20,12 +20,12 @@ Signed-off-by: Khem Raj
> > > gcc/configure | 19 +++
> > > gcc/configure.ac| 16
> > > gcc/doc/invoke.texi | 9 +
> > > - gcc/gcc.cc | 9 +++--
> > > + gcc/gcc.cc | 15 ---
> > > gcc/incpath.cc | 21 +
> > > - 7 files changed, 86 insertions(+), 2 deletions(-)
> > > + 7 files changed, 91 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/gcc/common.opt b/gcc/common.opt
> > > -index 8a0dafc522d..0357868e22c 100644
> > > +index 8a0dafc52..0357868e2 100644
> > > --- a/gcc/common.opt
> > > +++ b/gcc/common.opt
> > > @@ -710,6 +710,10 @@ Wreturn-local-addr
> > > @@ -40,7 +40,7 @@ index 8a0dafc522d..0357868e22c 100644
> > > Common Var(warn_shadow) Warning
> > > Warn when one variable shadows another. Same as -Wshadow=global.
> > > diff --git a/gcc/config.in b/gcc/config.in
> > > -index 64c27c9cfac..a693cb8a886 100644
> > > +index 64c27c9cf..a693cb8a8 100644
> > > --- a/gcc/config.in
> > > +++ b/gcc/config.in
> > > @@ -230,6 +230,16 @@
> > > @@ -61,7 +61,7 @@ index 64c27c9cfac..a693cb8a886 100644
> > > optimizer and back end) to be checked for dynamic type safety at
> > runtime.
> > > This is quite expensive. */
> > > diff --git a/gcc/configure b/gcc/configure
> > > -index 5ce0557719a..dc2d59701ad 100755
> > > +index 2b83acfb0..8bb97578c 100755
> > > --- a/gcc/configure
> > > +++ b/gcc/configure
> > > @@ -1023,6 +1023,7 @@ enable_maintainer_mode
> > > @@ -81,7 +81,7 @@ index 5ce0557719a..dc2d59701ad 100755
> > >--enable-plugin enable plugin support
> > >--enable-host-sharedbuild host code as shared libraries
> > >--disable-libquadmath-support
> > > -@@ -31982,6 +31985,22 @@ if test
> > "${enable_version_specific_runtime_libs+set}" = set; then :
> > > +@@ -31996,6 +31999,22 @@ if test
> > "${enable_version_specific_runtime_libs+set}" = set; then :
> > > fi
> > >
> > >
> > > @@ -105,10 +105,10 @@ index 5ce0557719a..dc2d59701ad 100755
> > >
> > >
> > > diff --git a/gcc/configure.ac b/gcc/configure.ac
> > > -index 23bee7010a3..36ce78924de
Re: [OE-core] [PATCH] gcc: Allow -Wno-error=poison-system-directories to take effect
> -Original Message-
> From: Ross Burton
> Sent: den 13 oktober 2022 16:05
> To: Peter Kjellerstedt
> Cc: Patches and discussions about the oe-core layer c...@lists.openembedded.org>
> Subject: Re: [OE-core] [PATCH] gcc: Allow -Wno-error=poison-system-
> directories to take effect
>
> Whilst this is a good fix, I’m horrified to ask why you need it…
We have a recipe for skia. Somewhere in that mess of a build
system it uses (gn), something adds -I/usr/include/freetype2,
which results in an error with -Werror=poison-system-directories
enabled (as it should). Now, to work around that problem, the
recipe currently adds -I=/usr/include/freetype2, which means we
know that the correct path is used. However, since the original
-I/usr/include/freetype2 is still in the list of options, the
error still triggers.
Now, to fix the problem properly, skias's build files should be
patched, but that is not my job. What I am working on is to get
our recipes to build with Langdale. This means I can cut some
corners and, e.g., disable errors and then hand off to the
responsible team to fix the underlying problem at a time that
suits them. Thus in this case I wanted to add
-Wno-error=poison-system-directories for skia, which I then, to
my surprise, noticed had no effect...
//Peter
>
> Ross
>
> > On 13 Oct 2022, at 14:29, Peter Kjellerstedt via lists.openembedded.org
> wrote:
> >
> > The change in commit e903b29f (gcc-cross: pass
> > -Werror=poison-system-directories to compiler stages) made it impossible
> > to disable the error using -Wno-error=poison-system-directories.
> >
> > Signed-off-by: Peter Kjellerstedt
> > ---
> > .../0002-gcc-poison-system-directories.patch | 36 +--
> > 1 file changed, 18 insertions(+), 18 deletions(-)
> >
> > diff --git a/meta/recipes-devtools/gcc/gcc/0002-gcc-poison-system-
> directories.patch b/meta/recipes-devtools/gcc/gcc/0002-gcc-poison-system-
> directories.patch
> > index bfec4477c1..5aa635b3d4 100644
> > --- a/meta/recipes-devtools/gcc/gcc/0002-gcc-poison-system-
> directories.patch
> > +++ b/meta/recipes-devtools/gcc/gcc/0002-gcc-poison-system-
> directories.patch
> > @@ -1,4 +1,4 @@
> > -From e1dbdcd0ea667bab4b551294354e04c6fe288ab6 Mon Sep 17 00:00:00 2001
> > +From 99f1e61b2957226254a116fde7fd73bf07034012 Mon Sep 17 00:00:00 2001
> > From: Khem Raj
> > Date: Mon, 8 Mar 2021 16:04:20 -0800
> > Subject: [PATCH] gcc: poison-system-directories
> > @@ -20,12 +20,12 @@ Signed-off-by: Khem Raj
> > gcc/configure | 19 +++
> > gcc/configure.ac| 16
> > gcc/doc/invoke.texi | 9 +
> > - gcc/gcc.cc | 9 +++--
> > + gcc/gcc.cc | 15 ---
> > gcc/incpath.cc | 21 +
> > - 7 files changed, 86 insertions(+), 2 deletions(-)
> > + 7 files changed, 91 insertions(+), 3 deletions(-)
> >
> > diff --git a/gcc/common.opt b/gcc/common.opt
> > -index 8a0dafc522d..0357868e22c 100644
> > +index 8a0dafc52..0357868e2 100644
> > --- a/gcc/common.opt
> > +++ b/gcc/common.opt
> > @@ -710,6 +710,10 @@ Wreturn-local-addr
> > @@ -40,7 +40,7 @@ index 8a0dafc522d..0357868e22c 100644
> > Common Var(warn_shadow) Warning
> > Warn when one variable shadows another. Same as -Wshadow=global.
> > diff --git a/gcc/config.in b/gcc/config.in
> > -index 64c27c9cfac..a693cb8a886 100644
> > +index 64c27c9cf..a693cb8a8 100644
> > --- a/gcc/config.in
> > +++ b/gcc/config.in
> > @@ -230,6 +230,16 @@
> > @@ -61,7 +61,7 @@ index 64c27c9cfac..a693cb8a886 100644
> > optimizer and back end) to be checked for dynamic type safety at
> runtime.
> > This is quite expensive. */
> > diff --git a/gcc/configure b/gcc/configure
> > -index 5ce0557719a..dc2d59701ad 100755
> > +index 2b83acfb0..8bb97578c 100755
> > --- a/gcc/configure
> > +++ b/gcc/configure
> > @@ -1023,6 +1023,7 @@ enable_maintainer_mode
> > @@ -81,7 +81,7 @@ index 5ce0557719a..dc2d59701ad 100755
> >--enable-plugin enable plugin support
> >--enable-host-sharedbuild host code as shared libraries
> >--disable-libquadmath-support
> > -@@ -31982,6 +31985,22 @@ if test
> "${enable_version_specific_runtime_libs+set}" = set; then :
> > +@@ -31996,6 +31999,22 @@ if test
> "${enable_version_specific_runtime_libs+set}" = set; then :
> > fi
> >
> >
> > @@ -105,10 +105,10 @@ index 5ce0557719a..dc2d59701ad 100755
> >
> >
> > diff --git a/gcc/configure.ac b/gcc/configure.ac
> > -index 23bee7010a3..36ce78924de 100644
> > +index daf2a708c..6155b83a7 100644
> > --- a/gcc/configure.ac
> > +++ b/gcc/configure.ac
> > -@@ -7421,6 +7421,22 @@ AC_ARG_ENABLE(version-specific-runtime-libs,
> > +@@ -7435,6 +7435,22 @@ AC_ARG_ENABLE(version-specific-runtime-libs,
> > [specify that runtime libraries should be
> > installed in a compiler-specific directory])])
> >
> > @@ -132,7 +132,7 @@ index 23bee7010a3..36ce78924de 100644
> > AC_SUBST(subdirs)
> > AC_SUBST(srcdir)
> > diff --git
Re: [OE-core] [PATCH] gcc: Allow -Wno-error=poison-system-directories to take effect
Whilst this is a good fix, I’m horrified to ask why you need it…
Ross
> On 13 Oct 2022, at 14:29, Peter Kjellerstedt via lists.openembedded.org
> wrote:
>
> The change in commit e903b29f (gcc-cross: pass
> -Werror=poison-system-directories to compiler stages) made it impossible
> to disable the error using -Wno-error=poison-system-directories.
>
> Signed-off-by: Peter Kjellerstedt
> ---
> .../0002-gcc-poison-system-directories.patch | 36 +--
> 1 file changed, 18 insertions(+), 18 deletions(-)
>
> diff --git
> a/meta/recipes-devtools/gcc/gcc/0002-gcc-poison-system-directories.patch
> b/meta/recipes-devtools/gcc/gcc/0002-gcc-poison-system-directories.patch
> index bfec4477c1..5aa635b3d4 100644
> --- a/meta/recipes-devtools/gcc/gcc/0002-gcc-poison-system-directories.patch
> +++ b/meta/recipes-devtools/gcc/gcc/0002-gcc-poison-system-directories.patch
> @@ -1,4 +1,4 @@
> -From e1dbdcd0ea667bab4b551294354e04c6fe288ab6 Mon Sep 17 00:00:00 2001
> +From 99f1e61b2957226254a116fde7fd73bf07034012 Mon Sep 17 00:00:00 2001
> From: Khem Raj
> Date: Mon, 8 Mar 2021 16:04:20 -0800
> Subject: [PATCH] gcc: poison-system-directories
> @@ -20,12 +20,12 @@ Signed-off-by: Khem Raj
> gcc/configure | 19 +++
> gcc/configure.ac| 16
> gcc/doc/invoke.texi | 9 +
> - gcc/gcc.cc | 9 +++--
> + gcc/gcc.cc | 15 ---
> gcc/incpath.cc | 21 +
> - 7 files changed, 86 insertions(+), 2 deletions(-)
> + 7 files changed, 91 insertions(+), 3 deletions(-)
>
> diff --git a/gcc/common.opt b/gcc/common.opt
> -index 8a0dafc522d..0357868e22c 100644
> +index 8a0dafc52..0357868e2 100644
> --- a/gcc/common.opt
> +++ b/gcc/common.opt
> @@ -710,6 +710,10 @@ Wreturn-local-addr
> @@ -40,7 +40,7 @@ index 8a0dafc522d..0357868e22c 100644
> Common Var(warn_shadow) Warning
> Warn when one variable shadows another. Same as -Wshadow=global.
> diff --git a/gcc/config.in b/gcc/config.in
> -index 64c27c9cfac..a693cb8a886 100644
> +index 64c27c9cf..a693cb8a8 100644
> --- a/gcc/config.in
> +++ b/gcc/config.in
> @@ -230,6 +230,16 @@
> @@ -61,7 +61,7 @@ index 64c27c9cfac..a693cb8a886 100644
> optimizer and back end) to be checked for dynamic type safety at runtime.
> This is quite expensive. */
> diff --git a/gcc/configure b/gcc/configure
> -index 5ce0557719a..dc2d59701ad 100755
> +index 2b83acfb0..8bb97578c 100755
> --- a/gcc/configure
> +++ b/gcc/configure
> @@ -1023,6 +1023,7 @@ enable_maintainer_mode
> @@ -81,7 +81,7 @@ index 5ce0557719a..dc2d59701ad 100755
>--enable-plugin enable plugin support
>--enable-host-sharedbuild host code as shared libraries
>--disable-libquadmath-support
> -@@ -31982,6 +31985,22 @@ if test
> "${enable_version_specific_runtime_libs+set}" = set; then :
> +@@ -31996,6 +31999,22 @@ if test
> "${enable_version_specific_runtime_libs+set}" = set; then :
> fi
>
>
> @@ -105,10 +105,10 @@ index 5ce0557719a..dc2d59701ad 100755
>
>
> diff --git a/gcc/configure.ac b/gcc/configure.ac
> -index 23bee7010a3..36ce78924de 100644
> +index daf2a708c..6155b83a7 100644
> --- a/gcc/configure.ac
> +++ b/gcc/configure.ac
> -@@ -7421,6 +7421,22 @@ AC_ARG_ENABLE(version-specific-runtime-libs,
> +@@ -7435,6 +7435,22 @@ AC_ARG_ENABLE(version-specific-runtime-libs,
> [specify that runtime libraries should be
> installed in a compiler-specific directory])])
>
> @@ -132,7 +132,7 @@ index 23bee7010a3..36ce78924de 100644
> AC_SUBST(subdirs)
> AC_SUBST(srcdir)
> diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
> -index 07b440190c3..b2de464798a 100644
> +index ff6c338be..a8ebfa59a 100644
> --- a/gcc/doc/invoke.texi
> +++ b/gcc/doc/invoke.texi
> @@ -379,6 +379,7 @@ Objective-C and Objective-C++ Dialects}.
> @@ -159,10 +159,10 @@ index 07b440190c3..b2de464798a 100644
> @opindex Wfloat-equal
> @opindex Wno-float-equal
> diff --git a/gcc/gcc.cc b/gcc/gcc.cc
> -index bb07cc244e3..ce161d3c853 100644
> +index beefde7f6..4e6557b3c 100644
> --- a/gcc/gcc.cc
> +++ b/gcc/gcc.cc
> -@@ -1159,6 +1159,8 @@ proper position among the other output files. */
> +@@ -1162,6 +1162,8 @@ proper position among the other output files. */
> "%{fuse-ld=*:-fuse-ld=%*} " LINK_COMPRESS_DEBUG_SPEC \
> "%X %{o*} %{e*} %{N} %{n} %{r}\
> %{s} %{t} %{u*} %{z} %{Z} %{!nostdlib:%{!r:%{!nostartfiles:%S}}} \
> @@ -171,7 +171,7 @@ index bb07cc244e3..ce161d3c853 100644
> %{static|no-pie|static-pie:} %@{L*} %(mfwrap) %(link_libgcc) " \
> VTABLE_VERIFICATION_SPEC " " SANITIZER_EARLY_SPEC " %o "" \
> %{fopenacc|fopenmp|%:gt(%{ftree-parallelize-loops=*:%*} 1):\
> -@@ -1254,8 +1256,11 @@ static const char *cpp_unique_options =
> +@@ -1257,8 +1259,11 @@ static const char *cpp_unique_options =
> static const char *cpp_options =
> "%(cpp_unique_options) %1 %{m*} %{std*} %{W**} %{w}\
> %{f*} %{g*:%{%:debug-level-gt(0):%{g*}\
> @@ -179,27 +179,27 @@ index
Re: [OE-core] [kirkstone] core-image-weston doesn't build
On Thu, Oct 13, 2022 at 2:59 AM Marta Rybczynska wrote: > $ bitbake weston > Loading cache: 100% > > |###| > Time: 0:00:00 > Loaded 1640 entries from dependency cache. > ERROR: Nothing PROVIDES 'weston' > weston was skipped: missing required distro features 'wayland opengl' > (not in DISTRO_FEATURES) > > Summary: There was 1 ERROR message, returning a non-zero exit code. > > I can add distro-features et al, just wondering if this image is > expected to build by default with oe-core? With poky yes but with vanilla oe-core it needs to enable OpenGL by default for nodistro > > > Regards, > Marta > > On Thu, Oct 13, 2022 at 10:15 AM Alexander Kanavin > wrote: > > > > What happens when you run 'bitbake weston'? > > > > Alex > > > > On Thu, 13 Oct 2022 at 10:10, Marta Rybczynska > wrote: > > > > > > > > > > > > On Thu, 13 Oct 2022, 17:00 Alexandre Belloni, < > alexandre.bell...@bootlin.com> wrote: > > >> > > >> On 13/10/2022 09:52:44+0200, Marta Rybczynska wrote: > > >> > Hello all, > > >> > I'm trying to build the core-image-weston in kirkstone to look into > > >> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=14926 > > >> > > > >> > It turns out that the image does not build (oe-core > > >> > e728d0965d6fda8ac54e065ca7bf7eb9da9a8170 with bitbake > > >> > 6603c3e39f1cf746669ec6c9f0be8c6e6ece426e). I'm getting: > > >> > > > >> > $ bitbake core-image-weston > > >> > Loading cache: 100% > > >> > > |###| > > >> > Time: 0:00:00 > > >> > Loaded 1640 entries from dependency cache. > > >> > NOTE: Resolving any missing task queue dependencies > > >> > ERROR: Nothing RPROVIDES 'weston-xwayland' (but > > >> > /oe-standalone/oe-core/meta/recipes-graphics/images/ > core-image-weston.bb > > >> > RDEPENDS on > > >> > or otherwise requires it) > > >> > NOTE: Runtime target 'weston-xwayland' is unbuildable, removing... > > >> > Missing or unbuildable dependency chain was: ['weston-xwayland'] > > >> > ERROR: Required build target 'core-image-weston' has no buildable > providers. > > >> > Missing or unbuildable dependency chain was: ['core-image-weston', > > >> > 'weston-xwayland'] > > >> > > > >> > Summary: There were 2 ERROR messages, returning a non-zero exit > code. > > >> > > > >> > I can't find this one in bugzilla. Is it a known issue? > > >> > > > >> > > >> Did you remove x11 from your DISTRO_FEATURES? > > > > > > > > > No. This is a fresh clone. The only changes I have are in local.conf: > DL_DIR and parallel build options. That's why I'm surprised. > > > > > > Regards > > > Marta > > > > > > > > > > > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171704): https://lists.openembedded.org/g/openembedded-core/message/171704 Mute This Topic: https://lists.openembedded.org/mt/94299411/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] gcc: Allow -Wno-error=poison-system-directories to take effect
The change in commit e903b29f (gcc-cross: pass
-Werror=poison-system-directories to compiler stages) made it impossible
to disable the error using -Wno-error=poison-system-directories.
Signed-off-by: Peter Kjellerstedt
---
.../0002-gcc-poison-system-directories.patch | 36 +--
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git
a/meta/recipes-devtools/gcc/gcc/0002-gcc-poison-system-directories.patch
b/meta/recipes-devtools/gcc/gcc/0002-gcc-poison-system-directories.patch
index bfec4477c1..5aa635b3d4 100644
--- a/meta/recipes-devtools/gcc/gcc/0002-gcc-poison-system-directories.patch
+++ b/meta/recipes-devtools/gcc/gcc/0002-gcc-poison-system-directories.patch
@@ -1,4 +1,4 @@
-From e1dbdcd0ea667bab4b551294354e04c6fe288ab6 Mon Sep 17 00:00:00 2001
+From 99f1e61b2957226254a116fde7fd73bf07034012 Mon Sep 17 00:00:00 2001
From: Khem Raj
Date: Mon, 8 Mar 2021 16:04:20 -0800
Subject: [PATCH] gcc: poison-system-directories
@@ -20,12 +20,12 @@ Signed-off-by: Khem Raj
gcc/configure | 19 +++
gcc/configure.ac| 16
gcc/doc/invoke.texi | 9 +
- gcc/gcc.cc | 9 +++--
+ gcc/gcc.cc | 15 ---
gcc/incpath.cc | 21 +
- 7 files changed, 86 insertions(+), 2 deletions(-)
+ 7 files changed, 91 insertions(+), 3 deletions(-)
diff --git a/gcc/common.opt b/gcc/common.opt
-index 8a0dafc522d..0357868e22c 100644
+index 8a0dafc52..0357868e2 100644
--- a/gcc/common.opt
+++ b/gcc/common.opt
@@ -710,6 +710,10 @@ Wreturn-local-addr
@@ -40,7 +40,7 @@ index 8a0dafc522d..0357868e22c 100644
Common Var(warn_shadow) Warning
Warn when one variable shadows another. Same as -Wshadow=global.
diff --git a/gcc/config.in b/gcc/config.in
-index 64c27c9cfac..a693cb8a886 100644
+index 64c27c9cf..a693cb8a8 100644
--- a/gcc/config.in
+++ b/gcc/config.in
@@ -230,6 +230,16 @@
@@ -61,7 +61,7 @@ index 64c27c9cfac..a693cb8a886 100644
optimizer and back end) to be checked for dynamic type safety at runtime.
This is quite expensive. */
diff --git a/gcc/configure b/gcc/configure
-index 5ce0557719a..dc2d59701ad 100755
+index 2b83acfb0..8bb97578c 100755
--- a/gcc/configure
+++ b/gcc/configure
@@ -1023,6 +1023,7 @@ enable_maintainer_mode
@@ -81,7 +81,7 @@ index 5ce0557719a..dc2d59701ad 100755
--enable-plugin enable plugin support
--enable-host-sharedbuild host code as shared libraries
--disable-libquadmath-support
-@@ -31982,6 +31985,22 @@ if test "${enable_version_specific_runtime_libs+set}"
= set; then :
+@@ -31996,6 +31999,22 @@ if test "${enable_version_specific_runtime_libs+set}"
= set; then :
fi
@@ -105,10 +105,10 @@ index 5ce0557719a..dc2d59701ad 100755
diff --git a/gcc/configure.ac b/gcc/configure.ac
-index 23bee7010a3..36ce78924de 100644
+index daf2a708c..6155b83a7 100644
--- a/gcc/configure.ac
+++ b/gcc/configure.ac
-@@ -7421,6 +7421,22 @@ AC_ARG_ENABLE(version-specific-runtime-libs,
+@@ -7435,6 +7435,22 @@ AC_ARG_ENABLE(version-specific-runtime-libs,
[specify that runtime libraries should be
installed in a compiler-specific directory])])
@@ -132,7 +132,7 @@ index 23bee7010a3..36ce78924de 100644
AC_SUBST(subdirs)
AC_SUBST(srcdir)
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
-index 07b440190c3..b2de464798a 100644
+index ff6c338be..a8ebfa59a 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -379,6 +379,7 @@ Objective-C and Objective-C++ Dialects}.
@@ -159,10 +159,10 @@ index 07b440190c3..b2de464798a 100644
@opindex Wfloat-equal
@opindex Wno-float-equal
diff --git a/gcc/gcc.cc b/gcc/gcc.cc
-index bb07cc244e3..ce161d3c853 100644
+index beefde7f6..4e6557b3c 100644
--- a/gcc/gcc.cc
+++ b/gcc/gcc.cc
-@@ -1159,6 +1159,8 @@ proper position among the other output files. */
+@@ -1162,6 +1162,8 @@ proper position among the other output files. */
"%{fuse-ld=*:-fuse-ld=%*} " LINK_COMPRESS_DEBUG_SPEC \
"%X %{o*} %{e*} %{N} %{n} %{r}\
%{s} %{t} %{u*} %{z} %{Z} %{!nostdlib:%{!r:%{!nostartfiles:%S}}} \
@@ -171,7 +171,7 @@ index bb07cc244e3..ce161d3c853 100644
%{static|no-pie|static-pie:} %@{L*} %(mfwrap) %(link_libgcc) " \
VTABLE_VERIFICATION_SPEC " " SANITIZER_EARLY_SPEC " %o "" \
%{fopenacc|fopenmp|%:gt(%{ftree-parallelize-loops=*:%*} 1):\
-@@ -1254,8 +1256,11 @@ static const char *cpp_unique_options =
+@@ -1257,8 +1259,11 @@ static const char *cpp_unique_options =
static const char *cpp_options =
"%(cpp_unique_options) %1 %{m*} %{std*} %{W**} %{w}\
%{f*} %{g*:%{%:debug-level-gt(0):%{g*}\
@@ -179,27 +179,27 @@ index bb07cc244e3..ce161d3c853 100644
- %{undef} %{save-temps*:-fpch-preprocess}";
+ %{!fno-working-directory:-fworking-directory}}} %{O*}"
+#ifdef POISON_BY_DEFAULT
-+ " -Werror=poison-system-directories"
++ " %{!Wno-error=poison-system-directories:-Werror=poison-system-directories}"
+#endif
+ " %{undef}
Re: [OE-Core][PATCH] rust: update 1.63.0 -> 1.64.0
On Thu, Oct 13, 2022 at 9:13 AM Alexandre Belloni
wrote:
>
> Hello,
>
> On 12/10/2022 08:17:14+0100, Alex Kiernan wrote:
> > Release notes:
> > https://blog.rust-lang.org/2022/09/22/Rust-1.64.0.html
> >
>
> This causes the following failure:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/5901/steps/12/logs/stdio
>
> ERROR: rust-1.64.0-r0 do_patch: Applying patch 'crossbeam_atomic.patch' on
> target directory
> '/home/pokybuild/yocto-worker/qemux86-world/build/build/tmp/work/core2-64-poky-linux/rust/1.64.0-r0/rustc-1.64.0-src'
> CmdError('quilt --quiltrc
> /home/pokybuild/yocto-worker/qemux86-world/build/build/tmp/work/core2-64-poky-linux/rust/1.64.0-r0/recipe-sysroot-native/etc/quiltrc
> push', 0, 'stdout: Applying patch crossbeam_atomic.patch
> patching file vendor/crossbeam-utils/build.rs
> patching file vendor/crossbeam-utils/.cargo-checksum.json
> Hunk #1 FAILED at 1.
> 1 out of 1 hunk FAILED -- rejects in file
> vendor/crossbeam-utils/.cargo-checksum.json
> Patch crossbeam_atomic.patch does not apply (enforce with -f)
>
How odd... I was half expecting that to need rework and was surprised
when I tested it locally that it didn't! Clearly I've missed
something...
--
Alex Kiernan
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171702):
https://lists.openembedded.org/g/openembedded-core/message/171702
Mute This Topic: https://lists.openembedded.org/mt/94276338/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] eSDK dependencies
Hi Ross, I did that. current behavior: $ devtool modify busybox Initialising tasks: 100% |###| Time: 0:00:00 Sstate summary: Wanted 14 Local 0 Mirrors 0 Missed 14 Current 6 (0% match, 30% complete) NOTE: Executing Tasks ... your new behavior: @@ -52,7 +52,7 @@ def check(args): try: output = subprocess.check_output( -'bitbake -n %s' % ' '.join(args.target), +'bitbake --runall build -n %s' % ' '.join(args.target), stderr=subprocess.STDOUT, env=env, $ devtool modify busybox Initialising tasks: 100% |###| Time: 0:00:00 Sstate summary: Wanted 14 Local 4 Mirrors 0 Missed 10 Current 6 (28% match, 50% complete) NOTE: Executing Tasks ... It just start fetching, patching... tasks without any dependencies build. Looks like, that this is exactly what we wanted to achieve. Let me ask the question about the percentage... why is 28% of match? Regards, Andrej On Thu, 2022-10-13 at 10:15 +, Ross Burton wrote: > > > > On 13 Oct 2022, at 09:23, Andrej Valek via lists.openembedded.org > > wrote: > > I had some time and made some more testing. > > > > Looks like, that the problematic commits are here: > > https://github.com/openembedded/openembedded-core/commit/41d7f1aa2cc9ef5dba4db38435402d4c9c0a63e1 > > https://github.com/openembedded/openembedded-core/commit/6e2cbfc561dac89bf9183d24d90e52f7d9117826 > > https://github.com/openembedded/openembedded-core/commit/030d56e2e8ece93472adc51fe467221d846c9ac0 > > > > Means, that recursive do_build task is not being executed on image > > level anymore. After re-creating/adding the meta class and inheriting > > it in populate_sdk_base, the image now contains all the missing deps. > > > > I tried to execute the "bitbake my-image -c populate_sdk_ext --runall > > build", but "--runall" destroyed the populate_sdk_ext task, so in > > this > > case is unusable. > > > > So what's the right way to get it working again? > > So the good news is that a few others reported this issue and a bug was > filed: > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=14626 > > Annoyingly, nobody who saw the bug remembered this thread. > > My hunch was that dependency rationalisation meant less > do_populate_sysroot calls, based on how the eSDK creation is done. If > you’ve isolated it down to those commits then that’s an indication my > hunch was right. > > Can you test something for me? Switch back to pristine oe-core without > the reverts, and add the ‘—runall build’ option to the bitbake call in > scripts/oe-check-sstate (line ~54). > > Thanks, > Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171701): https://lists.openembedded.org/g/openembedded-core/message/171701 Mute This Topic: https://lists.openembedded.org/mt/92019337/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] wic: implement binary repeatable disk identifiers
From: Sergei Zhmylev
When SOURCE_DATE_EPOCH variable is set, binary repeatable build
is expected. This commit implements reproducable disk identifiers
in such a case using its value as a Random seed.
Signed-off-by: Sergei Zhmylev
---
scripts/lib/wic/plugins/imager/direct.py | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/scripts/lib/wic/plugins/imager/direct.py
b/scripts/lib/wic/plugins/imager/direct.py
index da483daed5..6faa16bf9b 100644
--- a/scripts/lib/wic/plugins/imager/direct.py
+++ b/scripts/lib/wic/plugins/imager/direct.py
@@ -310,7 +310,10 @@ class PartitionedImage():
# all partitions (in bytes)
self.ptable_format = ptable_format # Partition table format
# Disk system identifier
-self.identifier = random.SystemRandom().randint(1, 0x)
+if os.getenv('SOURCE_DATE_EPOCH'):
+self.identifier =
random.Random(int(os.getenv('SOURCE_DATE_EPOCH'))).randint(1, 0x)
+else:
+self.identifier = random.SystemRandom().randint(1, 0x)
self.partitions = partitions
self.partimages = []
--
2.37.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171700):
https://lists.openembedded.org/g/openembedded-core/message/171700
Mute This Topic: https://lists.openembedded.org/mt/94301039/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 v3] mesa: only apply patch to fix ALWAYS_INLINE for native
On 12 Oct 2022, at 21:51, Khem Raj via lists.openembedded.org wrote: > As per https://wiki.yoctoproject.org/wiki/Weekly_Status, master is frozen for > release and RP is on vacation, so patches are being review/accumulated but > are not merging just yet. > > Can we publish the staging branch somewhere on poky-contrib or > oe-core-contrib There are a few. My usual staging branch is ross/mut on poky-contrib. It’s a bit of a mess usually... Alex and Luca are very efficient at sweeping the lists and doing builds. Their staging branches are on openembedded-core-contrib: abelloni/master-next and lucaceresoli/master-next respectively. Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171699): https://lists.openembedded.org/g/openembedded-core/message/171699 Mute This Topic: https://lists.openembedded.org/mt/94012441/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] eSDK dependencies
> On 13 Oct 2022, at 09:23, Andrej Valek via lists.openembedded.org > wrote: > I had some time and made some more testing. > > Looks like, that the problematic commits are here: > https://github.com/openembedded/openembedded-core/commit/41d7f1aa2cc9ef5dba4db38435402d4c9c0a63e1 > https://github.com/openembedded/openembedded-core/commit/6e2cbfc561dac89bf9183d24d90e52f7d9117826 > https://github.com/openembedded/openembedded-core/commit/030d56e2e8ece93472adc51fe467221d846c9ac0 > > Means, that recursive do_build task is not being executed on image > level anymore. After re-creating/adding the meta class and inheriting > it in populate_sdk_base, the image now contains all the missing deps. > > I tried to execute the "bitbake my-image -c populate_sdk_ext --runall > build", but "--runall" destroyed the populate_sdk_ext task, so in this > case is unusable. > > So what's the right way to get it working again? So the good news is that a few others reported this issue and a bug was filed: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14626 Annoyingly, nobody who saw the bug remembered this thread. My hunch was that dependency rationalisation meant less do_populate_sysroot calls, based on how the eSDK creation is done. If you’ve isolated it down to those commits then that’s an indication my hunch was right. Can you test something for me? Switch back to pristine oe-core without the reverts, and add the ‘—runall build’ option to the bitbake call in scripts/oe-check-sstate (line ~54). Thanks, Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171698): https://lists.openembedded.org/g/openembedded-core/message/171698 Mute This Topic: https://lists.openembedded.org/mt/92019337/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] [kirkstone] core-image-weston doesn't build
I guess it’s not. I’ve been pushing to enable these in oe-core but we’re not there yet. You get them enabled by default in poky. Alex On Thu 13. Oct 2022 at 11.59, Marta Rybczynska wrote: > $ bitbake weston > Loading cache: 100% > > |###| > Time: 0:00:00 > Loaded 1640 entries from dependency cache. > ERROR: Nothing PROVIDES 'weston' > weston was skipped: missing required distro features 'wayland opengl' > (not in DISTRO_FEATURES) > > Summary: There was 1 ERROR message, returning a non-zero exit code. > > I can add distro-features et al, just wondering if this image is > expected to build by default with oe-core? > > Regards, > Marta > > On Thu, Oct 13, 2022 at 10:15 AM Alexander Kanavin > wrote: > > > > What happens when you run 'bitbake weston'? > > > > Alex > > > > On Thu, 13 Oct 2022 at 10:10, Marta Rybczynska > wrote: > > > > > > > > > > > > On Thu, 13 Oct 2022, 17:00 Alexandre Belloni, < > alexandre.bell...@bootlin.com> wrote: > > >> > > >> On 13/10/2022 09:52:44+0200, Marta Rybczynska wrote: > > >> > Hello all, > > >> > I'm trying to build the core-image-weston in kirkstone to look into > > >> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=14926 > > >> > > > >> > It turns out that the image does not build (oe-core > > >> > e728d0965d6fda8ac54e065ca7bf7eb9da9a8170 with bitbake > > >> > 6603c3e39f1cf746669ec6c9f0be8c6e6ece426e). I'm getting: > > >> > > > >> > $ bitbake core-image-weston > > >> > Loading cache: 100% > > >> > > |###| > > >> > Time: 0:00:00 > > >> > Loaded 1640 entries from dependency cache. > > >> > NOTE: Resolving any missing task queue dependencies > > >> > ERROR: Nothing RPROVIDES 'weston-xwayland' (but > > >> > /oe-standalone/oe-core/meta/recipes-graphics/images/ > core-image-weston.bb > > >> > RDEPENDS on > > >> > or otherwise requires it) > > >> > NOTE: Runtime target 'weston-xwayland' is unbuildable, removing... > > >> > Missing or unbuildable dependency chain was: ['weston-xwayland'] > > >> > ERROR: Required build target 'core-image-weston' has no buildable > providers. > > >> > Missing or unbuildable dependency chain was: ['core-image-weston', > > >> > 'weston-xwayland'] > > >> > > > >> > Summary: There were 2 ERROR messages, returning a non-zero exit > code. > > >> > > > >> > I can't find this one in bugzilla. Is it a known issue? > > >> > > > >> > > >> Did you remove x11 from your DISTRO_FEATURES? > > > > > > > > > No. This is a fresh clone. The only changes I have are in local.conf: > DL_DIR and parallel build options. That's why I'm surprised. > > > > > > Regards > > > Marta > > > > > > > > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171697): https://lists.openembedded.org/g/openembedded-core/message/171697 Mute This Topic: https://lists.openembedded.org/mt/94299411/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] [kirkstone] core-image-weston doesn't build
$ bitbake weston Loading cache: 100% |###| Time: 0:00:00 Loaded 1640 entries from dependency cache. ERROR: Nothing PROVIDES 'weston' weston was skipped: missing required distro features 'wayland opengl' (not in DISTRO_FEATURES) Summary: There was 1 ERROR message, returning a non-zero exit code. I can add distro-features et al, just wondering if this image is expected to build by default with oe-core? Regards, Marta On Thu, Oct 13, 2022 at 10:15 AM Alexander Kanavin wrote: > > What happens when you run 'bitbake weston'? > > Alex > > On Thu, 13 Oct 2022 at 10:10, Marta Rybczynska wrote: > > > > > > > > On Thu, 13 Oct 2022, 17:00 Alexandre Belloni, > > wrote: > >> > >> On 13/10/2022 09:52:44+0200, Marta Rybczynska wrote: > >> > Hello all, > >> > I'm trying to build the core-image-weston in kirkstone to look into > >> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=14926 > >> > > >> > It turns out that the image does not build (oe-core > >> > e728d0965d6fda8ac54e065ca7bf7eb9da9a8170 with bitbake > >> > 6603c3e39f1cf746669ec6c9f0be8c6e6ece426e). I'm getting: > >> > > >> > $ bitbake core-image-weston > >> > Loading cache: 100% > >> > |###| > >> > Time: 0:00:00 > >> > Loaded 1640 entries from dependency cache. > >> > NOTE: Resolving any missing task queue dependencies > >> > ERROR: Nothing RPROVIDES 'weston-xwayland' (but > >> > /oe-standalone/oe-core/meta/recipes-graphics/images/core-image-weston.bb > >> > RDEPENDS on > >> > or otherwise requires it) > >> > NOTE: Runtime target 'weston-xwayland' is unbuildable, removing... > >> > Missing or unbuildable dependency chain was: ['weston-xwayland'] > >> > ERROR: Required build target 'core-image-weston' has no buildable > >> > providers. > >> > Missing or unbuildable dependency chain was: ['core-image-weston', > >> > 'weston-xwayland'] > >> > > >> > Summary: There were 2 ERROR messages, returning a non-zero exit code. > >> > > >> > I can't find this one in bugzilla. Is it a known issue? > >> > > >> > >> Did you remove x11 from your DISTRO_FEATURES? > > > > > > No. This is a fresh clone. The only changes I have are in local.conf: > > DL_DIR and parallel build options. That's why I'm surprised. > > > > Regards > > Marta > > > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171696): https://lists.openembedded.org/g/openembedded-core/message/171696 Mute This Topic: https://lists.openembedded.org/mt/94299411/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] wic: honor the SOURCE_DATE_EPOCH in case of updated fstab
Hello, This seems to have caused the following failure: https://autobuilder.yoctoproject.org/typhoon/#/builders/23/builds/6301/steps/13/logs/stdio | DEBUG: Executing python function extend_recipe_sysroot | NOTE: Direct dependencies are ['/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-bsp/grub/grub-efi_2.06.bb:do_populate_sysroot', '/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-core/glibc/cross-localedef-native_2.36.bb:do_populate_sysroot', '/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-core/glibc/ldconfig-native_2.12.1.bb:do_populate_sysroot', '/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-core/os-release/os-release.bb:do_populate_sysroot', '/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-core/systemd/systemd-boot_251.4.bb:do_populate_sysroot', '/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/binutils/binutils-cross_2.39.bb:do_populate_sysroot', '/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/cdrtools/cdrtools-native_3.01.bb:do_populate_sysroot', '/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/python/python3_3.10.6.bb:do_populate_sysroot', '/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/qemu/qemu-system-native_7.1.0.bb:do_populate_sysroot', '/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/qemu/qemuwrapper-cross_1.0.bb:do_populate_sysroot', '/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/syslinux/syslinux_6.04-pre2.bb:do_populate_sysroot', '/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-kernel/kmod/depmodwrapper-cross_1.0.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-core/update-rc.d/update-rc.d_0.8.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/btrfs-tools/btrfs-tools_5.19.1.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/createrepo-c/createrepo-c_0.20.1.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/dnf/dnf_4.14.0.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/dosfstools/dosfstools_4.2.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.46.5.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/erofs-utils/erofs-utils_1.5.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/fdisk/gptfdisk_1.0.9.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/makedevs/makedevs_1.0.1.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/mtools/mtools_4.0.41.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/opkg-utils/opkg-utils_0.5.0.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/opkg/opkg_0.6.0.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/python/python3-installer_0.5.1.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/python/python3-picobuild_0.2.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/python/python3-pip_22.2.2.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/python/python3-setuptools_65.0.2.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/python/python3-wheel_0.37.1.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/python/python3_3.10.6.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/rpm/rpm_4.18.0.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-devtools/syslinux/syslinux_6.04-pre2.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-extended/parted/parted_3.5.bb:do_populate_sysroot',
Re: [OE-core] [kirkstone][PATCH] binutils : Fix CVE-2022-38128
Hi Pgowda,
Many thanks for your patches!
On 10/13/22 09:47, Pgowda wrote:
From: pgowda
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=f07c08e115e27cddf5a0030dc6332bbee1bd9c6a]
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=175b91507b83ad42607d2f6dadaf55b7b511bdbe]
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=patch;h=695c6dfe7e85006b98c8b746f3fd5f913c94ebff]
Signed-off-by: pgowda
---
.../binutils/binutils-2.38.inc| 3 +
.../binutils/0018-CVE-2022-38128-1.patch | 350 ++
.../binutils/0018-CVE-2022-38128-2.patch | 436 ++
.../binutils/0018-CVE-2022-38128-3.patch | 95
4 files changed, 884 insertions(+)
create mode 100644
meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-1.patch
create mode 100644
meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-2.patch
create mode 100644
meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-3.patch
Would it be possible to have your "Signed-off-by" and "From" fields with
your real name?
That's what is required on
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
("sorry, no pseudonyms or anonymous contributions").
Another issue is that this stands out in the release notes in the
section listing the contributors.
Thanks again
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171694):
https://lists.openembedded.org/g/openembedded-core/message/171694
Mute This Topic: https://lists.openembedded.org/mt/94299370/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] [RFC PATCH 0/6] (e)SDK workflow directly in a Yocto build
Cheers - try the new layer setup and config management tools too :-) Alex On Thu, 13 Oct 2022 at 10:44, Leon Woestenberg wrote: > > Hello Alexander, > > On Wed, Jun 22, 2022 at 12:33 PM Alexander Kanavin > wrote: > > > > There's been a recent discussion about how we can make the Yocto SDK > > experience better [1]. One of the ideas was to eliminate the SDK > > as a separate artefact altogether and simply provide everything > > that the SDK and eSDKs do directly in a yocto build. > > > > So without further ado, here's how you get a 'SDK' with this set of patches: > > > Thanks for this work! I like this approach. > > Regards, > > Leon. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171693): https://lists.openembedded.org/g/openembedded-core/message/171693 Mute This Topic: https://lists.openembedded.org/mt/91918831/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] [RFC PATCH 0/6] (e)SDK workflow directly in a Yocto build
Hello Alexander, On Wed, Jun 22, 2022 at 12:33 PM Alexander Kanavin wrote: > > There's been a recent discussion about how we can make the Yocto SDK > experience better [1]. One of the ideas was to eliminate the SDK > as a separate artefact altogether and simply provide everything > that the SDK and eSDKs do directly in a yocto build. > > So without further ado, here's how you get a 'SDK' with this set of patches: > Thanks for this work! I like this approach. Regards, Leon. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171692): https://lists.openembedded.org/g/openembedded-core/message/171692 Mute This Topic: https://lists.openembedded.org/mt/91918831/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core][kirkstone][PATCH] lttng-tools: Upgrade 2.13.4 -> 2.13.8
Signed-off-by: He Zhe
---
.../lttng/{lttng-tools_2.13.4.bb => lttng-tools_2.13.8.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-kernel/lttng/{lttng-tools_2.13.4.bb =>
lttng-tools_2.13.8.bb} (98%)
diff --git a/meta/recipes-kernel/lttng/lttng-tools_2.13.4.bb
b/meta/recipes-kernel/lttng/lttng-tools_2.13.8.bb
similarity index 98%
rename from meta/recipes-kernel/lttng/lttng-tools_2.13.4.bb
rename to meta/recipes-kernel/lttng/lttng-tools_2.13.8.bb
index 0ea4da05ce..0b6dfa48a4 100644
--- a/meta/recipes-kernel/lttng/lttng-tools_2.13.4.bb
+++ b/meta/recipes-kernel/lttng/lttng-tools_2.13.8.bb
@@ -39,7 +39,7 @@ SRC_URI =
"https://lttng.org/files/lttng-tools/lttng-tools-${PV}.tar.bz2 \
file://disable-tests.patch \
"
-SRC_URI[sha256sum] =
"565f3102410a53d484f4c8ff517978f1dc59f67f9d16f872f4357f3ca12200f6"
+SRC_URI[sha256sum] =
"b1e959579b260790930b20f3c7aa7cefb8a40e0de80d4a777c2bf78c6b353dc1"
inherit autotools ptest pkgconfig useradd python3-dir manpages systemd
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171691):
https://lists.openembedded.org/g/openembedded-core/message/171691
Mute This Topic: https://lists.openembedded.org/mt/94299823/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] eSDK dependencies
Hello again, I had some time and made some more testing. Looks like, that the problematic commits are here: https://github.com/openembedded/openembedded-core/commit/41d7f1aa2cc9ef5dba4db38435402d4c9c0a63e1 https://github.com/openembedded/openembedded-core/commit/6e2cbfc561dac89bf9183d24d90e52f7d9117826 https://github.com/openembedded/openembedded-core/commit/030d56e2e8ece93472adc51fe467221d846c9ac0 Means, that recursive do_build task is not being executed on image level anymore. After re-creating/adding the meta class and inheriting it in populate_sdk_base, the image now contains all the missing deps. I tried to execute the "bitbake my-image -c populate_sdk_ext --runall build", but "--runall" destroyed the populate_sdk_ext task, so in this case is unusable. So what's the right way to get it working again? Regards, Andrej On Tue, 2022-06-28 at 11:16 +0100, Richard Purdie wrote: > On Tue, 2022-06-28 at 07:55 +, Valek, Andrej wrote: > > Hello Richard and Alex, > > > > Richard: > > We tried to revert the commits which you mentioned and it didn't > > work. > > > > Alex: > > Yes, is fully reproducible on latest master. > > > > bitbake core-image-minimal -c populate_sdk_ext > > > > eSDK installed via: poky-glibc-x86_64-core-image-minimal- > > cortexa15t2hf- > > neon-qemuarm-toolchain-ext-4.1+snapshot.sh > > > > . environment-setup-cortexa15t2hf-neon-poky-linux-gnueabi > > devtool modify busybox > > > > Sstate summary: Wanted 14 Local 0 Mirrors 0 Missed 14 Current 6 (0% > > match, 30% complete) > > > > So it started a compilation of missing components. We are assuming, > > that eSDK will include all build deps for all components in the image > > and not just a deps for image itself. > > Ok. To confirm, SDK_EXT_TYPE is set to full in both cases? Could you > share the locked-sigs.inc file from both? I'd like to understand if the > tools are there but not being used or whether they're really not there > at all. Is there much of a size difference between the two eSDKs? > > I suspect some kind of bisection to track down the change causing the > issue will be necessary unfortunately but at least that test case is > relatively straightforward... > > Cheers, > > Richard > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171690): https://lists.openembedded.org/g/openembedded-core/message/171690 Mute This Topic: https://lists.openembedded.org/mt/92019337/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] [kirkstone] core-image-weston doesn't build
What happens when you run 'bitbake weston'? Alex On Thu, 13 Oct 2022 at 10:10, Marta Rybczynska wrote: > > > > On Thu, 13 Oct 2022, 17:00 Alexandre Belloni, > wrote: >> >> On 13/10/2022 09:52:44+0200, Marta Rybczynska wrote: >> > Hello all, >> > I'm trying to build the core-image-weston in kirkstone to look into >> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=14926 >> > >> > It turns out that the image does not build (oe-core >> > e728d0965d6fda8ac54e065ca7bf7eb9da9a8170 with bitbake >> > 6603c3e39f1cf746669ec6c9f0be8c6e6ece426e). I'm getting: >> > >> > $ bitbake core-image-weston >> > Loading cache: 100% >> > |###| >> > Time: 0:00:00 >> > Loaded 1640 entries from dependency cache. >> > NOTE: Resolving any missing task queue dependencies >> > ERROR: Nothing RPROVIDES 'weston-xwayland' (but >> > /oe-standalone/oe-core/meta/recipes-graphics/images/core-image-weston.bb >> > RDEPENDS on >> > or otherwise requires it) >> > NOTE: Runtime target 'weston-xwayland' is unbuildable, removing... >> > Missing or unbuildable dependency chain was: ['weston-xwayland'] >> > ERROR: Required build target 'core-image-weston' has no buildable >> > providers. >> > Missing or unbuildable dependency chain was: ['core-image-weston', >> > 'weston-xwayland'] >> > >> > Summary: There were 2 ERROR messages, returning a non-zero exit code. >> > >> > I can't find this one in bugzilla. Is it a known issue? >> > >> >> Did you remove x11 from your DISTRO_FEATURES? > > > No. This is a fresh clone. The only changes I have are in local.conf: DL_DIR > and parallel build options. That's why I'm surprised. > > Regards > Marta > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171689): https://lists.openembedded.org/g/openembedded-core/message/171689 Mute This Topic: https://lists.openembedded.org/mt/94299411/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] rust: update 1.63.0 -> 1.64.0
Hello,
On 12/10/2022 08:17:14+0100, Alex Kiernan wrote:
> Release notes:
> https://blog.rust-lang.org/2022/09/22/Rust-1.64.0.html
>
This causes the following failure:
https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/5901/steps/12/logs/stdio
ERROR: rust-1.64.0-r0 do_patch: Applying patch 'crossbeam_atomic.patch' on
target directory
'/home/pokybuild/yocto-worker/qemux86-world/build/build/tmp/work/core2-64-poky-linux/rust/1.64.0-r0/rustc-1.64.0-src'
CmdError('quilt --quiltrc
/home/pokybuild/yocto-worker/qemux86-world/build/build/tmp/work/core2-64-poky-linux/rust/1.64.0-r0/recipe-sysroot-native/etc/quiltrc
push', 0, 'stdout: Applying patch crossbeam_atomic.patch
patching file vendor/crossbeam-utils/build.rs
patching file vendor/crossbeam-utils/.cargo-checksum.json
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- rejects in file
vendor/crossbeam-utils/.cargo-checksum.json
Patch crossbeam_atomic.patch does not apply (enforce with -f)
> Signed-off-by: Alex Kiernan
> ---
> meta/conf/distro/include/tcmode-default.inc | 2 +-
> .../{cargo_1.63.0.bb => cargo_1.64.0.bb} | 0
> ...ibstd-rs_1.63.0.bb => libstd-rs_1.64.0.bb} | 0
> 63.0.bb => rust-cross-canadian_1.64.0.bb} | 0
> ...ust-llvm_1.63.0.bb => rust-llvm_1.64.0.bb} | 0
> meta/recipes-devtools/rust/rust-snapshot.inc | 22 +--
> meta/recipes-devtools/rust/rust-source.inc| 2 +-
> .../rust/{rust_1.63.0.bb => rust_1.64.0.bb} | 0
> 8 files changed, 13 insertions(+), 13 deletions(-)
> rename meta/recipes-devtools/cargo/{cargo_1.63.0.bb => cargo_1.64.0.bb}
> (100%)
> rename meta/recipes-devtools/rust/{libstd-rs_1.63.0.bb =>
> libstd-rs_1.64.0.bb} (100%)
> rename meta/recipes-devtools/rust/{rust-cross-canadian_1.63.0.bb =>
> rust-cross-canadian_1.64.0.bb} (100%)
> rename meta/recipes-devtools/rust/{rust-llvm_1.63.0.bb =>
> rust-llvm_1.64.0.bb} (100%)
> rename meta/recipes-devtools/rust/{rust_1.63.0.bb => rust_1.64.0.bb} (100%)
>
> diff --git a/meta/conf/distro/include/tcmode-default.inc
> b/meta/conf/distro/include/tcmode-default.inc
> index 59b226e62fcd..6bba92ac9696 100644
> --- a/meta/conf/distro/include/tcmode-default.inc
> +++ b/meta/conf/distro/include/tcmode-default.inc
> @@ -27,7 +27,7 @@ GOVERSION ?= "1.19%"
> # 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 ?= "14.0.6"
> -RUSTVERSION ?= "1.63%"
> +RUSTVERSION ?= "1.64%"
>
> PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
> PREFERRED_VERSION_gcc-cross-${TARGET_ARCH} ?= "${GCCVERSION}"
> diff --git a/meta/recipes-devtools/cargo/cargo_1.63.0.bb
> b/meta/recipes-devtools/cargo/cargo_1.64.0.bb
> similarity index 100%
> rename from meta/recipes-devtools/cargo/cargo_1.63.0.bb
> rename to meta/recipes-devtools/cargo/cargo_1.64.0.bb
> diff --git a/meta/recipes-devtools/rust/libstd-rs_1.63.0.bb
> b/meta/recipes-devtools/rust/libstd-rs_1.64.0.bb
> similarity index 100%
> rename from meta/recipes-devtools/rust/libstd-rs_1.63.0.bb
> rename to meta/recipes-devtools/rust/libstd-rs_1.64.0.bb
> diff --git a/meta/recipes-devtools/rust/rust-cross-canadian_1.63.0.bb
> b/meta/recipes-devtools/rust/rust-cross-canadian_1.64.0.bb
> similarity index 100%
> rename from meta/recipes-devtools/rust/rust-cross-canadian_1.63.0.bb
> rename to meta/recipes-devtools/rust/rust-cross-canadian_1.64.0.bb
> diff --git a/meta/recipes-devtools/rust/rust-llvm_1.63.0.bb
> b/meta/recipes-devtools/rust/rust-llvm_1.64.0.bb
> similarity index 100%
> rename from meta/recipes-devtools/rust/rust-llvm_1.63.0.bb
> rename to meta/recipes-devtools/rust/rust-llvm_1.64.0.bb
> diff --git a/meta/recipes-devtools/rust/rust-snapshot.inc
> b/meta/recipes-devtools/rust/rust-snapshot.inc
> index b9d7edd6720f..e790705aba0c 100644
> --- a/meta/recipes-devtools/rust/rust-snapshot.inc
> +++ b/meta/recipes-devtools/rust/rust-snapshot.inc
> @@ -5,21 +5,21 @@
> ## The version is replicated here.
> ## TODO: find a way to add additional SRC_URIs based on the contents of an
> ## earlier SRC_URI.
> -RS_VERSION = "1.62.0"
> -CARGO_VERSION = "1.62.0"
> +RS_VERSION = "1.63.0"
> +CARGO_VERSION = "1.63.0"
>
> # TODO: Add hashes for other architecture toolchains as well. Make a script?
> -SRC_URI[rust-std-snapshot-x86_64.sha256sum] =
> "addfae87b6b1b521d98a50fdc5120990888a51bb397100062e9c558267c67c77"
> -SRC_URI[rustc-snapshot-x86_64.sha256sum] =
> "e7f71f4ef09334ddc9ec8cbf2f958d654e36f580c95f8fec6d5c816ce256dbd6"
> -SRC_URI[cargo-snapshot-x86_64.sha256sum] =
> "815c63119a9cf0282ff240c6444b6f867238763ee3dea182f10837ae7dbbb1d4"
> +SRC_URI[rust-std-snapshot-x86_64.sha256sum] =
> "993c2c17bf76ac626bfb5b17bddce65fbdfc14f70d183f33773de0cd12df46d2"
> +SRC_URI[rustc-snapshot-x86_64.sha256sum] =
> "bdab9d9afa5c329c40f9ba568364815237fab8426477c12bfabad35ffc484ab5"
> +SRC_URI[cargo-snapshot-x86_64.sha256sum] =
>
Re: [OE-core] [kirkstone] core-image-weston doesn't build
On Thu, 13 Oct 2022, 17:00 Alexandre Belloni, wrote: > On 13/10/2022 09:52:44+0200, Marta Rybczynska wrote: > > Hello all, > > I'm trying to build the core-image-weston in kirkstone to look into > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=14926 > > > > It turns out that the image does not build (oe-core > > e728d0965d6fda8ac54e065ca7bf7eb9da9a8170 with bitbake > > 6603c3e39f1cf746669ec6c9f0be8c6e6ece426e). I'm getting: > > > > $ bitbake core-image-weston > > Loading cache: 100% > > > |###| > > Time: 0:00:00 > > Loaded 1640 entries from dependency cache. > > NOTE: Resolving any missing task queue dependencies > > ERROR: Nothing RPROVIDES 'weston-xwayland' (but > > /oe-standalone/oe-core/meta/recipes-graphics/images/core-image-weston.bb > > RDEPENDS on > > or otherwise requires it) > > NOTE: Runtime target 'weston-xwayland' is unbuildable, removing... > > Missing or unbuildable dependency chain was: ['weston-xwayland'] > > ERROR: Required build target 'core-image-weston' has no buildable > providers. > > Missing or unbuildable dependency chain was: ['core-image-weston', > > 'weston-xwayland'] > > > > Summary: There were 2 ERROR messages, returning a non-zero exit code. > > > > I can't find this one in bugzilla. Is it a known issue? > > > > Did you remove x11 from your DISTRO_FEATURES? > No. This is a fresh clone. The only changes I have are in local.conf: DL_DIR and parallel build options. That's why I'm surprised. Regards Marta > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171687): https://lists.openembedded.org/g/openembedded-core/message/171687 Mute This Topic: https://lists.openembedded.org/mt/94299411/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] [kirkstone] core-image-weston doesn't build
On 13/10/2022 09:52:44+0200, Marta Rybczynska wrote: > Hello all, > I'm trying to build the core-image-weston in kirkstone to look into > https://bugzilla.yoctoproject.org/show_bug.cgi?id=14926 > > It turns out that the image does not build (oe-core > e728d0965d6fda8ac54e065ca7bf7eb9da9a8170 with bitbake > 6603c3e39f1cf746669ec6c9f0be8c6e6ece426e). I'm getting: > > $ bitbake core-image-weston > Loading cache: 100% > |###| > Time: 0:00:00 > Loaded 1640 entries from dependency cache. > NOTE: Resolving any missing task queue dependencies > ERROR: Nothing RPROVIDES 'weston-xwayland' (but > /oe-standalone/oe-core/meta/recipes-graphics/images/core-image-weston.bb > RDEPENDS on > or otherwise requires it) > NOTE: Runtime target 'weston-xwayland' is unbuildable, removing... > Missing or unbuildable dependency chain was: ['weston-xwayland'] > ERROR: Required build target 'core-image-weston' has no buildable providers. > Missing or unbuildable dependency chain was: ['core-image-weston', > 'weston-xwayland'] > > Summary: There were 2 ERROR messages, returning a non-zero exit code. > > I can't find this one in bugzilla. Is it a known issue? > Did you remove x11 from your DISTRO_FEATURES? -- Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171686): https://lists.openembedded.org/g/openembedded-core/message/171686 Mute This Topic: https://lists.openembedded.org/mt/94299411/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [kirkstone] core-image-weston doesn't build
Hello all, I'm trying to build the core-image-weston in kirkstone to look into https://bugzilla.yoctoproject.org/show_bug.cgi?id=14926 It turns out that the image does not build (oe-core e728d0965d6fda8ac54e065ca7bf7eb9da9a8170 with bitbake 6603c3e39f1cf746669ec6c9f0be8c6e6ece426e). I'm getting: $ bitbake core-image-weston Loading cache: 100% |###| Time: 0:00:00 Loaded 1640 entries from dependency cache. NOTE: Resolving any missing task queue dependencies ERROR: Nothing RPROVIDES 'weston-xwayland' (but /oe-standalone/oe-core/meta/recipes-graphics/images/core-image-weston.bb RDEPENDS on or otherwise requires it) NOTE: Runtime target 'weston-xwayland' is unbuildable, removing... Missing or unbuildable dependency chain was: ['weston-xwayland'] ERROR: Required build target 'core-image-weston' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-weston', 'weston-xwayland'] Summary: There were 2 ERROR messages, returning a non-zero exit code. I can't find this one in bugzilla. Is it a known issue? Kind regards, Marta -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171685): https://lists.openembedded.org/g/openembedded-core/message/171685 Mute This Topic: https://lists.openembedded.org/mt/94299411/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [kirkstone][PATCH] binutils : Fix CVE-2022-38128
From: pgowda
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=f07c08e115e27cddf5a0030dc6332bbee1bd9c6a]
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=175b91507b83ad42607d2f6dadaf55b7b511bdbe]
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=patch;h=695c6dfe7e85006b98c8b746f3fd5f913c94ebff]
Signed-off-by: pgowda
---
.../binutils/binutils-2.38.inc| 3 +
.../binutils/0018-CVE-2022-38128-1.patch | 350 ++
.../binutils/0018-CVE-2022-38128-2.patch | 436 ++
.../binutils/0018-CVE-2022-38128-3.patch | 95
4 files changed, 884 insertions(+)
create mode 100644
meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-1.patch
create mode 100644
meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-2.patch
create mode 100644
meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-3.patch
diff --git a/meta/recipes-devtools/binutils/binutils-2.38.inc
b/meta/recipes-devtools/binutils/binutils-2.38.inc
index fc88d4a79e..8259ec3232 100644
--- a/meta/recipes-devtools/binutils/binutils-2.38.inc
+++ b/meta/recipes-devtools/binutils/binutils-2.38.inc
@@ -39,5 +39,8 @@ SRC_URI = "\
file://0017-CVE-2022-38127-2.patch \
file://0017-CVE-2022-38127-3.patch \
file://0017-CVE-2022-38127-4.patch \
+ file://0018-CVE-2022-38128-1.patch \
+ file://0018-CVE-2022-38128-2.patch \
+ file://0018-CVE-2022-38128-3.patch \
"
S = "${WORKDIR}/git"
diff --git
a/meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-1.patch
b/meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-1.patch
new file mode 100644
index 00..0a490d86b3
--- /dev/null
+++ b/meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-1.patch
@@ -0,0 +1,350 @@
+From f07c08e115e27cddf5a0030dc6332bbee1bd9c6a Mon Sep 17 00:00:00 2001
+From: Alan Modra
+Date: Thu, 21 Jul 2022 08:38:14 +0930
+Subject: [PATCH] binutils/dwarf.c: abbrev caching
+
+I'm inclined to think that abbrev caching is counter-productive. The
+time taken to search the list of abbrevs converted to internal form is
+non-zero, and it's easy to decode the raw abbrevs. It's especially
+silly to cache empty lists of decoded abbrevs (happens with zero
+padding in .debug_abbrev), or abbrevs as they are displayed when there
+is no further use of those abbrevs. This patch stops caching in those
+cases.
+
+ * dwarf.c (record_abbrev_list_for_cu): Add free_list param.
+ Put abbrevs on abbrev_lists here.
+ (new_abbrev_list): Delete function.
+ (process_abbrev_set): Return newly allocated list. Move
+ abbrev base, offset and size checking to..
+ (find_and_process_abbrev_set): ..here, new function. Handle
+ lookup of cached abbrevs here, and calculate start and end
+ for process_abbrev_set. Return free_list if newly alloc'd.
+ (process_debug_info): Consolidate cached list lookup, new list
+ alloc and processing into find_and_process_abbrev_set call.
+ Free list when not cached.
+ (display_debug_abbrev): Similarly.
+
+Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=f07c08e115e27cddf5a0030dc6332bbee1bd9c6a]
+
+Signed-off-by: Pgowda
+---
+ binutils/dwarf.c | 208 +--
+ 1 file changed, 110 insertions(+), 98 deletions(-)
+
+diff --git a/binutils/dwarf.c b/binutils/dwarf.c
+index 267ed3bb382..2fc352f74c5 100644
+--- a/binutils/dwarf.c
b/binutils/dwarf.c
+@@ -882,8 +882,15 @@ static unsigned long next_free_abbrev_m
+ #define ABBREV_MAP_ENTRIES_INCREMENT 8
+
+ static void
+-record_abbrev_list_for_cu (dwarf_vma start, dwarf_vma end, abbrev_list * list)
++record_abbrev_list_for_cu (dwarf_vma start, dwarf_vma end,
++ abbrev_list *list, abbrev_list *free_list)
+ {
++ if (free_list != NULL)
++{
++ list->next = abbrev_lists;
++ abbrev_lists = list;
++}
++
+ if (cu_abbrev_map == NULL)
+ {
+ num_abbrev_map_entries = INITIAL_NUM_ABBREV_MAP_ENTRIES;
+@@ -936,20 +943,6 @@ free_all_abbrevs (void)
+ }
+
+ static abbrev_list *
+-new_abbrev_list (dwarf_vma abbrev_base, dwarf_vma abbrev_offset)
+-{
+- abbrev_list * list = (abbrev_list *) xcalloc (sizeof * list, 1);
+-
+- list->abbrev_base = abbrev_base;
+- list->abbrev_offset = abbrev_offset;
+-
+- list->next = abbrev_lists;
+- abbrev_lists = list;
+-
+- return list;
+-}
+-
+-static abbrev_list *
+ find_abbrev_list_by_abbrev_offset (dwarf_vma abbrev_base,
+ dwarf_vma abbrev_offset)
+ {
+@@ -966,7 +959,7 @@ find_abbrev_list_by_abbrev_offset (dwarf
+ /* Find the abbreviation map for the CU that includes OFFSET.
+OFFSET is an absolute offset from the start of the .debug_info section. */
+ /* FIXME: This function is going to slow down readelf & objdump.
+- Consider using a better
Re: [OE-core] [PATCH] pango: upgrade 1.50.10 -> 1.50.11
This causes ptest failures:
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/4115/steps/12/logs/stdio
'pango': ['pango/test-no-fonts.test']}
On 11/10/2022 16:05:57+0800, wangmy wrote:
> Signed-off-by: Wang Mingyu
> ---
> .../pango/{pango_1.50.10.bb => pango_1.50.11.bb}| 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> rename meta/recipes-graphics/pango/{pango_1.50.10.bb => pango_1.50.11.bb}
> (94%)
>
> diff --git a/meta/recipes-graphics/pango/pango_1.50.10.bb
> b/meta/recipes-graphics/pango/pango_1.50.11.bb
> similarity index 94%
> rename from meta/recipes-graphics/pango/pango_1.50.10.bb
> rename to meta/recipes-graphics/pango/pango_1.50.11.bb
> index 95209889a8..1120e053b8 100644
> --- a/meta/recipes-graphics/pango/pango_1.50.10.bb
> +++ b/meta/recipes-graphics/pango/pango_1.50.11.bb
> @@ -24,7 +24,7 @@ SRC_URI += "file://run-ptest \
> file://0001-Skip-running-test-layout-test.patch \
> "
>
> -SRC_URI[archive.sha256sum] =
> "7e5d2f1e40854d24a9a2c4d093bafe75dcdbeccdf1de43e4437332eabed64966"
> +SRC_URI[archive.sha256sum] =
> "8800f812d89ee61388188703203f3a7878963c22f8695aaf1fa0a1a1428d17ae"
>
> DEPENDS = "glib-2.0 glib-2.0-native fontconfig freetype virtual/libiconv
> cairo harfbuzz fribidi"
>
> --
> 2.25.1
>
>
>
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171683):
https://lists.openembedded.org/g/openembedded-core/message/171683
Mute This Topic: https://lists.openembedded.org/mt/94254215/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] pango: upgrade 1.50.10 -> 1.50.11
On 12/10/2022 16:46:44+, Ross Burton wrote:
> We only have 1.50.9 in oe-core master, please ensure that you sent patches
> based on master, or if they’re based on another staging branch please make
> that clear.
>
this applied fine on master-next because we carry your 1.50.10 upgrade
> Ross
>
> > On 11 Oct 2022, at 09:05, wangmy via lists.openembedded.org
> > wrote:
> >
> > Signed-off-by: Wang Mingyu
> > ---
> > .../pango/{pango_1.50.10.bb => pango_1.50.11.bb}| 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> > rename meta/recipes-graphics/pango/{pango_1.50.10.bb => pango_1.50.11.bb}
> > (94%)
> >
> > diff --git a/meta/recipes-graphics/pango/pango_1.50.10.bb
> > b/meta/recipes-graphics/pango/pango_1.50.11.bb
> > similarity index 94%
> > rename from meta/recipes-graphics/pango/pango_1.50.10.bb
> > rename to meta/recipes-graphics/pango/pango_1.50.11.bb
> > index 95209889a8..1120e053b8 100644
> > --- a/meta/recipes-graphics/pango/pango_1.50.10.bb
> > +++ b/meta/recipes-graphics/pango/pango_1.50.11.bb
> > @@ -24,7 +24,7 @@ SRC_URI += "file://run-ptest \
> > file://0001-Skip-running-test-layout-test.patch \
> > "
> >
> > -SRC_URI[archive.sha256sum] =
> > "7e5d2f1e40854d24a9a2c4d093bafe75dcdbeccdf1de43e4437332eabed64966"
> > +SRC_URI[archive.sha256sum] =
> > "8800f812d89ee61388188703203f3a7878963c22f8695aaf1fa0a1a1428d17ae"
> >
> > DEPENDS = "glib-2.0 glib-2.0-native fontconfig freetype virtual/libiconv
> > cairo harfbuzz fribidi"
> >
> > --
> > 2.25.1
> >
> >
> >
> >
>
>
>
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171682):
https://lists.openembedded.org/g/openembedded-core/message/171682
Mute This Topic: https://lists.openembedded.org/mt/94254215/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
