From: Martin Jansa
* refresh 0001-Revert-Linux-Implement-a-useful-version-of-_startup_.patch
(just different commit SHA in master and 2.35 branch)
* add proposed fixes for build failure with DEBUG_BUILD:
http://errors.yoctoproject.org/Errors/Details/663898/
86_64-oe-linux-gcc -m64 -march=c
Signed-off-by: Khem Raj
Signed-off-by: Martin Jansa
---
v2: Add DEBUG_BUILD fixes
v3: Update SRCREV to latest on 2.36 branch
meta/conf/distro/include/tcmode-default.inc | 2 +-
...2.35.bb => cross-localedef-native_2.36.bb} | 4 +-
meta/recipes-core/glibc/glibc-common.inc | 2 +-
...bc
These defines are needed to enable some GNU APIs and large file support
is default in OE anyway
Signed-off-by: Khem Raj
---
meta/recipes-devtools/perl/perl_5.36.0.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/perl/perl_5.36.0.bb
b/meta/recipes-devtools/perl/perl
There are latent issues in function detection which were succeeding due
to compiler being lenient, but this is fast changing e.g. clang-15 has
turned the -Wimplicit-function-declaration into error which ends up
failing these tests and rightly so. Therefore try to improve the tests
to have proper pr
On 8/8/22 01:35, Martin Jansa wrote:
Hi Mark,
Does this still work for you?
Yes, it still works for me. Without that patch, it fails with
"DEBUG_BUILD = '1'" in local.conf for qemux86-64.
With this change applied (now in master), mesa fails here with:
http://errors.yoctoproject.org/Erro
Source: https://gitlab.gnome.org/GNOME/gdk-pixbuf
MR: 120380
Type: Security Fix
Disposition: Backport from
https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/commit/5398f04d772f7f8baf5265715696ed88db0f0512
ChangeID: d8a843bcf97268ee4f0c6870f1339790a9a908e5
Description:
CVE-2021-46829 gdk-pixbuf:
Source: https://gitlab.gnome.org/GNOME/gdk-pixbuf
MR: 120379
Type: Security Fix
Disposition: Backport from
https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/commit/5398f04d772f7f8baf5265715696ed88db0f0512
ChangeID: 37f962b51bdb0c522b2a991c549fd29e3d2e58d7
Description:
CVE-2021-46829 gdk-pixbuf:
On Mon, Aug 8, 2022 at 3:38 AM Richard Purdie
wrote:
>
> Hi Bruce,
>
> On Thu, 2022-08-04 at 18:57 -0400, bruce.ashfi...@gmail.com wrote:
> > As I mentioned earlier today, I've built and booted the 5.19 kernel
> > on all architectures, have run core-iamge-kernel-dev, core-image-sato
> > and valida
From: Bruce Ashfield
Integrating the following commit(s) to linux-yocto/5.19:
e0e977e1b098 init/Kconfig: fix CC_HAS_ASM_GOTO_TIED_OUTPUT test with dash
Signed-off-by: Bruce Ashfield
---
.../linux/linux-yocto-rt_5.19.bb | 2 +-
.../linux/linux-yocto-tiny_5.19.bb|
From: Bruce Ashfield
Integrating the following commit(s) to linux-yocto/.:
00e2494f7e4 cfg/x32: rename X86_X32 X86_X32_ABI
Signed-off-by: Bruce Ashfield
---
Apply this on top of my previous 5.19 patches to get the x32 tune
booting again.
Bruce
meta/recipes-kernel/linux/linux-yocto-rt_5
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
4fd9cb57a3f5 Linux 5.10.135
4bfc9dc60873 selftests: bpf: Don't run sk_lookup in verifier tests
6d3fad2b44eb bpf: Add PROG_TEST_RUN support for sk_lookup programs
6aad811b37ee b
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
77ba2b9b46f8 Linux 5.4.208
ca5762c5896e x86: drop bogus "cc" clobber from __try_cmpxchg_user_asm()
f88d8c188229 net: usb: ax88179_178a needs FLAG_SEND_ZLP
f7785092cb7f tty: use
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
8d8935e76f6f Linux 5.4.209
0b0088e47587 scsi: core: Fix race between handling STS_RESOURCE and
completion
85fe8623f061 mt7601u: add USB device ID for some versions of XiaoDu WiFi
From: Bruce Ashfield
Integrating the following commit(s) to linux-yocto/5.15:
efe20512212b init/Kconfig: fix CC_HAS_ASM_GOTO_TIED_OUTPUT test with dash
Fixes: 1aa0e8b144b6 ("Kconfig: Add option for asm goto w/ tied outputs to
workaround clang-13 bug")
Signed-off-by: Alexandre Belloni
Sign
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
d676d6149a2f Linux 5.15.59
f0e42e43795d x86/bugs: Do not enable IBPB at firmware entry when IBPB is
not available
d10e819d13f7 locking/rwsem: Allow slowpath writer to ignore hando
The full path of patch may contain '/meta/' but not in oe-core, skip
patches by checking it starts with oe-core full path or not.
Signed-off-by: Yang Xu
---
meta/classes/insane.bbclass | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/classes/insane.bbclass b/meta/classe
All,
Below is the list as of top 37 bug owners as of the end of WW32 of who have
open medium or higher bugs and enhancements against YP 4.1. There are 57
possible work days left until the final release candidates for YP 4.1 needs
to be released.
Who
Count
michael.opdenac...@bootlin.com
36
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
On Mon, Aug 8, 2022 at 11:28 PM Martin Jansa via lists.openembedded.org
wrote:
> * but it still won't work well on hosts without libxml2, make
> sure to use pre-generated testapi.c in do_compile_ptest
>
> * this is reproducible with SOURCE_DATE_EPOCH set to 0 which
> e.g. meta-updater still s
* but it still won't work well on hosts without libxml2, make
sure to use pre-generated testapi.c in do_compile_ptest
* this is reproducible with SOURCE_DATE_EPOCH set to 0 which
e.g. meta-updater still sets by default for DISTROs which
use it :(, see https://github.com/uptane/meta-updater/p
On Mon, Aug 8, 2022 at 2:34 PM Alexandre Belloni
wrote:
>
> Hi,
>
> On 08/08/2022 08:19:51-0500, Joshua Watt wrote:
> > The regex to match github or gitlab was unnecessarily shortened, which
> > prevented them from showing up when grepping.
> >
>
> This doesn't apply since we have "classes/sanity:
Hi,
On 08/08/2022 08:19:51-0500, Joshua Watt wrote:
> The regex to match github or gitlab was unnecessarily shortened, which
> prevented them from showing up when grepping.
>
This doesn't apply since we have "classes/sanity: Add comment about
github & gitlab archives" in master. I guess this was
On Mon, 8 Aug 2022 at 15:08, Richard Purdie
wrote:
> > > Using modifier ff
> > > failed to set mode: Invalid argument
> > >
> >
> > I did do graphical tests on x86-64, and didn't see any issues. I'll
> > have another look.
>
> This is virgl GL passthrough in qemu so not a commonly test
Signed-off-by: Alexander Kanavin
---
...common.c-do-not-use-invalid-modifier.patch | 27 +++
meta/recipes-graphics/kmscube/kmscube_git.bb | 6 +++--
2 files changed, 31 insertions(+), 2 deletions(-)
create mode 100644
meta/recipes-graphics/kmscube/kmscube/0001-drm-common.c-do-
On Mon, Aug 8, 2022 at 11:07 AM Bruce Ashfield wrote:
>
> On Mon, Aug 8, 2022 at 12:14 PM Khem Raj wrote:
> >
> > Hi Bruce
> >
> > 5.19 has issues with zfs see [1], it seem zfs is not yet working well
> > with 5.19 I see this message
> >
> > | checking whether blk_queue_discard() is available...
On Mon, Aug 8, 2022 at 12:14 PM Khem Raj wrote:
>
> Hi Bruce
>
> 5.19 has issues with zfs see [1], it seem zfs is not yet working well
> with 5.19 I see this message
>
> | checking whether blk_queue_discard() is available... configure: error:
> | *** None of the expected "blk_queue_discard"
On 8/7/22 11:42 PM, Alexander Kanavin wrote:
Drop dont-use-plane-add-prop.patch as issue is fixed elsewhere
(see the link in the patch).
I think this needs some verification if this implied patch really fixes
the problem. I will see if I can test it out in coming week.
Signed-off-by: Ale
On Mon, 8 Aug 2022 at 19:07, Khem Raj wrote:
> > Drop handle-read-only-files.patch: read only files should
> > be handled by making them writeable explicitly. See
> > the upstream discussion:
> > https://github.com/NixOS/patchelf/pull/89
>
> I agree with this. However, we have been carrying this f
On 8/8/22 10:21 AM, Bruce Ashfield wrote:
On Mon, Aug 8, 2022 at 1:11 PM Bruce Ashfield via
lists.openembedded.org
wrote:
On Mon, Aug 8, 2022 at 12:14 PM Khem Raj wrote:
Hi Bruce
5.19 has issues with zfs see [1], it seem zfs is not yet working well
with 5.19 I see this message
Indeed!
On Mon, 8 Aug 2022 at 18:59, Khem Raj wrote:
> > -LIC_FILES_CHKSUM =
> > "file://Copyright.txt;md5=f2102a52df7aa592cf072180e7ebc8c7 \
> > +LIC_FILES_CHKSUM =
> > "file://Copyright.txt;md5=45025187a129339459b6f1a24f7fac6e \
>
> Reason for this change would be good to document in commit msg.
Than
This is the upstream issue. This patch can be dropped I guess.
https://github.com/mkj/dropbear/issues/186
Alex
On Mon, 8 Aug 2022 at 18:54, Khem Raj wrote:
>
> it seems to back up again. However, if its a site flakiness issue
> perhaps finding a good mirror might be nice.
>
> On 8/7/22 11:41 PM
On Mon, Aug 8, 2022 at 1:11 PM Bruce Ashfield via
lists.openembedded.org
wrote:
>
> On Mon, Aug 8, 2022 at 12:14 PM Khem Raj wrote:
> >
> > Hi Bruce
> >
> > 5.19 has issues with zfs see [1], it seem zfs is not yet working well
> > with 5.19 I see this message
> >
>
> Indeed! It is pretty clear ab
On Mon, Aug 8, 2022 at 12:14 PM Khem Raj wrote:
>
> Hi Bruce
>
> 5.19 has issues with zfs see [1], it seem zfs is not yet working well
> with 5.19 I see this message
>
Indeed! It is pretty clear about that.
I can try and uprev of the package, or did you have one already started ?
Bruce
> | che
On 8/7/22 11:42 PM, Alexander Kanavin wrote:
Signed-off-by: Alexander Kanavin
---
...ure-due-to-libc-using-libc-functions.patch | 42 +++
.../{libwpe_1.12.0.bb => libwpe_1.12.2.bb}| 6 ++-
2 files changed, 46 insertions(+), 2 deletions(-)
create mode 100644
meta/rec
On 8/7/22 11:42 PM, Alexander Kanavin wrote:
Signed-off-by: Alexander Kanavin
---
...0001-fix-signedness-of-char-in-tests.patch | 27 +++
.../{harfbuzz_4.4.1.bb => harfbuzz_5.1.0.bb} | 6 +++--
2 files changed, 31 insertions(+), 2 deletions(-)
create mode 100644
meta/r
On 8/7/22 11:42 PM, Alexander Kanavin wrote:
Drop handle-read-only-files.patch: read only files should
be handled by making them writeable explicitly. See
the upstream discussion:
https://github.com/NixOS/patchelf/pull/89
I agree with this. However, we have been carrying this for a while and
On 8/7/22 11:41 PM, Alexander Kanavin wrote:
Signed-off-by: Alexander Kanavin
---
.../cmake/{cmake-native_3.23.2.bb => cmake-native_3.24.0.bb} | 0
meta/recipes-devtools/cmake/cmake.inc | 4 ++--
.../cmake/{cmake_3.23.2.bb => cmake_3.24.0.bb}| 0
3
it seems to back up again. However, if its a site flakiness issue
perhaps finding a good mirror might be nice.
On 8/7/22 11:41 PM, Alexander Kanavin wrote:
Signed-off-by: Alexander Kanavin
---
meta/recipes-core/dropbear/dropbear_2022.82.bb | 4 +++-
1 file changed, 3 insertions(+), 1 deleti
Thanks I have taken in all your glibc patches into my testing branch here
https://github.com/YoeDistro/openembedded-core/commits/yoe/mut
On 8/8/22 8:54 AM, Martin Jansa wrote:
From: Khem Raj
Signed-off-by: Khem Raj
Signed-off-by: Martin Jansa
---
v2: rebased for current master which has
Hi Bruce
5.19 has issues with zfs see [1], it seem zfs is not yet working well
with 5.19 I see this message
| checking whether blk_queue_discard() is available... configure: error:
| *** None of the expected "blk_queue_discard" interfaces were detected.
| *** This may be because your
* add only necessary definitions from linux/fs.h, because including
whole file causes conflicts with sys/mount.h since glibc-2.36:
http://errors.yoctoproject.org/Errors/Details/664535/
https://sourceware.org/glibc/wiki/Release/2.36#Usage_of_.3Clinux.2Fmount.h.3E_and_.3Csys.2Fmount.h.3E
Sig
* refresh 0001-Revert-Linux-Implement-a-useful-version-of-_startup_.patch
(just different commit SHA in master and 2.35 branch)
* add proposed fixes for build failure with DEBUG_BUILD:
http://errors.yoctoproject.org/Errors/Details/663898/
86_64-oe-linux-gcc -m64 -march=core2 -mtune=core2 -ms
From: Khem Raj
Signed-off-by: Khem Raj
Signed-off-by: Martin Jansa
---
v2: rebased for current master which has one more patch in SRC_URI
and there was another SRCREV bump from 2.35 causing conflicts
bumped SRCREV to match glibc-2.36 tag
meta/conf/distro/include/tcmode-default.inc
On Mon, 2022-08-08 at 15:19 +0200, Luca Ceresoli via
lists.openembedded.org wrote:
> Hi Thomas,
>
> On Mon, 8 Aug 2022 08:39:59 +
> "Roos, Thomas" wrote:
>
> > Hi Luca,
> > thank you for this - will update my patch and try with the sendemail.from
> > parameter.
> > The correct procedure wil
cargo ends up running target-rust-ccld with LD_LIBRARY_PATH set to libdir but
not
base_libdir which breaks the SDK. You see errors like:
/bin/sh: error while loading shared libraries: libncurses.so.5: cannot open
shared object file: No such file or directory
On such a system, this would fail:
utils already has a create_wrapper function which I tried to use from cargo
and got unexpected results. Rename the rust function to avoid this conflict
of named.
Signed-off-by: Richard Purdie
---
meta/classes/rust-common.bbclass | 18 +-
1 file changed, 9 insertions(+), 9 deletio
The current test assumes the kernel size leaves a certain amount of whitespace
in the output. Improve this constraint so a slightly larger kernel doesn't fail
the test.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/selftest/cases/wic.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
di
The following changes since commit 3564ce3d9b2030dd420362c66147bd327090915c:
initscripts: run umountnfs as a KILL script (2022-07-28 05:32:25 -1000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/kirkstone-next
http://cgit.openembedded.
Hi Joshua,
On Mon, 8 Aug 2022 08:19:51 -0500
Joshua Watt wrote:
> The regex to match github or gitlab was unnecessarily shortened, which
> prevented them from showing up when grepping.
>
> Signed-off-by: Joshua Watt
Thank you!
Reviewed-by: Luca Ceresoli
--
Luca Ceresoli, Bootlin
Embedded
On Mon, 8 Aug 2022 at 15:12, Bruce Ashfield wrote:
> > This is virgl GL passthrough in qemu so not a commonly tested thing,
> > you'd need to run the selftest. I'm hoping AlexK has some ideas on this
> > one.
I'm running a build now, will report.
> > The kernel didn't remove x32 did it? That wou
Hi Thomas,
On Mon, 8 Aug 2022 08:39:59 +
"Roos, Thomas" wrote:
> Hi Luca,
> thank you for this - will update my patch and try with the sendemail.from
> parameter.
> The correct procedure will be creating a v3 patch and send as new again?
The correct thing would be to configure your git sen
The regex to match github or gitlab was unnecessarily shortened, which
prevented them from showing up when grepping.
Signed-off-by: Joshua Watt
---
meta/classes/insane.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bb
On Mon, Aug 8, 2022 at 9:08 AM Richard Purdie
wrote:
>
> On Mon, 2022-08-08 at 09:01 -0400, Bruce Ashfield wrote:
> > On Mon, Aug 8, 2022 at 3:38 AM Richard Purdie
> > wrote:
> > >
> > > Hi Bruce,
> > >
> > > On Thu, 2022-08-04 at 18:57 -0400, bruce.ashfi...@gmail.com wrote:
> > > > As I mentione
On Mon, 2022-08-08 at 09:01 -0400, Bruce Ashfield wrote:
> On Mon, Aug 8, 2022 at 3:38 AM Richard Purdie
> wrote:
> >
> > Hi Bruce,
> >
> > On Thu, 2022-08-04 at 18:57 -0400, bruce.ashfi...@gmail.com wrote:
> > > As I mentioned earlier today, I've built and booted the 5.19 kernel
> > > on all ar
On Mon, Aug 8, 2022 at 3:38 AM Richard Purdie
wrote:
>
> Hi Bruce,
>
> On Thu, 2022-08-04 at 18:57 -0400, bruce.ashfi...@gmail.com wrote:
> > As I mentioned earlier today, I've built and booted the 5.19 kernel
> > on all architectures, have run core-iamge-kernel-dev, core-image-sato
> > and valida
Hi Awais,
On 8/8/22 12:32, Awais Belal wrote:
The KERNEL_DEVICETREE and related variables could potentially have a device
tree listed multiple times and this works okay for most scenarios. However,
when we create FIT entries for these we get duplicate nodes and uboot-mkimage
fails with
fit-imag
The KERNEL_DEVICETREE and related variables could potentially have a device
tree listed multiple times and this works okay for most scenarios. However,
when we create FIT entries for these we get duplicate nodes and uboot-mkimage
fails with
fit-image-initramfs-image.its:219.58-229.19: ERROR (dupli
On Mon, Jul 18, 2022 at 04:12:25PM +, Ross Burton wrote:
> This still seems overkill. You can build minizip from inside the zlib recipe
> by fixing the minizip Makefile (fix posted to
> https://github.com/madler/zlib/pull/681) and then adding one line to
> do_compile:
>
> oe_runmake -C
On Mon, 2022-08-08 at 11:35 +0200, Alexander Kanavin wrote:
> On Mon, 8 Aug 2022 at 10:23, Alexander Kanavin via
> lists.openembedded.org
> wrote:
> > Usage of patchelf in uninative seems to be contained in
> > uninative_changeinterp, which can be tweaked
> > to handle r/o files before invoking pa
On Mon, 8 Aug 2022 at 10:23, Alexander Kanavin via
lists.openembedded.org
wrote:
> Usage of patchelf in uninative seems to be contained in
> uninative_changeinterp, which can be tweaked
> to handle r/o files before invoking patchelf. Was it that all usages
> of it need to be tweaked similarly?
Ok
From: Luca Ceresoli
The 'name' option here is not needed as there is only one file in SRC_URI.
The layer index lists no bbappend for this recipe, thus this is unlikely
useful for bbappends.
Signed-off-by: Luca Ceresoli
---
meta/recipes-extended/libmnl/libmnl_1.0.5.bb | 4 ++--
1 file changed,
The 2nd fix was updated in upstream:
https://sourceware.org/pipermail/libc-alpha/2022-August/141290.html (1st is
the same https://sourceware.org/pipermail/libc-alpha/2022-August/141289.html
)
will send updated version, once the final fix is merged in master branch
(or SRCREV update once it gets mer
On Mon, 8 Aug 2022 at 09:43, Richard Purdie
wrote:
>
> On Mon, 2022-08-08 at 08:38 +0200, Alexander Kanavin wrote:
> > Drop handle-read-only-files.patch: read only files should
> > be handled by making them writeable explicitly. See
> > the upstream discussion:
> > https://github.com/NixOS/patchel
I wasn't testing this with musl, so it is probably this one.
Khem, can you have a look if you have musl build ready?
On Mon, Aug 8, 2022 at 9:40 AM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Sat, 2022-08-06 at 14:09 +0200, Martin Jansa wrote:
> > Signed-off-by: Martin Jansa
On Mon, 2022-08-08 at 08:38 +0200, Alexander Kanavin wrote:
> Drop handle-read-only-files.patch: read only files should
> be handled by making them writeable explicitly. See
> the upstream discussion:
> https://github.com/NixOS/patchelf/pull/89
>
> Signed-off-by: Alexander Kanavin
> ---
> .../pa
On Sat, 2022-08-06 at 14:09 +0200, Martin Jansa wrote:
> Signed-off-by: Martin Jansa
> ---
> ...binstaller-Fix-build-with-glibc-2.36.patch | 53 +++
> .../syslinux/syslinux_6.04-pre2.bb| 1 +
> 2 files changed, 54 insertions(+)
> create mode 100644
> meta/recipes-de
Hi Bruce,
On Thu, 2022-08-04 at 18:57 -0400, bruce.ashfi...@gmail.com wrote:
> As I mentioned earlier today, I've built and booted the 5.19 kernel
> on all architectures, have run core-iamge-kernel-dev, core-image-sato
> and validated musl.
>
> At this point, we need wider coverage to scare out t
Hello Thomas,
On Thu, 4 Aug 2022 15:49:20 +0200
"Thomas Roos via lists.openembedded.org"
wrote:
^^^
As you can see above, your sender address is getting mangled. This is
not your fault, it is done by DMARC for anti-p
68 matches
Mail list logo
