Open jrobsonchase opened 6 years ago
I'm not sure how sccache works, but I don't think you will be able to use it with the RLS since we use our own version of rustc, so I don't think that will work with RUSTC_WRAPPER
Oh, I thought that rls
are just not working yet. Will retry without sccache
Is is possible for RLS to remove RUSTC_WRAPPER from the environment that is passed to rustc ? (as long as this feature is not supported by RLS)
This will make RLS working as usual in an environment that use sccache
^ -- I think that's a reasonable thing to do.
My logs are flooded with the same multiple input provided. And I don't want to stop using sccache just because of this. If that is indeed the only problem, perhaps, make RLS remove it from it's own env before starting rustc?
It's seems like what must be a simple solution. I don't know why this issue is open for so long unfixed.
Is there a workaround for this? I think this bug is the reason why the VSCode rust extension doesn't work for me at all.
The same problem here.
I can't find a workaround so I removed sccache
from RUSTC_WRAPPER
finally.
Still experiencing
This is not an issue with rust-analyzer.
Setting
RUSTC_WRAPPER=$HOME/.local/bin/sccache
seems to cause rls to fail to compile withmultiple input filenames provided
. Tested with sccache 2.5 and rls-preview 0.125.0-nightly (dee42bd 2018-02-04).vscode rust settings:
Log with
RUSTC_WRAPPER
set andRUST_LOG=rls=debug
: