On Fri, 29 May 2026 at 19:01, Tatrai, Peter via lists.openembedded.org <[email protected]> wrote: > When SDKMACHINE is set to i686 or i586, nativesdk binaries are compiled > as 32-bit. Without -D_TIME_BITS=64 and -D_FILE_OFFSET_BITS=64, stat() > and time-related syscalls use 32-bit types, causing EOVERFLOW on > filesystems with large inode numbers (e.g. container overlay filesystems) > and Y2038 issues.
Hurray! As chance would have it, we have just recently discussed dropping Yocto CI testing for SDKs that run on 32 bit hosts. The trigger for that discussion was that latest qemu can no longer run on such hosts (but it can emulate 32 bit platforms just fine, that is not going away). RP had mentioned that someone has recently submitted a fix, and presumably they have a use case, and that someone is you. So the question: how and why are you using such SDKs? Would you be very upset if Yocto no longer tests them? Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#237770): https://lists.openembedded.org/g/openembedded-core/message/237770 Mute This Topic: https://lists.openembedded.org/mt/119550198/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
