-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 passed to rustdoc #5650
Labels
C-bug
Category: bug
Comments
Sorry about that, there is a test specifically for this case, but it didn't quite catch this particular issue (it's a complex interaction between having build scripts, dependencies, and using |
ehuss
added a commit
to ehuss/cargo
that referenced
this issue
Jun 26, 2018
Fixes rust-lang#5650. cc rust-lang#5435 As part of my recent work on profiles, I introduced some situations where a library can be compiled multiple times with different settings. Doctests were greedily grabbing all dependencies for a package, regardless of which target is was for. This can cause doctests to fail if it links multiple copies of the same library. One way to trigger this is `cargo test --release` if you have dependencies, a build script, and `panic="abort"`. There are other (more obscure) ways to trigger it with profile overrides.
bors
added a commit
that referenced
this issue
Jul 5, 2018
Fix doctests linking too many libs. Fixes #5650. cc #5435 As part of my recent work on profiles, I introduced some situations where a library can be compiled multiple times with different settings. Doctests were greedily grabbing all dependencies for a package, regardless of which target is was for. This can cause doctests to fail if it links multiple copies of the same library. One way to trigger this is `cargo test --release` if you have dependencies, a build script, and `panic="abort"`. There are other (more obscure) ways to trigger it with profile overrides.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Starting with Rust 1.27, we're seeing duplicate rlibs passed to rustdoc for the
miniz_oxide_c_api
crate.https://kojipkgs.fedoraproject.org/work/tasks/1896/27791896/build.log
Rust 1.26 was fine, and I can reproduce the issue up through nightly.
It's easy to reproduce by checking out https://github.com/Frommi/miniz_oxide, for the current master at commit 10c070c61b2d412358196db1e83f48f3b7422d7e.
This does not happen with plain
cargo test
. We generally usecargo test --release
in Fedora rpm builds to try and test the same artifacts produced in the rpm%build
step, but it looks likepanic = "abort"
is throwing a wrench in things.The text was updated successfully, but these errors were encountered: