-
Notifications
You must be signed in to change notification settings - Fork 165
RLS fails to start, error running rustup #293
Comments
When trying to After
and installing rls via Nevertheless, a more helpful error message would be nice. |
Unfortunately, I have encountered a very similar error after cleaning As previously, I tried to install the nightly toolchain. Due to rust-lang/rust#51699 I needed to specify it manually:
The error message is exactly the same. /edit: after setting |
@marmistrz could you try again today please? Nightly on rustup has been broken for a few days but should now be fixed. |
I'm getting same error after update to stable-x86_64-unknown-linux-gnu - rustc 1.33.0 (2aa4c46cf 2019-02-28) and nightly-x86_64-unknown-linux-gnu - rustc 1.35.0-nightly (f22dca0a1 2019-03-05) |
@robatipoor Looks like the #517. Adding |
The same thing that happened to @robatipoor also happened to me. Thanks for the guidance on how to fix it. For those (like me), who need a little more hand-holding on vscode, here is what I did to fix it, step-by-step:
So the file looks something like this:
|
Thank's, that was the solution for me ! |
configure to handle different library and symbol names... need to check this tomorrow: https://github.com/rust-lang/libc/search?q=%5Blink%28name&unscoped_q=%5Blink%28name configuration attributes: https://doc.rust-lang.org/reference/attributes.html https://doc.rust-lang.org/reference/conditional-compilation.html https://users.rust-lang.org/t/platform-specific-use-statements/6923 (char types and FFI) https://stackoverflow.com/questions/24145823/how-do-i-convert-a-c-string-into-a-rust-string-and-back-via-ffi this to get my VSCode back to work rust-lang/vscode-rust#293
We now surface a lot more errors as to why RLS could not be started or installed, so I'll close this issue. |
I'm getting a warning:
later on:
in the
Rust Language Server
logs:The text was updated successfully, but these errors were encountered: