You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specifically, I guess, the jemallocator crate just fixed the riscv64gc-unknown-linux-musl build in January 2024, but the current release is actually from mid-2023 :(
The simplest thing here would be to just not use jemallocator on this target. It's already a target specific dependency. Patches are welcome.
(The purpose of jemallocator is to replace the musl allocator, which is somewhat slow. But this is in the pursuit of squeezing every ounce of perf we can and probably doesn't make a huge difference in many workloads. So you might be perfectly fine with musl's allocator.)
I just opened #2992 which disables jemallocator for RISC-V musl targets and builds successfully, though hopefully it can be re-enabled once jemallocator gets a new release and the crates.io version is able to support RISC-V + musl.
Right now, building ripgrep fails because of
Invalid configuration
riscv64gc-unknown-linux-musl': machineriscv64gc-unknown' not recognized
.Upstream tikv/jemalloc supports this target: https://github.com/tikv/jemallocator/blob/fa4486d23f7402f3999b8c857333c60090001314/jemalloc-sys/build.rs#L393
I'd like to be able to run ripgrep on my RISC-V board that's using musl libc
The text was updated successfully, but these errors were encountered: