-
Notifications
You must be signed in to change notification settings - Fork 13.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compiler error when referencing crate "glfw-rs" #12377
Comments
This means that you've got two versions of the same |
I have just build the library for the first time, and I can only find one dylib for it on my system (next to the rlib, but I gues that shouldn't cause any problems). Is there another possibility for this error? Gesendet: Mittwoch, 19. Februar 2014 um 01:09 UhrVon: "Alex Crichton" [email protected]: mozilla/rust [email protected]: hhildebr [email protected]: Re: [rust] Compiler error when referencing crate "glfw-rs" (#12377) This means that you've got two versions of the same libglfw-rs.dylib lying around, and rustc doesn't like having two versions. This will be fixed by #12164, I just need to land it :( — |
Having a dylib and an rlib simultaneously should not be a problem, it is in fact quite common. Having 2 dylibs and 1 rlib or 2 rlibs and 1 dylib however is a problem. |
sorry, my mistake in parsing the title of #12164. |
Yes, indeed, I had several identical dylibs, but it wasn't the glfw-rs.. there were rust libs in /usr/local/lib and /usr/local/lib/rustlib/...
Thanks!
Gesendet: Mittwoch, 19. Februar 2014 um 17:15 UhrVon: "Alex Crichton" [email protected]: mozilla/rust [email protected]: hhildebr [email protected]: Re: [rust] Compiler error when referencing crate "glfw-rs" (#12377) Having a dylib and an rlib simultaneously should not be a problem, it is in fact quite common. Having 2 dylibs and 1 rlib or 2 rlibs and 1 dylib however is a problem. — |
@hhildebr so can we close this ticket now, in that case? Or do you want to wait for alexcrichton's patches to land, and see what things look like for you then? |
Nono,
the ticket can be closed for now. Thanks for your help!
Gesendet: Mittwoch, 19. Februar 2014 um 21:30 UhrVon: "Felix S Klock II" [email protected]: mozilla/rust [email protected]: hhildebr [email protected]: Re: [rust] Compiler error when referencing crate "glfw-rs" (#12377) @hhildebr so can we close this ticket now, in that case? Or do you want to wait for alexcrichton's patches to land, and see what things look like for you then? — |
minor: log build script invocations
fix [`empty_docs`] trigger in proc-macro fixes: rust-lang#12377 --- changelog: fix [`empty_docs`] trigger in proc-macros
Built glfw-rs using rust 0.10-pre. When referencing this crate in another source file and building, I get
error: internal compiler error: unexpected failure
This message reflects a bug in the Rust compiler.
We would appreciate a bug report: http://static.rust-lang.org/doc/master/complement-bugreport.html
note: the compiler hit an unexpected failure path. this is a bug
Ok(task 'rustc' failed at 'assertion failed: lib.dylib.is_none()', /Users/haukehildebrandt/Documents/Development/MagnaTerra/Rust/rust/src/librustc/metadata/loader.rs:214
)
This is on OSX 10.9:
rustc 0.10-pre (a886549 2014-02-18 10:16:48 -0800)
host: x86_64-apple-darwin
The text was updated successfully, but these errors were encountered: