Closed
Description
I am seeing the following failure in what should be a clean build.
$ wget https://static.rust-lang.org/dist/rustc-1.31.0-src.tar.gz
$ tar xf rustc-1.31.0-src.tar.gz
$ cd rustc-1.31.0-src
$ sed 's/#extended = false/extended = true/' config.toml.example > config.toml
$ ./x.py build
...
Building stage2 tool miri (x86_64-unknown-linux-gnu)
Compiling num-traits v0.2.5
Compiling num-integer v0.1.39
Compiling bitflags v1.0.4
Compiling byteorder v1.2.3
Compiling time v0.1.40
Compiling failure v0.1.2
Compiling chrono v0.4.4
Compiling vergen v3.0.3
Compiling miri v0.1.0 (rustc-1.31.0-src/src/tools/miri)
error: failed to run custom build command for `miri v0.1.0 (rustc-1.31.0-src/src/tools/miri)`
process didn't exit successfully: `rustc-1.31.0-src/build/x86_64-unknown-linux-gnu/stage2-tools/release/build/miri-ffcc0501a1e0abe7/build-script-build` (exit code: 101)
--- stdout
cargo:rustc-env=PROFILE=release
cargo:rerun-if-changed=build.rs
cargo:rustc-env=VERGEN_SEMVER_LIGHTWEIGHT=0.1.0
cargo:rustc-env=VERGEN_TARGET_TRIPLE=x86_64-unknown-linux-gnu
cargo:rustc-env=VERGEN_SHA_SHORT=
cargo:rustc-env=VERGEN_SEMVER=0.1.0
cargo:rustc-env=VERGEN_BUILD_TIMESTAMP=2018-12-06T22:22:03.560705685+00:00
cargo:rustc-env=VERGEN_COMMIT_DATE=
cargo:rustc-env=VERGEN_SHA=
cargo:rustc-env=VERGEN_BUILD_DATE=2018-12-06
--- 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: "rustc-1.31.0-src/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "build" "--target" "x86_64-unknown-linux-gnu" "-j" "28" "--release" "--manifest-path" "rustc-1.31.0-src/src/tools/miri/Cargo.toml" "--message-format" "json"
expected success, got: exit code: 101
Build completed successfully in 0:06:23
Mentioning @oli-obk in case you know of an easy fix.
Mentioning @zachreizner who hit this upgrading Chrome OS to Rust 1.31.