On 22 Oct 2026, at 09:24, Khem Raj via lists.openembedded.org <[email protected]> wrote: > Until then, opt into them for riscv32 musl targets with the > libc_unstable_musl_v1_2_3 cfg, which libc 0.2.189 reads. Earlier > versions are not opted in: 0.2.174 to 0.2.188 read the > RUST_LIBC_UNSTABLE_MUSL_V1_2_3 environment variable instead, but their > riscv32 time64 layouts lack the timespec padding (up to 0.2.182) or > fail to build with duplicate __pad1/__pad2 fields (0.2.183 to 0.2.188), > and older versions have no musl time64 support.
Should we be setting this without a machine override, if it specifies what version of musl the crate should be targeting? Seems wrong that only one architecture will be targeting the correct version of musl. Rss
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#248686): https://lists.openembedded.org/g/openembedded-core/message/248686 Mute This Topic: https://lists.openembedded.org/mt/121880755/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
