From: Kai Kang
It needs some functions from libatomic on 32-bit powerpc too:
| libavformat/libavformat.so: undefined reference to `__atomic_fetch_sub_8'
Signed-off-by: Kai Kang
---
v2:
* correct the typo of the machine in commit log
meta/recipes-multimedia/ffmpeg/ffmpeg_4.4.bb | 1 +
1 file
On 6/15/21 2:22 PM, Andre McCurdy wrote:
On Mon, Jun 14, 2021 at 8:54 PM kai wrote:
From: Kai Kang
It needs some functions from libatomic on 32-bit mips too:
| libavformat/libavformat.so: undefined reference to `__atomic_fetch_sub_8'
Signed-off-by: Kai Kang
---
meta/recipes-multimedia/ff
On Mon, Jun 14, 2021 at 8:54 PM kai wrote:
>
> From: Kai Kang
>
> It needs some functions from libatomic on 32-bit mips too:
>
> | libavformat/libavformat.so: undefined reference to `__atomic_fetch_sub_8'
>
> Signed-off-by: Kai Kang
> ---
> meta/recipes-multimedia/ffmpeg/ffmpeg_4.4.bb | 1 +
>
Hi Steve/Akuster,
I think as i have sent this patch to: openembedded-core@lists.openembedded.org
that's why this tag [OE-core] is automatically added as i have not added it .
Please do not consider this patch i will send a new one to:
openembedded-de...@lists.openembedded.org
And as per NVD it
From: Kai Kang
It needs some functions from libatomic on 32-bit mips too:
| libavformat/libavformat.so: undefined reference to `__atomic_fetch_sub_8'
Signed-off-by: Kai Kang
---
meta/recipes-multimedia/ffmpeg/ffmpeg_4.4.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-multi
I used devtool upgrade util-linux and generated the directory of util-linux
under the build directory.
However, because it’s failed to apply the patch, it only modified
SRC_URI[sha256sum] in the final recipe.
Therefore, when I encounter OSS that cannot be automatically updated, I modify
the patc
All,
The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Newc
This ensures the glibc based binaries can find it in right place
Signed-off-by: Khem Raj
---
meta/recipes-core/musl/gcompat_git.bb | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/musl/gcompat_git.bb
b/meta/recipes-core/musl/gcompat_git.bb
in
Signed-off-by: Khem Raj
---
meta/classes/linuxloader.bbclass | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/classes/linuxloader.bbclass b/meta/classes/linuxloader.bbclass
index 30925ac87d..3ded1fc786 100644
--- a/meta/classes/linuxloader.bbclass
+++ b/meta/classes/linuxloader.bbclass
Version 1.1.2 - This is a bug fix release, correcting a regression [1]
introduced by and
improving the checks from the fix for CVE-2021-31535.
[1] https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/133
Alan Coopersmith (1):
libX11 1.7.2
Matthieu Herrb (2):
include always, not if
Summary for 1.10.1 libpcap release
Packet filtering:
Fix "type XXX subtype YYY" giving a parse error
Source code:
Add PCAP_AVAILABLE_1_11.
Building and testing:
Rename struct bpf_aux_data to avoid NetBSD compile errors
Squelch some compiler warnings
Squelch some Bison warn
Changes:
* Bump inputproto to 2.3.99.2
* specs: Fix type of GESTURECLASS num_touches member
* specs: Fix type of TOUCHCLASS num_touches member
* Bump inputproto to 2.3.99.1
* specs: Specify XI 2.4 as unreleased
Signed-off-by: Andreas Müller
---
.../{xorgproto_2021.4.99.1.bb => xorgproto_2021.4.9
Changes:
build:
* Fix up the build to actually build all library objects with libtool
consistently, also ensuring no pointless static archives for output modules.
* Adapted things to autoconf 2.71, requiring 2.69 now (the latter tested on
Debian, with their patches).
* Improved config
With 1.7.2 it is not required any and although they mention glibc explicitly,
_GNU_SOURCE is set in config.h for musl either.
Signed-off-by: Andreas Müller
---
meta/recipes-graphics/xorg-lib/libx11_1.7.2.bb | 3 ---
1 file changed, 3 deletions(-)
diff --git a/meta/recipes-graphics/xorg-lib/libx
Fixes runtime problems with qemu-user
Fatal glibc error: CPU lacks float128 support (POWER 9 or later required)
Signed-off-by: Khem Raj
---
meta/recipes-devtools/qemu/qemu.inc | 1 +
...nux-user-Tag-vsx-with-ieee128-fpbits.patch | 35 +++
2 files changed, 36 insertions
On Mon, Jun 14, 2021 at 5:45 AM Armin Kuster wrote:
>
>
>
> On 6/14/21 3:46 AM, RAHUL taya wrote:
> > As per below reference links this CVE issue seems to be minor and
> > harmless and as per upstream this is not a real issue in practice.
> >
> > And as per red hat this issue is marked as low seve
This is now fixed in gcc properly, and the patches are backported into
gcc11 branch which OE updated to recently.
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=645bfc161987a12395869728b63ed01084d23c00
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=f1d012911bd103e9701ed378f32928a3cbcf028a
This reve
Signed-off-by: Sakib Sajal
---
scripts/oe-time-dd-test.sh | 3 +++
1 file changed, 3 insertions(+)
diff --git a/scripts/oe-time-dd-test.sh b/scripts/oe-time-dd-test.sh
index 46b218b76a..103eee5f65 100755
--- a/scripts/oe-time-dd-test.sh
+++ b/scripts/oe-time-dd-test.sh
@@ -24,6 +24,9 @@ uptime
Hi Alex,
On 6/14/21 3:17 PM, Alexander Kanavin wrote:
> That would be very useful, but you should check if the entire
> nomenclature of UPSTREAM_CHECK_* variables is documented as well
> (_COMMITS, _REGEX, _URI, _GITTAGREGEX).
Great, many thanks for the advise!
I filed a bug to keep track of thi
On 6/14/21 3:46 AM, RAHUL taya wrote:
> As per below reference links this CVE issue seems to be minor and
> harmless and as per upstream this is not a real issue in practice.
>
> And as per red hat this issue is marked as low severity.
>
> 1. https://bugzilla.suse.com/show_bug.cgi?id=CVE-2015-523
That would be very useful, but you should check if the entire nomenclature
of UPSTREAM_CHECK_* variables is documented as well
(_COMMITS, _REGEX, _URI, _GITTAGREGEX).
Alex
On Mon, 14 Jun 2021 at 15:12, Michael Opdenacker <
michael.opdenac...@bootlin.com> wrote:
> Hi Khem
>
> On 6/13/21 12:10 AM,
Hi Khem
On 6/13/21 12:10 AM, Khem Raj wrote:
> Signed-off-by: Khem Raj
> ---
> meta/recipes-core/musl/musl_git.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-core/musl/musl_git.bb
> b/meta/recipes-core/musl/musl_git.bb
> index 6569d1b37b..bd9d5f1d4b 100644
> --- a/me
CVE-2016-9312 is only for windows.
Signed-off-by: Sekine Shigeki
---
meta-networking/recipes-support/ntp/ntp_4.2.8p15.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta-networking/recipes-support/ntp/ntp_4.2.8p15.bb
b/meta-networking/recipes-support/ntp/ntp_4.2.8p15.bb
index 7e168825
On Fri, 4 Jun 2021 at 00:55, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Thu, 2021-06-03 at 15:13 +0800, wangmy wrote:
> > avoid_parallel_tests.patch
> > Automake-use-EXTRA_LTLIBRARIES-instead-of-noinst_LTL.patch
> > removed since they are included in 2.37
> >
> > Signed-off-b
Hi Rahul,
Looks good to me.
Thanks & Regards,
Purushottam
From: Rahul
Sent: Monday, June 14, 2021 4:45 PM
To: openembedded-core@lists.openembedded.org
; raj.k...@gmail.com
Cc: Nisha Parrakat ; Purushottam Choudhary
; Rahul Taya
Subject: [meta-oe][dunfell][PA
On Sun, 13 Jun 2021 at 15:04, Steve Sakoman wrote:
> CVE-2020-27661: qemu:qemu-native:qemu-system-native
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-27661 *
Fixed in 5.2, CPE updated.
> CVE-2020-35505: qemu:qemu-native:qemu-system-native
> https://web.nvd.nist.gov/view/vuln/det
As per below reference links this CVE issue seems to be minor and
harmless and as per upstream this is not a real issue in practice.
And as per red hat this issue is marked as low severity.
1. https://bugzilla.suse.com/show_bug.cgi?id=CVE-2015-5237
2. https://security-tracker.debian.org/tracker/C
Fix a slew of CVEs (CVE-2021-3544, CVE-2021-3545, CVE-2021-3546) by
backporting the relevant patches from qemu's git.
Signed-off-by: Ross Burton
---
meta/recipes-devtools/qemu/qemu.inc | 7 +++
...ix-memory-disclosure-in-virgl_cmd_ge.patch | 43 ++
...ix-resource-leak-in-v
This patch isn't yet upstream but it has been submitted and other distros
are shipping it.
Signed-off-by: Ross Burton
---
meta/recipes-connectivity/avahi/avahi_0.8.bb | 1 +
.../avahi/files/handle-hup.patch | 41 +++
2 files changed, 42 insertions(+)
create mode 1
As per below reference links this CVE issue seems to be minor and
harmless and as per upstream this is not a real issue in practice.
And as per red hat this issue is marked as low severity.
1. https://bugzilla.suse.com/show_bug.cgi?id=CVE-2015-5237
2. https://security-tracker.debian.org/tracker/C
On Sun, 13 Jun 2021 at 15:04, Steve Sakoman wrote:
> CVE-2020-17541: libjpeg-turbo:libjpeg-turbo-native
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-17541 *
Bad CPE, send a change request.
> CVE-2021-3468: avahi
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3468 *
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152924):
https://lists.openembedded.org/g/openembedded-core/message/152924
Mute This Topic: https://lists.openembedded.org/mt/83526830/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
32 matches
Mail list logo
