Stream: t-compiler/help

Topic: env vars and x.py


nikomatsakis (Oct 04 2019 at 18:40, on Zulip):

Argh it drives me crazy when I get messages like this:

thread 'main' panicked at 'RUSTC_STAGE was not set: NotPresent', src/libcore/result.rs:1165:5

is there some easy way to get access to all the env variables?

Santiago Pastorino (Oct 04 2019 at 18:46, on Zulip):

would be good to know this

Santiago Pastorino (Oct 04 2019 at 18:46, on Zulip):

last time I just added a bunch of println!s around here https://github.com/rust-lang/rust/blob/2e7244807a7878f6eca3eb7d97ae9b413aa49014/src/bootstrap/builder.rs#L912

pnkfelix (Oct 07 2019 at 08:05, on Zulip):

there's an issue where nagisa recommended a more general observation mechanism, let me find it

pnkfelix (Oct 07 2019 at 08:06, on Zulip):

x.py --on-fail is what we've talked about in the past

pnkfelix (Oct 07 2019 at 08:08, on Zulip):

so the ancient issue about this is #38686

pnkfelix (Oct 07 2019 at 08:08, on Zulip):

and nagisa addressed it via PR #39888

pnkfelix (Oct 07 2019 at 08:09, on Zulip):

but using that with bash stopped working sometime in 2017/2018, as documented in #47645; but you can still use x.py --on-fail=print-env instead of trying to do x.py --on-fail=bash.

Last update: Nov 11 2019 at 22:00UTC