On Tue, 27 Jun 2023 at 17:33, Richard Purdie <[email protected]> wrote:
> > +# Additionally cargo_common class (i.e. everything written in rust) > > +# gets the same INSANE_SKIP setting. The culprit is the libc crate, > > +# which as of Jun 2023 calls directly into 32 bit time functions in glibc, > > +# bypassing all of glibc provisions to choose the right Y2038-safe > > functions. As > > +# rust components statically link with that crate, pretty much everything > > +# is affected, and so there's no point trying to have recipe-specific > > +# INSANE_SKIP entries. > > +# > > +# Upstream ticket and PR: > > +# https://github.com/rust-lang/libc/issues/3223 > > +# https://github.com/rust-lang/libc/pull/3175 > > This doesn't feel quite right. I think this comment should be in the > cargo class with a comment in time64.inc to see the cargo class for > rust specific issues? Sure, I can invert this. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#183493): https://lists.openembedded.org/g/openembedded-core/message/183493 Mute This Topic: https://lists.openembedded.org/mt/99811046/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
