Skip to content
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

Downgrading from latest master to 0.6.0, unable to compile #2178

Closed
Chuongv opened this issue Nov 28, 2015 · 3 comments
Closed

Downgrading from latest master to 0.6.0, unable to compile #2178

Chuongv opened this issue Nov 28, 2015 · 3 comments

Comments

@Chuongv
Copy link

Chuongv commented Nov 28, 2015

I originally compiled cargo from source successfully, a few days back off of master. Now I am trying to downgrade to 0.6.0 to since I was having issues with one project, thought that maybe going down would help.

I also originally had rust on latest master, then I went back to the stable branch. Not sure if that matters.

$ rustc -Vv
rustc 1.4.0-dev (8ab8581f6 2015-10-27)
binary: rustc
commit-hash: 8ab8581f6921bc7a8e3fa4defffd2814372dcb15
commit-date: 2015-10-27
host: x86_64-apple-darwin
release: 1.4.0-dev
$ cc --version
Apple LLVM version 7.0.0 (clang-700.1.76)
Target: x86_64-apple-darwin15.0.0
Thread model: posix

Output of make after following the steps from https://github.com/rust-lang/cargo
https://gist.github.com/Chuongv/3dc346ba9fcf7788ac7f

What's weird is that I also wasn't able to do make test on latest master either for cargo.

@Chuongv
Copy link
Author

Chuongv commented Nov 29, 2015

Seems to be similar to alexcrichton/ssh2-rs#23

brew install libssh2
brew install openssl
brew link --force openssl

But still get the same error.

@alexcrichton
Copy link
Member

This basically indicates that the project was compiled against one OpenSSL version and then linked against another. That happens here because compilation uses the homebrew-based OpenSSL but then linking (which picks up /usr/lib via a zlib dependency) ends up using the system OpenSSL, a much older version.

You may have to start out from a new clean build directory if you're using a system libssh2 instead of building one from scratch as well, but that in theory should do the trick!

@Chuongv
Copy link
Author

Chuongv commented Nov 30, 2015

Thanks!

For anyone curious on how to solve this:

make clean
brew link --force openssl

Which should let you build again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants