It builds glibc source like other glibc recipes do, and so the same problems occur.
Signed-off-by: Alexander Kanavin <[email protected]> --- meta/conf/distro/include/time64.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/conf/distro/include/time64.inc b/meta/conf/distro/include/time64.inc index 2e7278292c6..73adebd39db 100644 --- a/meta/conf/distro/include/time64.inc +++ b/meta/conf/distro/include/time64.inc @@ -10,6 +10,7 @@ TARGET_CC_ARCH:append:x86 = "${@bb.utils.contains('TUNE_FEATURES', 'm32', '${GLI GLIBC_64BIT_TIME_FLAGS:pn-glibc = "" GLIBC_64BIT_TIME_FLAGS:pn-glibc-tests = "" +GLIBC_64BIT_TIME_FLAGS:pn-glibc-testsuite = "" # pipewire-v4l2 explicitly sets _FILE_OFFSET_BITS=32 to get access to # both 32 and 64 bit file APIs. But it does not handle the time side? # Needs further investigation -- 2.30.2
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#180513): https://lists.openembedded.org/g/openembedded-core/message/180513 Mute This Topic: https://lists.openembedded.org/mt/98554682/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
