On Fri, Oct 21, 2022 at 7:58 PM Alexander Kanavin <[email protected]> wrote:
> > > On Fri 21. Oct 2022 at 23.49, Khem Raj <[email protected]> wrote: > >> On Fri, Oct 21, 2022 at 2:01 PM Alexander Kanavin >> <[email protected]> wrote: >> > >> > On Fri, 21 Oct 2022 at 22:05, Khem Raj <[email protected]> wrote: >> > > Update the arch part of tuple to consider OE's names >> > > for riscv32 >> > >> > > +--- a/vendor/crossbeam-utils-0.8.8/no_atomic.rs >> > > ++++ b/vendor/crossbeam-utils-0.8.8/no_atomic.rs >> > > +@@ -49,6 +49,8 @@ const NO_ATOMIC_64: &[&str] = &[ >> > > + "powerpc-wrs-vxworks-spe", >> > > + "riscv32gc-unknown-linux-gnu", >> > > + "riscv32gc-unknown-linux-musl", >> > > ++ "riscv32-unknown-linux-gnu", >> > > ++ "riscv32-unknown-linux-musl", >> > > + "riscv32i-unknown-none-elf", >> > > + "riscv32im-unknown-none-elf", >> > > + "riscv32imac-unknown-none-elf", >> > >> > No. Updating this patch with every rust upgrade is already a pain in >> > the ass due to rust checksumming, it needs to be upstreamed in some >> > form rather sooner than later, and you just made it worse. Please >> > let's do a proper arch re-mapping. >> >> we should apply the v1 of patch and move on. > > > No again. Riscv32 is already listed so it’s on you to use existing mapping > to use those entries, and not add new ones. > ? v1 is passing the needed options via cflags. No patching needed. If you have better suggestions come up with a better patch > Alex >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#172058): https://lists.openembedded.org/g/openembedded-core/message/172058 Mute This Topic: https://lists.openembedded.org/mt/94484005/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
