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

native library `openssl` is being linked to by more than one package, and can only be linked to by one package #886

Closed
seanmonstar opened this Issue Nov 15, 2014 · 13 comments

Comments

Projects
None yet
5 participants
@seanmonstar

seanmonstar commented Nov 15, 2014

native library `openssl` is being linked to by more than one package, and can only be linked to by one package
  openssl-sys v0.0.1 (https://github.com/alexcrichton/openssl-sys#d66fe840)
  openssl-sys v0.0.1 (https://github.com/sfackler/rust-openssl#fa42ed9e)

Affects master of hyper

@alexcrichton

This comment has been minimized.

Member

alexcrichton commented Nov 16, 2014

This is actually by design, the two libs can't both be linked to, one of them needs to be pruned out (in this case alexcrichton/openssl-sys should be deprecated at least)

@seanmonstar

This comment has been minimized.

seanmonstar commented Nov 17, 2014

Is there any way to deal with this? How do I figure out which dependency included the openssl-sys?

@alexcrichton

This comment has been minimized.

Member

alexcrichton commented Nov 17, 2014

You can take a look at Cargo.lock and see what libraries has alexcrichton/openssl-sys in its dependencies key

@seanmonstar

This comment has been minimized.

seanmonstar commented Nov 17, 2014

Ok, so its in curl-rust. Is the solution to ask curl-rust to change it's dep to rust-openssl? Or is there something I can configure to get around it in the meantime?

I've tried putting in my .cargo/config:

[target.x86_64-unknown-linux-gnu.openssl-sys]
git = "https://github.com/sfackler/rust-openssl"

But doesn't seem to help.

@alexcrichton

This comment has been minimized.

Member

alexcrichton commented Nov 17, 2014

Yes you'll need curl-rust to update (which it has now). The section you've put in .cargo/config isn't quite how that's supposed to work, see the documentation for why.

@Ryman

This comment has been minimized.

Ryman commented Dec 3, 2014

Should this be re-opened as the error message doesn't really help the user figure out which packages are responsible for the clash, or is the preference for a new issue to be logged?

@alexcrichton

This comment has been minimized.

Member

alexcrichton commented Dec 3, 2014

@Ryman could you open another issue?

@Ryman

This comment has been minimized.

Ryman commented Dec 3, 2014

@alexcrichton Opened #1006 to track.

@alexcrichton

This comment has been minimized.

Member

alexcrichton commented Dec 3, 2014

Thanks @Ryman!

@softprops

This comment has been minimized.

softprops commented Apr 6, 2015

This just started happening to me recently as well.

@dbrgn

This comment has been minimized.

Contributor

dbrgn commented Dec 2, 2015

I'm also having this problem on Travis recently (https://travis-ci.org/coredump-ch/spaceapi-server-rs/jobs/94403932). The thing is, I cannot reproduce this locally, even after deleting Cargo.lock and the target directory. Any ideas?

Edit: Never mind, I was on the wrong branch. Can reproduce this now.

@alexcrichton

This comment has been minimized.

Member

alexcrichton commented Dec 2, 2015

@dbrgn that basically means that something in the graph is requiring 0.6 and something else is requiring 0.7, to fix the issue you'll need to make sure that everyone works with one or the other

@dbrgn

This comment has been minimized.

Contributor

dbrgn commented Dec 2, 2015

Yep, that was the case :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment