Stream: t-compiler

Topic: miri build failure in stage2


Zach Reizner (Dec 06 2018 at 20:28, on Zulip):

I'm encountering an error in my bootstrapped build of 1.31.0. Anybody else encounter this?

Building stage2 tool miri (x86_64-unknown-linux-gnu)
   Compiling miri v0.1.0 (/var/tmp/portage/dev-lang/rust-1.31.0/work/rustc-1.31.0-src/src/tools/miri)
error: failed to run custom build command for `miri v0.1.0 (/var/tmp/portage/dev-lang/rust-1.31.0/work/rustc-1.31.0-src/src/tools/miri)`
process didn't exit successfully: `/var/tmp/portage/dev-lang/rust-1.31.0/work/rustc-1.31.0-src/build/x86_64-unknown-linux-gnu/stage2-tools/release/build/miri-fb46e632379e59e4/build-script-build` (exit code: 101)
--- stdout
cargo:rustc-env=PROFILE=release
cargo:rerun-if-changed=build.rs
cargo:rustc-env=VERGEN_SHA_SHORT=
cargo:rustc-env=VERGEN_TARGET_TRIPLE=x86_64-unknown-linux-gnu
cargo:rustc-env=VERGEN_SHA=
cargo:rustc-env=VERGEN_COMMIT_DATE=
cargo:rustc-env=VERGEN_BUILD_DATE=2018-12-06
cargo:rustc-env=VERGEN_SEMVER_LIGHTWEIGHT=0.1.0
cargo:rustc-env=VERGEN_SEMVER=0.1.0
cargo:rustc-env=VERGEN_BUILD_TIMESTAMP=2018-12-06T20:25:03.258039997+00:00

--- stderr
thread 'main' panicked at 'Unable to generate vergen keys!: Os { code: 2, kind: NotFound, message: "No such file or directory" }', libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.

command did not execute successfully: "/var/tmp/portage/dev-lang/rust-1.31.0/work/cargo-0.31.0-x86_64-unknown-linux-gnu/cargo/bin/cargo" "build" "--target" "x86_64-unknown-linux-gnu" "-j" "24" "--release" "--frozen" "--manifest-path" "/var/tmp/portage/dev-lang/rust-1.31.0/work/rustc-1.31.0-src/src/tools/miri/Cargo.toml" "--message-format" "json"
expected success, got: exit code: 101
Zach Reizner (Dec 06 2018 at 20:29, on Zulip):

It seems like this may be caused by lack of .git information.

Zach Reizner (Dec 06 2018 at 22:42, on Zulip):

This is filed as https://github.com/rust-lang/rust/issues/56576

Last update: Nov 20 2019 at 01:15UTC