Stream: general

Topic: bootstrap-issues


davidtwco (Jul 03 2018 at 19:43, on Zulip):

Doing a fresh build of Rust, just cloned on the system I normally use and I'm getting the following:

Updating only changed submodules
Submodules updated in 0.21 seconds
    Finished dev [unoptimized] target(s) in 0.92s
Warning: Using a potentially old librustc. This may not behave well.
Warning: Using a potentially old libstd. This may not behave well.
Warning: Using a potentially old libtest. This may not behave well.
Warning: Using a potentially old librustc. This may not behave well.
Warning: Using a potentially old librustc. This may not behave well.
Copying stage0 rustc from stage0 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
thread 'main' panicked at 'File::open(stamp) failed with No such file or directory (os error 2)', bootstrap/lib.rs:1093:12
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
             at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::print
             at libstd/sys_common/backtrace.rs:71
             at libstd/sys_common/backtrace.rs:59
   2: std::panicking::default_hook::{{closure}}
             at libstd/panicking.rs:211
   3: std::panicking::default_hook
             at libstd/panicking.rs:227
   4: std::panicking::rust_panic_with_hook
             at libstd/panicking.rs:511
   5: std::panicking::continue_panic_fmt
             at libstd/panicking.rs:426
   6: std::panicking::begin_panic_fmt
             at libstd/panicking.rs:413
   7: bootstrap::Build::read_stamp_file
             at bootstrap/lib.rs:1093
   8: bootstrap::compile::add_to_sysroot
             at bootstrap/compile.rs:1015
   9: <bootstrap::compile::RustcLink as bootstrap::builder::Step>::run
             at bootstrap/compile.rs:618
  10: bootstrap::builder::Builder::ensure
             at bootstrap/builder.rs:1117
  11: <bootstrap::compile::Rustc as bootstrap::builder::Step>::run
             at bootstrap/compile.rs:496
  12: bootstrap::builder::Builder::ensure
             at bootstrap/builder.rs:1117
  13: <bootstrap::compile::Assemble as bootstrap::builder::Step>::run
             at bootstrap/compile.rs:953
  14: bootstrap::builder::Builder::ensure
             at bootstrap/builder.rs:1117
  15: bootstrap::builder::Builder::compiler
             at bootstrap/builder.rs:577
  16: <bootstrap::compile::Std as bootstrap::builder::Step>::make_run
             at bootstrap/compile.rs:56
  17: bootstrap::builder::StepDescription::maybe_run
             at bootstrap/builder.rs:191
  18: bootstrap::builder::StepDescription::run
             at bootstrap/builder.rs:215
  19: bootstrap::builder::Builder::run_step_descriptions
             at bootstrap/builder.rs:569
  20: bootstrap::builder::Builder::execute_cli
             at bootstrap/builder.rs:559
  21: bootstrap::Build::build
             at bootstrap/lib.rs:461
  22: bootstrap::main
             at bootstrap/bin/main.rs:29
  23: std::rt::lang_start::{{closure}}
             at /checkout/src/libstd/rt.rs:74
  24: std::panicking::try::do_call
             at libstd/rt.rs:59
             at libstd/panicking.rs:310
  25: __rust_maybe_catch_panic
             at libpanic_unwind/lib.rs:105
  26: std::rt::lang_start_internal
             at libstd/panicking.rs:289
             at libstd/panic.rs:392
             at libstd/rt.rs:58
  27: std::rt::lang_start
             at /checkout/src/libstd/rt.rs:74
  28: main
  29: __libc_start_main
  30: _start
failed to run: /mnt/c/Users/David/Projects/personal/rust0/build/bootstrap/debug/bootstrap build --config ./config.toml --stage 1 --keep-stage 0 -j 4 -i
Build completed unsuccessfully in 0:00:04

Any ideas? I've tried clearing the build directory and completely re-cloning but seem to be getting nowhere?

Jake Goulding (Jul 03 2018 at 19:43, on Zulip):

This may not behave well.

Nailed it.

davidtwco (Jul 03 2018 at 19:43, on Zulip):

It did successfully pull down all the submodules in the first run.

davidtwco (Jul 03 2018 at 19:44, on Zulip):

It's a fresh build of master. So I don't know why it is saying that.

Jake Goulding (Jul 03 2018 at 19:44, on Zulip):

Which SHA?

davidtwco (Jul 03 2018 at 19:44, on Zulip):

860d169474acabdc53b9a698f8ce02eba7e0daeb

simulacrum (Jul 03 2018 at 19:44, on Zulip):

That message should only be printed if you pass --keep-stage...

simulacrum (Jul 03 2018 at 19:45, on Zulip):

are you?

davidtwco (Jul 03 2018 at 19:45, on Zulip):

Ah, I am doing that. It's just one of the flags I always pass.

simulacrum (Jul 03 2018 at 19:45, on Zulip):

Yeah, the behavior has been updated such that compiler devs are happier; that also means that it might not do what you expect

Jake Goulding (Jul 03 2018 at 19:45, on Zulip):
 * [new branch]            weak-unboxing -> upstream/weak-unboxing

Who is pushing their topic branches to the master repo, SMH

Jake Goulding (Jul 03 2018 at 19:46, on Zulip):

This is why we can't have nice things

davidtwco (Jul 03 2018 at 19:46, on Zulip):

Alright, it worked without that, thanks!

Last update: Nov 22 2019 at 00:05UTC