-
Notifications
You must be signed in to change notification settings - Fork 190
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
The newly updated version "0.2.13" cannot run on mipsel #407
Comments
This is almost certainly caused by #396 That PR removed certain fallback code on certain Linux CPU architectures (all CPU architectures that aren't ARM, x86, PowerPC, or s390). On such architectures (like @lbl8603 to help us debug further:
|
CC @newpavlov @briansmith (who worked on #396) |
|
Looking at the platform list, it seems like the musl targets don't list a minimum kernel version (they just require MUSL 1.2.3 which requires kernel 2.6 or later), while for @lbl8603 out of curiosity what system/distro are you running on? Based on the @newpavlov @briansmith should we support MUSL systems with kernels older than 3.17? |
Hm, Adding a MUSL exception looks like an obvious solution for now. |
I'm wondering if MUSL might target an older kernel version. It seems like a lot of the folks who target very old kernels intentionally use MUSL to avoid depending on an ancient glibc. EDIT: Looking at rust-lang/compiler-team#493 it seems like the only reason Linux 3.2 is even required by rust is to support GLIBC (whose newer versions have that as the minimum kernel version). |
Compiling target |
It can run normally before you update 0.2.13
thread 'main' panicked at 'could not initialize thread_rng: Function not implemented', /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rand-0.8.5/src/rngs/thread.rs:72:17
note: run with
RUST_BACKTRACE=1
environment variable to display a backtraceAborted
The text was updated successfully, but these errors were encountered: