Compiler told me to report bug: "can't determine value for sysroot"

[logicchains]

I encountered the following output when trying to compile a simple program (well, any simple program) with rustc:

error: internal compiler error: unexpected failure
note: the compiler hit an unexpected failure path. this is a bug.
note: we would appreciate a bug report: http://doc.rust-lang.org/complement-bugreport.html
note: run with `RUST_BACKTRACE=1` for a backtrace
task 'rustc' failed at 'can't determine value for sysroot', /build/rust/src/rust-nightly/src/librustc/metadata/filesearch.rs:179

And so I'm duly reporting it. My OS is the latest ARMv7 ArchLinux build, running on a Galaxy SIII (in a chroot). It was working previously, but then I rebooted the phone and attempted to run rustc before I had properly mounted sysfs, proc and devpts. If I mount those, it works fine. So the bug isn't an actual hindrance, but nevertheless I'm reporting it as requested by the compiler.

[steveklabnik]

Triage bump. @logicchains , does this still ICE in this situation?

[logicchains]

Unfortunately I don't have that ARM system setup now. I could test it in an
x86 chroot Arch Linux without mounting sysfs and proc, would that be any
use?

On 21 April 2015 at 10:22, Steve Klabnik notifications@github.com wrote:

Triage bump. @logicchains https://github.com/logicchains , does this
still ICE in this situation?

—
Reply to this email directly or view it on GitHub
#16229 (comment).

[steveklabnik]

It depends. This was filed a long time ago, and we haven't heard of anything from anyone since, so maybe just giving it a close is appropriate, since it no longer affects you?

[logicchains]

Sure, closing it would be fine with me. I only opened it because the
compiler told me to.

On 23 April 2015 at 00:56, Steve Klabnik notifications@github.com wrote:

It depends. This was filed a long time ago, and we haven't heard of
anything from anyone since, so maybe just giving it a close is appropriate,
since it no longer affects you?

—
Reply to this email directly or view it on GitHub
#16229 (comment).

[bryteise]

Just as a bump, I still see this on an x86_64 in a chroot without proc, sys and dev mounted trying to build 1.3.0.

thread 'rustc' panicked at 'can't determine value for sysroot', ../src/librustc/metadata/filesearch.rs:206

[thegatsbylofiexperience]

I am also receiving this error... I was running 1.11.0 (stable) with no issue but after using rustup to upgrade to 1.14.0 (stable).

I have also changed to 1.12.0 with the same panic.

I am running this on a Ubuntu 14.04 LXC container inside a smartos (solaris) host.
I understand this is not exactly a common setup. :P

edit:
I have now tried downgrading to 1.11.0 and that now does not work too.

[thegatsbylofiexperience]

1.14.0 error string: thread 'rustc' panicked at '../src/librustc/session/filesearch.rs:164: can't determine value for sysroot', ../src/librustc/session/mod.rs:771

[thegatsbylofiexperience]

I managed to get all working again after upgrading my container host os and rebooting. Not sure which part of the two fixed it. Thanks, and sorry for wasting time.

[Mark-Simulacrum]

Not a waste of time! Seems like this isn't really reproducible in most cases; closing.