Could not compile wtftw_core
rainerborene opened this issue · 4 comments
Compiling wtftw_core v0.3.1 (file:///home/test/Projects/wtftw)
core/src/config.rs:92:9: 123:10 error: internal compiler error: cannot relate bound region: ReScope(DestructionScope(150)) <= ReLateBound(DebruijnIndex { depth: 1 }, BrAnon(0))
core/src/config.rs:92 Config {
core/src/config.rs:93 general: GeneralConfig {
core/src/config.rs:94 focus_follows_mouse: true,
core/src/config.rs:95 focus_border_color: 0x00B6FFB0,
core/src/config.rs:96 border_color: 0x00444444,
core/src/config.rs:97 border_width: 2,
...
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
note: run with `RUST_BACKTRACE=1` for a backtrace
thread 'rustc' panicked at 'Box<Any>', /home/rustbuild/src/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libsyntax/diagnostic.rs:176
stack backtrace:
1: 0x7fee7dc1a5c9 - sys::backtrace::write::h350af8200010e467Z5r
2: 0x7fee7dc22519 - panicking::on_panic::h4194b7c3f2c96e6a0Kw
3: 0x7fee7dbe3212 - rt::unwind::begin_unwind_inner::hf945ded7ea7b4f57aqw
4: 0x7fee7afbd07d - rt::unwind::begin_unwind::h8796533312692526900
5: 0x7fee7afbd012 - diagnostic::SpanHandler::span_bug::h7e9f54619e37e35df6B
6: 0x7fee7bc9f73a - middle::infer::region_inference::RegionVarBindings<'a, 'tcx>::make_subregion::h473442f3e4c3f39dBev
7: 0x7fee7bcb802f - middle::infer::mk_subr::h0776c164be74f332nty
8: 0x7fee7d35f01f - check::regionck::type_must_outlive::h4669d3aa7f47c5baLue
9: 0x7fee7d35d1ca - check::dropck::iterate_over_potentially_unsafe_regions_in_type::hcb1bbdbbf6cef3aaMDa
10: 0x7fee7d35d37c - check::dropck::iterate_over_potentially_unsafe_regions_in_type::hcb1bbdbbf6cef3aaMDa
11: 0x7fee7d35d37c - check::dropck::iterate_over_potentially_unsafe_regions_in_type::hcb1bbdbbf6cef3aaMDa
12: 0x7fee7d35d533 - check::dropck::iterate_over_potentially_unsafe_regions_in_type::hcb1bbdbbf6cef3aaMDa
13: 0x7fee7d35d37c - check::dropck::iterate_over_potentially_unsafe_regions_in_type::hcb1bbdbbf6cef3aaMDa
14: 0x7fee7d35d37c - check::dropck::iterate_over_potentially_unsafe_regions_in_type::hcb1bbdbbf6cef3aaMDa
15: 0x7fee7d35d37c - check::dropck::iterate_over_potentially_unsafe_regions_in_type::hcb1bbdbbf6cef3aaMDa
16: 0x7fee7d35d37c - check::dropck::iterate_over_potentially_unsafe_regions_in_type::hcb1bbdbbf6cef3aaMDa
17: 0x7fee7d35bd58 - check::dropck::check_safety_of_destructor_if_necessary::h4c427730a42a4da1Wxa
18: 0x7fee7d38cf6d - check::regionck::check_safety_of_rvalue_destructor_if_necessary::h9b6ec91f45b6399abQd
19: 0x7fee7d386cc1 - check::regionck::visit_expr::hc9e3bd482aef71ae7ad
20: 0x7fee7d384dba - check::regionck::Rcx<'a, 'tcx>::visit_fn_body::h6820d6f59a6da53bzNc
21: 0x7fee7d3fd71d - check::check_bare_fn::h705b7c21d36bdd45Tun
22: 0x7fee7d409a6c - check::check_method_body::h9107e7ed5684a56cP6n
23: 0x7fee7d3fb365 - check::CheckItemBodiesVisitor<'a, 'tcx>.Visitor<'tcx>::visit_item::h4df3e762586989feWrn
24: 0x7fee7d3fb79f - check::CheckItemBodiesVisitor<'a, 'tcx>.Visitor<'tcx>::visit_item::h4df3e762586989feWrn
25: 0x7fee7d4bbd4a - check_crate::closure.38931
26: 0x7fee7d4b57bc - check_crate::h779a0efdf619d19euJC
27: 0x7fee7e16a37f - driver::phase_3_run_analysis_passes::heb3d8e9920254d63tGa
28: 0x7fee7e14e1ac - driver::compile_input::hd3dd730970eb45c2Qba
29: 0x7fee7e2041b1 - run_compiler::h4be6ca332f13312675b
30: 0x7fee7e201a02 - boxed::F.FnBox<A>::call_box::h7925108573723512372
31: 0x7fee7e200fc9 - rt::unwind::try::try_fn::h5378213576640735239
32: 0x7fee7dc9ac28 - rust_try_inner
33: 0x7fee7dc9ac15 - rust_try
34: 0x7fee7e201264 - boxed::F.FnBox<A>::call_box::h12991688188475136491
35: 0x7fee7dc212b1 - sys::thread::Thread::new::thread_start::h750ed153b2916909hxv
36: 0x7fee77cbd373 - start_thread
37: 0x7fee7d87327c - clone
38: 0x0 - <unknown>
Could not compile `wtftw_core`.
To learn more, run the command again with --verbose.
Currently using:
cargo 0.2.0-nightly (a483581 2015-05-14) (built 2015-05-15)
rustc 1.2.0-nightly (c23a9d42e 2015-05-17) (built 2015-05-17)
Yeah, unfortunately that's a known bug. rust-lang/rust#25279
Can't do anything about that at the moment other than suggest to compile it with 1.0 stable.
There might be a way to alter the source code as to not trigger that internal compiler fault, but at the moment I am knee deep in my thesis, sorry.
But I'll leave this open until the compiler issue is resolved.
Ok, it should work now with, at least with nightly (that's what I tested with).
Sorry to bump this old thread.
I'm trying to build wtftw on ubuntu 15.04 with the latest stable and stumbled into this.
How should I proceed to update my rust stack?
Yeah you have to use 1.1 at least I think.