-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for riscv64gc-unknown-linux-musl #118
Comments
I don't know too much Rust, so I don't know what exactly is wrong here. I did try just building the
|
Did you run |
🤦 I did not... sorry. I guess it's a ripgrep thing, then? Thanks. |
I guess it got added with commit b913c24, but there hasn't been a release since then. Will that be coming at some point? |
tikv-jemallocator 0.6.0 was released, which should contain the commit. However, due to lack of force merge permission, jemallocator 0.6.0 is not released. Track on #96. |
Thanks!On Feb 16, 2025, at 21:37, Jay ***@***.***> wrote:
tikv-jemallocator 0.6.0 was released, which should contain the commit. However, due to lack of force merge permission, jemallocator 0.6.0 is not released. Track on #96.—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: ***@***.***>
BusyJay left a comment (tikv/jemallocator#118)
tikv-jemallocator 0.6.0 was released, which should contain the commit. However, due to lack of force merge permission, jemallocator 0.6.0 is not released. Track on #96.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
I've got a BananaPi BPI-F3 RISC-V dev board but, right now, this crate does not support it.
upstream jemalloc/jemalloc does support this target.
The text was updated successfully, but these errors were encountered: