RUSTFLAGS + a sysroot with spaces in its path = 😭

[steveklabnik]

When using cargo-xbuild to do things like "build an OS", you need to set the sysroot via RUSTFLAGS.

Here's an example rustc invocation on my machine that builds:

rustc --crate-name ux "C:\Users\Steve Klabnik\.cargo\registry\src\git.luolix.top-1ecc6299db9ec823\ux-0.1.2\src\lib.rs" --color always --crate-type lib --emit=dep-info,link -C panic=abort -C debuginfo=2 -C metadata=b446262c41a4777f -C extra-filename=-b446262c41a4777f --out-dir "C:\Users\Steve Klabnik\src\intermezzos\kernel\target\intermezzos\debug\deps" --target "\\?\C:\Users\Steve Klabnik\src\intermezzos\kernel\intermezzos.json" -L "dependency=C:\Users\Steve Klabnik\src\intermezzos\kernel\target\intermezzos\debug\deps" -L "dependency=C:\Users\Steve Klabnik\src\intermezzos\kernel\target\debug\deps" --cap-lints allow --sysroot "C:\Users\Steve Klabnik\src\intermezzos\kernel\target\sysroot"

The last bit is the important part:

--sysroot "C:\Users\Steve Klabnik\src\intermezzos\kernel\target\sysroot"

It appears the space in my username causes this to be impossible to set via RUSTFLAGS. With an invocation like this:

~\src\intermezzos\kernel [master ↑1]> $env:RUSTFLAGS="--sysroot ""C:\Users\Steve Klabnik\src\intermezzos\kernel\target\sysroot"""
~\src\intermezzos\kernel [master ↑1]> $env:RUSTFLAGS
--sysroot "C:\Users\Steve Klabnik\src\intermezzos\kernel\target\sysroot"

You can see that it's all good. However, this fails when passed to rustc:

> cargo build
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `rustc - --crate-name ___ --print=file-names --sysroot "\"C:\Users\Steve" "Klabnik\src\intermezzos\kernel\target\sysroot\"" --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro` (exit code: 1)
--- stderr
error: multiple input filenames provided

I am not sure what to do here.

[nagisa]

This is a cargo issue I think.

[steveklabnik]

Yes, I guess that is possible too. Let me double check...

…

On Oct 5, 2018, at 1:57 PM, Simonas Kazlauskas ***@***.***> wrote: This is a cargo issue I think. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[steveklabnik]

Yep, I think this is a Cargo issue. Closing in favor of rust-lang/cargo#6139