-
Notifications
You must be signed in to change notification settings - Fork 14
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
gstreamer does not build in rust 1.4, cargo 0.5. #5
Comments
it's working for me fine, have you tried to run |
It pulled 2.2 for me initially, but gave the same error. I downgraded to 1.12 because that was what was in the passing Travis build, in case it had been a breaking upgrade. If it's working for you, I'm curious what exact rustc / cargo versions are you using? Given that rustc's error points to a discussion of stabilization of libc in future rustc versions, I suspect that this issue is (hopefully) only temporarily unstable. That said, I'd be willing to use an older version of the compiler if that makes the code work. |
i've just installed 1.4 stable from the web, i'm using cargo 0.5.0-nightly (833b947 2015-09-13) and rustc 1.4.0 (8ab8581f6 2015-10-27) on linux |
It looks like the only difference in our setup right now is the platform; I may be able to get a linux box up and running in a little while to see if On Mon, Dec 7, 2015 at 7:59 PM, arturo [email protected] wrote:
|
Adding 'libc = "*"' to [build-dependencies] seems to fix it on windows, 1.5 stable and 1.6 beta. |
Alternately, you can replace build.rs:20 with the following: let key = if cfg!(target_pointer_width = "32") { and it appears to work then, also. |
thanks! |
i've also removed the dependency with libc since the needed types are now in std::os::raw |
I've tested this with libc 0.1.12 and 0.2.2; they both return the same error.
The referred error (rust-lang/rust#27783) is a bit opaque to me given that as far as I can tell, you do in fact require the use of libc from crates.io in your Cargo.toml here.
Any ideas what's going on here and how to get this to compile, or do you feel it's more useful to just wait until libc stabilizes?
The text was updated successfully, but these errors were encountered: