rust-native & rust-cross: "error: multiple dylib candidates for std found"
#6
Comments
|
|
Unclear if this is solvable with current ie: we want dylibs, but we want to ignore the dylibs that aren't llvm. Rustc's command line doesn't let us do that. Easy solution would be to ignore lib conflicts by selecting the first lib. |
|
It's also possible that we might be able to adjust the hash rustc appends to libraries to include bitbake's PV + PR, which might aleviate our issues. https://github.com/Heather/gentoo-rust/blob/master/dev-lang/rust/rust-1.2.0.ebuild#L50 |
|
Right now my workaround for this ( |
codyps
changed the title
rustc against the system rustc libraries (if any are installed)std found"
codyps
changed the title
std found"std found"
|
rust-lang/rust#14650 might be adaptable to resolve this in rustc directly. |
|
|
It appears to reproduce easily by doing A really bad work-around (that would only fix things for clean sysroots) might be to configure task dependencies to cause both rust variants to wait for the other before installing. |
|
Alternately, a direct reproduction with bitbake: Because this error is being emitted by the rustc snapshot building stage0, we can't resolve this in meta-rust by patching the compiler itself, instead we need to look at adjusting the flags passed to the rustc snapshot to avoid it. |
codyps
referenced
this issue
in codyps/rust
Aug 26, 2015
…BDIR This fixes the case where we try to re-build & re-install rust to the same prefix (without uninstalling) while using an llvm-root that is the same as the prefix. Without this, builds like that fail with: 'error: multiple dylib candidates for `std` found' See https://github.com/jmesmon/meta-rust/issues/6 for some details. May also be related to rust-lang#20342.
bors
referenced
this issue
in rust-lang/rust
Aug 27, 2015
This fixes the case where we try to re-build & re-install rust to the same prefix (without uninstalling) while using an llvm-root that is the same as the prefix. Without this, builds like that fail with: 'error: multiple dylib candidates for `std` found' See https://github.com/jmesmon/meta-rust/issues/6 for some details. May also be related to #20342.
ashie
pushed a commit
to webdino/meta-rust
that referenced
this issue
Nov 23, 2018
…-license-checksum Fix checksums missed in Firefox 38.6.1esr update.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Need to be more careful about how we tell rustc's build process to search for libraries to link against, in particular we need to convince it not to search
${libdir}when doing the initial builds.The problem there is the search of
${libdir}is:target.json(so invocations of the finalrustcto build other things look in${libdir}).The text was updated successfully, but these errors were encountered: