Could not compile gcc

[wraithan]

This doesn't appear to be a problem with my application but I can push a copy of it at the current point and link to that if it is useful. This is occurring when I have my application setup to run cargo clean && cargo test on file change. I am on OSX and I believe I've included all relevant version information.

Output

OS Version

$ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.10
BuildVersion:   14A389

Rust Version

$ rustc --version
rustc 0.13.0-nightly (ffc111889 2014-12-12 21:07:19 +0000)

Cargo Version

$ cargo --version
cargo 0.0.1-pre-nightly (0f6667c 2014-12-08 21:19:01 +0000)

Error and Trace

$ RUST_BACKTRACE=1 cargo test
   Compiling gcc v0.1.1
error: internal compiler error: unexpected panic
note: the compiler unexpectedly panicked. 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' panicked at 'called `Result::unwrap()` on an `Err` value: couldn't copy path (the source path is not an existing file; from=/Users/wraithan/devel/rust/ferric-mail/target/deps/gcc-a225ab49d731620d.0.o; to=/Users/wraithan/devel/rust/ferric-mail/target/deps/gcc-a225ab49d731620d.o)', /Users/rustbuild/src/rust-buildbot/slave/nightly-mac/build/src/libcore/result.rs:744

stack backtrace:
   1:        0x106b865c0 - rt::backtrace::imp::write::h276c1d3da30d25d7bVx
   2:        0x106b897d0 - failure::on_fail::h26104c4e5109e22dPhy
   3:        0x106dda905 - unwind::begin_unwind_inner::heffc9437c9480c1cFBc
   4:        0x106dda5e7 - unwind::begin_unwind_fmt::h65a57e1c4c39bde22yc
   5:        0x106dda302 - rust_begin_unwind
   6:        0x106e281ec - panicking::panic_fmt::h114ee3e43194a3bcRtl
   7:        0x103caba01 - back::write::run_passes::closure.35659
   8:        0x103ca79d3 - back::write::run_passes::hcde40b8895145e33jHc
   9:        0x103566c51 - driver::phase_5_run_llvm_passes::closure.19122
  10:        0x103530b8f - util::common::time::h2908045668643024249
  11:        0x1034ffa31 - driver::phase_5_run_llvm_passes::h03d44c2eafb16b8aNDa
  12:        0x1034e7050 - driver::compile_input::h07eb2d0e88b46326pba
  13:        0x10357e8ed - run_compiler::h657657a0aa19c050EYb
  14:        0x10357d34e - run::closure.21518
  15:        0x10358e7ae - task::TaskBuilder::try_future::closure.22972
  16:        0x106b5f833 - task::TaskBuilder::spawn_internal::closure.30639
  17:        0x106dd850d - task::Task::spawn::closure.5568
  18:        0x106e3feac - rust_try_inner
  19:        0x106e3fe96 - rust_try
  20:        0x106dd85e7 - unwind::try::h9964c705e60747d7Wqc
  21:        0x106dd83bc - task::Task::run::h976e36ba3d824167fIb
  22:        0x106dd80bf - task::Task::spawn::closure.5544
  23:        0x106dd99c7 - thread::thread_start::h436a5ebf6a0549c5wZb
  24:     0x7fff8ef412fc - _pthread_body
  25:     0x7fff8ef41279 - _pthread_body

Could not compile `gcc`.

To learn more, run the command again with --verbose.
make[1]: *** [test] Error 101

[alexcrichton]

Bugs like this generally reflect that there are multiple instances of Cargo running parallel, which is known to result in badness.

For now though, this looks like a dupe of rust-lang/cargo#354, so closing in favor of that. Thanks for the report though!

[cgaebel]

I just got the same thing. rm -rf target/ and rebuild fixed it for me.