-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
A linkage error when running tests relying on a sys crate #3200
Comments
Yep, looks like it. Will investigate.
Before:
After:
|
@matklad, thanks for the help! Please note also that the job in question had a custom feature enabled, not the default one:
By default, it’s |
bors
added a commit
that referenced
this issue
Oct 17, 2016
Pass target environment for rustdoc This should fix #3200, but I am not sure that this is a correct fix, and I need some input to figure this out. `rustdoc` is invoked in two places, in `cargo_test.rs` and in `cargo_rustc/mod.rs`. Before the refactoring PR, these invocations used different LD_LIBRARY paths. [The one in cargo_rustc](https://github.com/rust-lang/cargo/pull/3198/files#diff-59acd1a3101aebbb591ac7ab51c19d9eR427) used "host" version, while [the one in cargo_test](https://github.com/rust-lang/cargo/blob/a8baa5b8f36e88170c8c56523b6eb72efc2cc55e/src/cargo/ops/cargo_test.rs#L131) used "target" version. The original PR changed both to "host", this PR switches both to "target". Is this correct, or should we stick with different environments for building documentation and doctests?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is a crate that depend on a sys crate. The crate has documentation tests and benchmarks. The tests used to compile and pass on nightly a couple of days back, but they fail to do so right now. The benchmarks work just fine in both cases. The error is due to linkage:
The versions of Rust and Cargo that don’t have this issue are as follows:
The versions of Rust and Cargo that have this issue are as follows:
Here is how it looks on Travis CI: before and after.
I’m wondering if it’s indeed due to the latest changes in Rust and/or Cargo, or it’s a problem with the crate itself. Let me know if the rust repository is a better fit for this issue. Thank you.
Regards,
Ivan
The text was updated successfully, but these errors were encountered: