-
Notifications
You must be signed in to change notification settings - Fork 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
Linking liblibc with musl target fails with the new nightlies #529
Comments
I've also recently been seeing weird things, although it's not the same error message, so I'm not sure if it's related:
See: https://travis-ci.org/BurntSushi/ripgrep/jobs/203183624 |
Trying to pinpoint which nightly breaks it. |
So, |
Here's a minified, dockerized regression test that doesn't compile. (Try with |
I believe this is not the fault of libc itself, but rather the way we distribute binaries, so closing in favor of rust-lang/rust#39979 (I'll investigate soon) |
Thanks @alexcrichton :-) |
* Add few ARM DSP Intrinsics - Signed saturating add/sub - Saturating four 8-bit integer add/sub - Saturating two 8-bit integer add/sub The intent is mainly to setup the module and to add all the rest in the future. Listed intrinsics are available on Cortex-M too (+dsp is required on some model except for M4). * Arm DSP: rebase and remove portable vector types Rebase everything on top of master since the portable vector types have been removed.
Not sure if this belongs in the Rust repo issues or here, but anyway.
When building with
nightly-2017-02-19
(on a Linux host) and with targetx86_64-unknown-linux-musl
, the error message is as following:With
nightly-2017-02-13
it builds without problems.The text was updated successfully, but these errors were encountered: