Your email prompted me to check my own software (Dropbear) and it showed a few y2038 issues to fix. Those bugs wouldn't be noticed from a quick test - it "only" prevented auth and idle timeouts from o

Some time ago I filed https://bugzilla.yoctoproject.org/show_bug.cgi?id=6803 as Debian has a nice sanity check where it warns if non-LFS glibc functions are used. I imagine the same logic could be use

Hello fellow OpenEmbeddeders! Less than 24 hours until we kick off the OpenEmbedded Developers virtual Meeting 2022.11! For more details, please see https://www.openembedded.org/wiki/OEDvM_2022.11 You

On Tue, 29 Nov 2022 at 16:45, Stephen Jolley <sjolley.yp.pm@...> wrote: > We’d welcome a proposal/series on how to move forward with the Y2038 work for 32 bit platforms. I have the following proposal:

Hi Alexander, Please find a few comments: 1. There is already provided meta-y2038 [1] to test if 32 bit systems correctly support Y2038 problem. It uses qemu machines from OE/Yocto 2. There are ptest

Hi Richard, Y2038 ptests maybe? Here is the list of integrated tests to ptests: https://github.com/lmajewski/y2038-tests Could you be more specific here? Would you like to disable some syscalls? Could

lists.openembedded.org wrote: What is the potential issue with builtools? To be clear, we don't run ptests on 32 bit targets, only on qemux86-64 and qemuarm64 where we have KVM available. We do run im

I ran a-full with "-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" last week, it didn't go too well gcc-sanitizer and pulseaudio being the main offenders but buildtools needs to be investigated. The main issu

Hi, I've a few things I've been pondering for a while and given the summit and OEDVM this week, I thought I'd sent out this email and some RFC patches. Export variable flag (and unexport/network) ----

Users, contributors, members! [1] It is about time again to gather - in virtual form - for some hours of knowledge exchange, discussion, and designing the future of OpenEmbedded. The OpenEmbedded Deve

I thought I'd quickly write down some notes on the relocatable binary "problem" we have. We have a need to be able to run our binaries with a different dynamic loader in a few cases which basically co

I'm starting a new thread/discussion on this with a new perspective. I did a little research myself on how these files are being used. My conclusion is that templateconf.cfg isn't really used by much

Hi all, I thought the agreement was to stop promoting meta-gplv2? Still I find it listed here - it somehow implies that this is still officially support, which everyone agreed it isn't Can this be rem

Dear all, (cross-posting to oe-core and *-architecture) In the last months, we have worked in Oniro on using the create-spdx class for both IP compliance and security. During this work, Alberto Pianon

Hi Joshua, nice to meet you! I'm new to this list, and I've always approached Yocto just from the "IP compliance side", so I may miss important pieces of information. That is why Marta encouraged me a

I was asked about getting official support for the TOOLCHAIN variable in core. This is obviously late in the release cycle and after a bit of thought, the answer is no. I wanted to document why since

Sharing a copy of this to openembedded-architecture. Cheers, Richard

On Thu, 18 Aug 2022 at 11:27, Richard Purdie <richard.purdie@...> wrote: > The intent is the user could add something like: > > require conf/yocto-autobuilder/x32.inc > > or > > require conf/yocto-aut

lists.openembedded.org wrote: I've gone ahead and sent some patches for this for OE-Core and BitBake. There is more work to do so if anyone has a few minutes and wants to clean up a few more file head

Hi all, Today I’m excited to publish a tool I’ve been developing internally for about a year now. It is called ‘yb’, and you can think of it like a cross between kas, Google’s repo, and myrepos (mr).