-
Notifications
You must be signed in to change notification settings - Fork 213
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
multiple rlib candidates for compiler_builtins
found
#334
Comments
Are you using |
Yes I'm using Not adding compiler_builtins as a dependency leads to |
It seems that the |
Rust actually pins |
(sorry, I deleted a comment in-between, as I realized what you said) I think my issue is rust-lang/wg-cargo-std-aware#15 and rust-lang/wg-cargo-std-aware#28 I don't really understand why the |
I think this is likely a bug with |
Reopened as rust-lang/wg-cargo-std-aware#53 |
Hi is there a solution for this already? I face a similar issue when building for a custom target with -Zbuild-std=core,alloc and providing compiler_builtins as dependency in Cargo.toml file. Any help much appreciated. Thanks |
@AthiraRamakrishna this has been closed for a long time. Could you open a new issue describing what you are trying and what problem you are experiencing? |
Sorry if this is not the right place to report this issue.
After upgrading to the latest nightly, my
no_std
project suddenly stopped compiling with this error:I'm following the instructions in
README.md
which ask you to addcompiler_builtins
as a dependency and addextern crate compiler_builtins;
.It seems that Rust indeed passes
compiler_builtins
twice when compiling the crate. Here's a fragment of the invocation ofrustc
:Interestingly, if I do that in Cargo.toml:
And then
extern crate compiler_builtins_under_a_different_name;
, then everything works fine on some platforms but gives linking errorsforformemcpy
memcmp
on some others.The text was updated successfully, but these errors were encountered: