On Thu, 27 Apr 2023 at 09:04, Khem Raj <[email protected]> wrote: > While this might be good, does this fix anything specific for enabling > 64bit time_t.
Yes; please see the link. > This change means we are implying that yocto wont work with kernels > older than 5.15 and maybe SDK would also need > 5.15 on SDK hosts and similar need for build hosts might be imposed > too. Perhaps it would be good to do some due diligence before > applying this. I was waiting for someone to say something like this. :) SDKs are not affected. There's a separate setting for them, SDK_OLDEST_KERNEL which stays as it was, at 3.2.0. Kernels versions on build hosts don't have a setting or check, and that never causes trouble. The focus here is specifically on removing all uses of 32 bit time on 32 bit targets, and as a bonus, enabling other optimized paths in glibc that are only supported with newer kernels. The implication is not that yocto won't work with < 5.15, it's that it is not tested with such kernels. Which is fair enough, isn't it? If someone does need an older kernel (and yes, I'm waiting for the 'outdated vendor kernels' squad to come out and lynch me for this change), they can reset OLDEST_KERNEL locally, which would confirm that they should be doing their own testing. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#180471): https://lists.openembedded.org/g/openembedded-core/message/180471 Mute This Topic: https://lists.openembedded.org/mt/98511406/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
