TheBinitGhimire / NtHiM

Now, the Host is Mine! - Super Fast Sub-domain Takeover Detection!
https://whoisbinit.me/NtHiM/
MIT License
357 stars 64 forks source link

[FAQ] What to do if I get "failed to run custom build command for `openssl-sys v ...`" error? #1

Open TheBinitGhimire opened 3 years ago

TheBinitGhimire commented 3 years ago

Some users might get an error that says the following:

failed to run custom build command for `openssl-sys v ...`

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)

brew install openssl@1.1

macOS (MacPorts)

sudo port install openssl

macOS (pkgsrc)

sudo pkgin install openssl

Arch Linux

sudo pacman -S pkg-config openssl

Debian and Ubuntu

sudo apt-get install pkg-config libssl-dev

Fedora

sudo dnf install pkg-config openssl-devel

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)

TheBinitGhimire commented 3 years ago

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, Binit Ghimire (@TheBinitGhimire)

saikumar9121 commented 3 years ago
error[E0658]: use of unstable library feature 'slice_strip' --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/os_str_bytes-4.2.0/src/raw_str.rs:605:16 605 self.0.strip_prefix(pat).map(Self::from_raw_bytes_unchecked) ^^^^^^^^^^^^
= note: see issue #73413 <https://github.com/rust-lang/rust/issues/73413> for more information
error[E0658]: use of unstable library feature 'slice_strip' --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/os_str_bytes-4.2.0/src/raw_str.rs:635:16 635 self.0.strip_suffix(pat).map(Self::from_raw_bytes_unchecked) ^^^^^^^^^^^^
= note: see issue #73413 <https://github.com/rust-lang/rust/issues/73413> for more information
error[E0658]: use of unstable library feature 'slice_strip' --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/os_str_bytes-4.2.0/src/raw_str.rs:726:39 726 impl_trim_matches!(self, pat, strip_suffix) ^^^^^^^^^^^^
= note: see issue #73413 <https://github.com/rust-lang/rust/issues/73413> for more information
error[E0658]: use of unstable library feature 'slice_strip' --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/os_str_bytes-4.2.0/src/raw_str.rs:749:39 749 impl_trim_matches!(self, pat, strip_prefix) ^^^^^^^^^^^^
= note: see issue #73413 <https://github.com/rust-lang/rust/issues/73413> for more information

For more information about this error, try rustc --explain E0658. error: could not compile os_str_bytes due to 4 previous errors warning: build failed, waiting for other jobs to finish... error: failed to compile NtHiM v0.1.2, intermediate artifacts can be found at /tmp/cargo-installxBNBb8

Caused by: build failed

TheBinitGhimire commented 3 years ago

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, @TheBinitGhimire

nukats commented 1 year ago

NtHiM -t https://example.example.com -v [ERROR] An error occured for [https://example.example.com].

How to troubleshoot?