Internal Compiler Error after setting flag "-L/usr/local/lib"

[dwrensha]

I observe this error on Mac OSX 10.9.

// test.rs
fn main() {}

$ rustc -L/usr/local/lib test.rs
task 'rustc' failed at 'assertion failed: lib.dylib.is_none()', rust/src/librustc/metadata/loader.rs:211
error: internal compiler error: unexpected failure
This message reflects a bug in the Rust compiler. 
We would appreciate a bug report: https://github.com/mozilla/rust/wiki/HOWTO-submit-a-Rust-bug-report
note: the compiler hit an unexpected failure path. this is a bug
note: try running with RUST_LOG=rustc=1 to get further details and report the results to github.com/mozilla/rust/issues
task '<main>' failed at 'explicit failure', 
rust/src/librustc/lib.rs:441

Note that /usr/local/lib is the installation directory for Rust.

I ran into this error when I was trying to built rust-zmq, which requires linking against zmq.dylib, which is also installed in /usr/local/lib.

[alexcrichton]

The sequence of events that would lead to this error are:

1. An rlib for library X is found
2. The corresponding dylib for library X is found
3. The corresponding dylib for library X is found again (listed in the search paths twice?)

Right now this is an assertion that I used when debugging the introduction of rlibs, but I don't think that it's ok to override that assertion. If you've got /usr/local/lib as the installation directory for rust, then this is probably picking up the libstd that is used by rustc itself, and not the target libstd which you're supposed to be linking against.

All in all, this is correctly an error today, although This should certainly not actually be an error. We advertise rust as being installable to /usr/local/lib, (or /usr/lib), and it looks like that doesn't quite work. This would need a resolution of #11145 to make further progress on this issue.

In the meantime, I would sadly recommend installing rustc itself not to /usr/local/lib, but you can continue to install all other rust libraries to /usr/local/lib.

[SiegeLord]

then this is probably picking up the libstd that is used by rustc itself, and not the target libstd which you're supposed to be linking against.

Why can't rustc be statically compiled?

[lilyball]

This no longer ICEs. Instead it complains about multiple matching libraries.

> rustc -L/usr/local/lib test.rs
test.rs:1:1: 1:1 error: multiple dylib candidates for `std` found
test.rs:1 fn main() {}
          ^
test.rs:1:1: 1:1 note: candidate #1: /usr/local/lib/rustlib/x86_64-apple-darwin/lib/libstd-59beb4f7-0.11.0-pre.dylib
test.rs:1 fn main() {}
          ^
test.rs:1:1: 1:1 note: candidate #2: /usr/local/lib/libstd-59beb4f7-0.11.0-pre.dylib
test.rs:1 fn main() {}
          ^
test.rs:1:1: 1:1 error: multiple dylib candidates for `libc` found
test.rs:1 fn main() {}
          ^
test.rs:1:1: 1:1 note: candidate #1: /usr/local/lib/rustlib/x86_64-apple-darwin/lib/liblibc-4f9a876d-0.11.0-pre.dylib
test.rs:1 fn main() {}
          ^
test.rs:1:1: 1:1 note: candidate #2: /usr/local/lib/liblibc-4f9a876d-0.11.0-pre.dylib
test.rs:1 fn main() {}
          ^
error: aborting due to 2 previous errors

[steveklabnik]

Today, this gives me no error. Closing.