Closed KonishchevDmitry closed 4 years ago
I've managed to figure out that it was my broken environment. :( I used brew install openssl
for installing openssl
dependency, but other packages already installed openssl@1.1
as their dependency, brew
didn't complain on having two versions installed and they interfered each other.
Sorry for interruption. Maybe it worth to mention this possible trouble in README.
I, too, can't install cargo-update on macOS Mojave. I have openssl from MacPorts, not from Homebrew. I don't understand why it should interfere with installing cargo-update though. Ideally, the build steps should work either by detecting macOS and pinning OpenSSL library to the system one, or simply by adapting to any available OpenSSL library.
@KonishchevDmitry Apologies for the delay, I must have missed the notification the first time around. Glad you could resolve the issue and I've added this quirk to the README, thanks for sharing!
@ksze I might be able to divine something if you post your build log, but (a) I'm thoroughly unfamiliar with the idiosyncrasies of macos development and (b) we only use openssl as a transitive dependency from git2
, so if you're unable to compile any crate that uses it, you might be better off opening it either there or even further upstream?
Could you please suggest something?