ICE: "No triple in crate" when building js.rs

[ngsankha]

I was trying to build the js.rs project with rustc 0.11.0-pre-nightly (7ec7805 2014-06-16 08:16:49 +0000) on Ubuntu 12.04 64 bit.

I ran into an error and then ran it again with RUST_BACKTRACE=1 and here is the output I got:

cd target && rustc ../src/front/front.rs -L .
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 'No triple in crate', /home/rustbuild/src/rust-buildbot/slave/nightly-linux/build/src/libcore/option.rs:246

stack backtrace:
   1:     0x2b493d218970 - rt::backtrace::imp::write::h5132eab0d9bd9243kGp::v0.11.0.pre
   2:     0x2b493d2200a0 - failure::on_fail::hb0e2b0e9114df057Q1p::v0.11.0.pre
   3:     0x2b493caa4400 - unwind::begin_unwind_inner::h505156ff65762c6aQRd::v0.11.0.pre
   4:     0x2b493caa3e90 - unwind::begin_unwind_fmt::h1b95d8aad331c544jPd::v0.11.0.pre
   5:     0x2b493caa3e50 - rust_begin_unwind
   6:     0x2b493caecc40 - failure::begin_unwind::h307e1fb63a5490ed23v::v0.11.0.pre
   7:     0x2b493a92bab0 - metadata::decoder::get_crate_triple::h4cd78fbea11c9a6cddr::v0.11.0.pre
   8:     0x2b493a94d540 - metadata::loader::Context<'a>::extract_one::h8295a54013b91f670St::v0.11.0.pre
   9:     0x2b493a9442a0 - metadata::loader::Context<'a>::find_library_crate::h603c58c46dff84f3tlt::v0.11.0.pre
  10:     0x2b493a93dc30 - metadata::creader::PluginMetadataReader<'a>::read_plugin_metadata::ha8fc9fe164df40b3c9r::v0.11.0.pre
  11:     0x2b493aa41180 - plugin::load::PluginLoader<'a>.Visitor<(*>::visit_view_item::ha4896319f8ba867aUIy::v0.11.0.pre
  12:     0x2b493aa410a0 - visit::walk_crate::h8948545686026892103::v0.11.0.pre
  13:     0x2b493a95d3a0 - driver::driver::phase_2_configure_and_expand::h943c8d82ead48213lkv::v0.11.0.pre
  14:     0x2b493a958330 - driver::driver::compile_input::h3da42a086c5ec4b59dv::v0.11.0.pre
  15:     0x2b493aa23030 - driver::run_compiler::h36852bed2c8a2fe6LXx::v0.11.0.pre
  16:     0x2b493aa22f40 - driver::main_args::closure.98559
  17:     0x2b493aa3ea70 - driver::monitor::closure.99649
  18:     0x2b493aa399b0 - task::TaskBuilder::try::closure.99412
  19:     0x2b4939aaf240 - task::spawn_opts::closure.7149
  20:     0x2b493caa0fb0 - task::Task::run::closure.5308
  21:     0x2b493cb064c0 - rust_try
  22:     0x2b493caa39f0 - unwind::try::hff9f11c8495162d3fGd::v0.11.0.pre
  23:     0x2b493caa0e30 - task::Task::run::hd14e65be9d626e23VVc::v0.11.0.pre
  24:     0x2b4939aaefe0 - task::spawn_opts::closure.7122
  25:     0x2b493caa2fc0 - thread::thread_start::h29b39a0f53979794kdd::v0.11.0.pre
  26:     0x2b493d868dc0 - start_thread
  27:                0x0 - <unknown>

[pnkfelix]

(updated title to be more descriptive)

[alexcrichton]

I'm a little baffled why this is still coming up. Unless you're using libraries that were built more than a month ago at this point, this error should be impossible to reach.

Do you have stale libraries lying around that have been there for upwards of a month causing this problem?

[ngsankha]

@alexcrichton I had an old version of Rust which I had built from source and installed using make install. Can that be a possible source of conflict?

[alexcrichton]

That could indeed! The old version of Rust would have to be quite old at this point to generate this error as well.

[ngsankha]

How can I get rid of the old files, without changing the current installation?

[alexcrichton]

I would recommend cleaning out all built libraries and being sure to use the right installation to compile everything from scratch. Updating to the latest nightly should also be quite easy.

[steveklabnik]

Is this issue still relevant?

[tamird]

@steveklabnik probably time to close as stale