-
Notifications
You must be signed in to change notification settings - Fork 255
Problem finding sysroot #544
Comments
What I did:
Content of rls.log:
The project is a basic project with one source file, main.rs which contains:
What I've also noticed is, that it doesn't properly show that there is a type violation in |
@cynecx do you have a |
I'm guilty of "simplifying" that logic and only now I realized I changed the semantics - previously it attempted to extract the sysroot using command at Maybe that's the root of the problem? |
@Xanewok Yes, it's currently set to |
Does |
@Xanewok Yes, it does work. The print sysroot command prints:
|
I have the same problem. I have rustc in path, I don't have The funny thing is, this doesn't really seem to matter much to RLS ‒ it works even after that backtrace. I wouldn't have noticed if I didn't look into the log for other reasons. |
Until this gets fixed, it seems hecaex's fix found in this comment still works. Set the |
@GabrielMajeri unfortunately I just tried this, and at least using the latest nightly Rust this does not in fact stop it from throwing errors |
In my case setting
|
I'm facing the same problem. RLS stopped working a few days ago, first discovered when I saw "RLS: working" as described in #548.
The proposed workaround #544 (comment) did not solve the issue here.
My setup: |
Substituting a compiled binary directly from the git repository solves the problem. There must be something wrong with the version rustup installs. |
@colibre I can confirm that this "fix" works. |
For me, copying rls over borks rustup installation completely. |
@colibre works for me. |
Same problem here Ubuntu 17.2 ..not comfortable with the "fix" print sysroot is also correct . |
|
@MaxBittker Nope. It's still spinnin'. Re-compiling rls and replacing the binary solves the issue. EDIT: Stacktrace
|
1.23.0-nightly (79cfce3d3 2017-11-12) has the RLS fixes in it. @cynecx, Can you run
If it does print that, it may be that your client (like VS Code) is using a non-working RLS version. |
That's strange, I've just run |
Works for me after updating. |
Reported in #450 (comment) by @cynecx
Might be an issue with the client setting up a bad environment, or it might be some bug in the RLS.
@cynecx Could you get a backtrace and try running with logging please? Details about logging are in https://github.com/rust-lang-nursery/rls/blob/master/debugging.md
The text was updated successfully, but these errors were encountered: