-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
[FAQ] What to do if I get "failed to run custom build command for openssl-sys v ...
" error?
#1
Comments
Adding the following line under [dependencies] in the Cargo.toml file can simply resolve the issue: openssl = { version = "0.10", features = ["vendored"] } But, this would make the NtHiM executable binary consume more memory due to OpenSSL being built into it. Therefore, I haven't included it inside the file. You might be interested in adding this line into the file in case you are interested in modifying NtHiM to build something more interesting. Thanks, |
error[E0658]: use of unstable library feature 'slice_strip' error[E0658]: use of unstable library feature 'slice_strip' error[E0658]: use of unstable library feature 'slice_strip' error[E0658]: use of unstable library feature 'slice_strip' For more information about this error, try Caused by: |
Hello @saikumar9121, Would you mind letting me know about your system? Also, using what method are you trying to install NtHiM? I just tried doing a fresh install on a clean, new Debian 10 instance on amd64 with only Rustup installed, and the installation was successful both through crates.io and manual building. So, I would love to know about the system where you were trying to install and faced this issue. Thanks, |
NtHiM -t https://example.example.com -v How to troubleshoot? |
Some users might get an error that says the following:
Due to this error, the Cargo build or installation process for NtHiM might be stopped. But, there is a fix for this issue, and it is clearly mentioned at the Docs.rs documentation for openssl, which can be found here: https://docs.rs/openssl/0.10.34/openssl/
If you are one of the victims of this issue, then I would suggest you to use the following commands to resolve the issue for your respective platform.
macOS (Homebrew)
macOS (MacPorts)
macOS (pkgsrc)
Arch Linux
Debian and Ubuntu
Fedora
By performing one of these actions, the issue might be resolved in your case. If this doesn't resolve the issue, please let me know!
Thanks,
Binit Ghimire (@TheBinitGhimire)
The text was updated successfully, but these errors were encountered: