-
Notifications
You must be signed in to change notification settings - Fork 240
32-bit armv7 build fails #89
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
Comments
Ah actually I think this is basically a case where libc 0.2 isn't compatible with older versions of libstd on ARM due to this change, if you update std the error should go away. |
All right, I'll try that and close the issue if that's all there is to it. EDIT:
|
That's a problem with a different crate, actually, and I just published 0.1.7 of that crate so it should fix that problem. Looks like it fixed it for curl, though, so I'm going to close this issue. Thanks for the report! |
Indeed, the filetime crate update was effective but doesn't fix building cargo on arm. Where should I be posting these incremental reports? (opening a new issue for every broken crate is not my idea of fun) |
You can also feel free to submit PRs! |
Hopefully you're not suggesting I should be fixing all this stuff myself? Still, locally speaking, what do you think of this little hack in
|
I'm not sure I quite understand, the amount of effort needed to get cargo working again will be proportional to the number of broken crates, and are you basically saying you'd rather not do that yourself? That's ok, no worries! |
What a relief! ;) I meant keeping these crate-specific reports related to the same issue in one place was definitely a better idea. Due to the number of cargo's dependencies I'd originally thought that would be the right place to start. |
I think it's part of some systemic breakage (libc?) as I had already seen this error before: jeaye/ncurses-rs#99
Built with
rustc 1.6.0-dev (d53496bda 2015-11-06)
My guess about the libc crate was probably right:
https://users.rust-lang.org/t/the-libc-crate-is-now-at-v0-2-0/3509/5
The text was updated successfully, but these errors were encountered: