On Wednesday 11 August 2021 at 18:32:31 +0200, Alexander Kanavin wrote: > On Wed, 11 Aug 2021 at 18:14, Mike Crowe <m...@mcrowe.com> wrote: > > I agree regarding the lack of explanation. However, even if the problem is > > real (which it looks like it is based on > > https://bugs.python.org/issue41710) > > then it wouldn't be expected to cause test failures unless the system clock > > was being warped at inconvenient times during the tests. > > So can we just patch python to use the right glibc function with the right > clock type, and send the patch upstream then? Much better than the > workaround that was merged.
In theory, yes. I've no idea how hard that is though. It probably requires adding build-time detection of whether the new functions are available to avoid breaking other/older target operating systems. Mike.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#154729): https://lists.openembedded.org/g/openembedded-core/message/154729 Mute This Topic: https://lists.openembedded.org/mt/84632397/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
