On Wed, Nov 30 2022, Richard Purdie wrote: > On Wed, 2022-11-30 at 17:56 +0100, Alexandre Belloni wrote: >> On 30/11/2022 16:46:17+0000, Ross Burton wrote: >> > On 30 Nov 2022, at 14:20, Richard Purdie via >> > lists.yoctoproject.org >> > <richard.purdie=linuxfoundation....@lists.yoctoproject.org> wrote: >> > > > > * Could we optionally disable some of the glibc 32 bit function calls >> > > > > to ensure they're not being used? >> > > > >> > > > Could you be more specific here? Would you like to disable some >> > > > syscalls? >> > > >> > > I'm meaning disabling the 32 bit glibc time functions. >> > >> > 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 used to check for 32- >> > bit time_t use. > > That sounds interesting and something we should probably look into for > both issues...
I have a working sanity checker that checks for any glibc functions affected by -D_FILE_OFFSET_BITS=64 or -D_TIME_BITS=64. The INSANE_SKIP functionality needs some more polish but I'd be happy to contribute it. Some libraries use both 32 and 64 bit APIs to glibc and needs exceptions in the checker. I have not run any world builds with this checker, I've focused on the recipes we actually use so far so we could get to a testable system. My biggest worry at the moment is rust, I know to little to know if it is an actual problem and how to fix it. I would like to be part of any "y2038 team" for Yocto. -- Ola x Nilsson
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#174282): https://lists.openembedded.org/g/openembedded-core/message/174282 Mute This Topic: https://lists.openembedded.org/mt/95361986/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
