-
Notifications
You must be signed in to change notification settings - Fork 218
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
#388
Comments
Got the same error when I was complying for avr-atmega328p.
|
maybe this helps: [build]
rustflags = [
"-C", "link-self-contained=no",
] |
I have a similar problem and the compiler flag doesn't help. |
This workaround works for me: add [unstable]
build-std = ["core", "alloc"]
build-std-features = ["compiler-builtins-mangled-names"] to [dependencies]
compiler_builtins_local = { path = "../../compiler-builtins", package = "compiler_builtins" } to
to the top of |
I am not quite sure this was intended to work with -Zbuild-std. At the very least it wouldn't be possible to provide any stability guarantees as a codegen backend is free to depend on new intrinsics from compiler-builtins. |
This is a pretty old issue and it seems like there are solutions, so I will close this. |
Add exhaustive/extensive tests
I'm having a similar issue to #334 but it's different I think. I have
build-std = ["core", "alloc"]
in config.toml and I'm trying to compile a local patch of compiler-builtins, for the reasons stated in #387 . In Cargo.toml I have the following configuration:But the compiler is giving the error:
I believe one version is the one included by default by cargo because of
core
in https://github.com/rust-lang/cargo/blob/master/src/cargo/core/compiler/standard_lib.rs#L28, whereas the second one is my patch. How do I opt-out the cargo-inserted one?The text was updated successfully, but these errors were encountered: