-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Error loading shared library libgcc_s.so.1; Error relocating XXX (musl, Ubuntu) #108907
Comments
Could it be that the user hasn't installed musl? Given that they are on ubuntu using a musl toolchain (which is very weird anyways, they should be using a musl target). So I guess this issue is a request for a better error message? Or a warning when using a non-host toolchain? I don't quite understand what is expected here. |
A better error message would certainly be useful. I have the toolchain installed because I need to use it as a target. I ran into this issue while trying to run |
I don't think there is much |
The rustc toolchain performs cross-compilation natively, it is not necessary to install a toolchain that differs from your host. Please post any bugs you encounter while cross-compiling from a host gnu toolchain to a musl target. |
WG-prioritization assigning priority (Zulip discussion). @rustbot label -I-prioritize +P-low |
I got the same problem on Debian 12 Bookworm: Download
Install
Environment check
|
@Berbe Debian is a glibc host. You must use the x86_64-unknown-linux-gnu host toolchain. If you go out of your way to install the musl host, then you get a host that is meant to be run on a musl distro. You are bypassing the rustup shell installer to run a binary that happens to be statically linked, but the host toolchain is dynamically linked, because it's for Alpine and the like. Really, we can't actually solve this any more than we can solve people trying to run the Windows host on their Mac, and we get the same class of errors. Closing. |
(ported over from rust-lang/rustup#3254 )
Ran:
User expected to see this happen: a reasonable version output
Instead, this happened: the above linking/loading failures.
The text was updated successfully, but these errors were encountered: