error: native library `openssl` is being linked to by more than one version of the same package

问题

I'm facing this problem when I try to cargo build:

error: native library openssl is being linked to by more than one version of the same package, but it can only be linked once; try updating or pinning your dependencies to ensure that this package only shows up once

openssl-sys v0.6.7

openssl-sys v0.7.13

Cargo and Rust versions:

$ cargo --version
cargo 0.11.0-nightly (3ff108a 2016-05-24)

$ rustc --version
rustc 1.11.0-nightly (7746a334d 2016-05-28)

Files:

• Cargo.toml

• Cargo.lock

can't get why this doesn't compile and how to solve this problem. Thank you!

回答1:

The way that linking works, you can only have a single version of a native library linked, otherwise you end up with duplicate symbols. Cargo's links manifest key helps prevent you from accidentally linking to the same set of symbols twice.

To solve it, you need to read through your Cargo.lock (it's not a difficult file format to understand). Find the crates that have the offending library as a dependency and note which ones have conflicting versions.

Then you have to manually resolve your dependencies so that their dependencies use the same version of the native library.

---

In this case, the important aspects of the dependency chain are:

server (0.0.1) => cookie (0.2.4) => openssl (0.7.13)
               => hyper (0.6.16) => cookie (0.1.21) => openssl (0.6.7)

To fix it, modify your Cargo.toml to use the same version of cookie as hyper. Then you will implicitly get the same version of openssl.

To be honest, this is one of the roughest parts of Rust at the moment. At least this version of the "multiple different versions of the same crate" strangeness provides a straight-forward Cargo error.

来源：https://stackoverflow.com/questions/43882354/native-library-glib-is-being-linked-to-by-more-than-one-package-and-can-only