Open daenney opened 6 years ago
It tries to get the OpenSSL version by an environment variable. I've run env DEP_OPENSSL_VERSION=111 bash
and compiled it.
My build fails at:
go clean -cache || true
cd sigchain && CARGO_RELEASE=--release make libsigchain-with-dashboard
make[1]: Entering directory '/home/hiro/src/kr/sigchain'
if [ "`cargo web --version`" != "cargo-web 0.6.10" ]; then echo "Please install cargo-web 0.6.10 with \`cargo install -f --version 0.6.10 cargo-web\`"; exit 1; fi
# use rsync so that file modifed times are only updated when the contents change
cd dashboard_yew && cargo web deploy --release --target=wasm32-unknown-emscripten && rsync --checksum --delete -r ../target/deploy/* ../target/deploy-final
Downloading emscripten-1.37.27-1-x86_64-unknown-linux-gnu.tgz...
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', libcore/option.rs:345:21
note: Run with `RUST_BACKTRACE=1` for a backtrace.
make[1]: *** [Makefile:25: libsigchain-with-dashboard] Error 101
make[1]: Leaving directory '/home/hiro/src/kr/sigchain'
make: *** [Makefile:50: all] Error 2
Caused by an outdated version of openssl-sys (which is discontinued).
See sigchain/Cargo.toml
[replace."openssl:0.9.23"]
git = "https://github.com/kryptco/rust-openssl"
Thank you for reporting these build issues. As a temporary workaround, version 0.6.10 of cargo-web can be installed by installing openssl-1.0
and then pointing rust-openssl to it:
$ sudo pacman -S openssl-1.0
$ env OPENSSL_INCLUDE_DIR=/usr/include/openssl-1.0 OPENSSL_LIB_DIR=/usr/lib/openssl-1.0/ DEP_OPENSSL_VERSION=101 cargo install -f --version 0.6.10 cargo-web
After running these commands, makepkg
should complete successfully. We are working on updating the PKGBUILD to use a later version of cargo-web and reqwest
As a side note, rust-openssl 0.9.x does not correspond with the OpenSSL version being linked. When building cargo-web (which is the step @daenney is failing on), rust is linking your system OpenSSL. This version of cargo-web only supports up to OpenSSL 1.0.x, which the steps above install and expose.
Alright I feel really dumb now ;). I should have tried to install an older version of openssl. Instead, I've stared ripping sigchain out of kr, which was partially successful. Thank you.
This is still happening. I'm a little wary about the security consequences of depending on an outdated OpenSSL version...?
This is still happening. I'm a little wary about the security consequences of depending on an outdated OpenSSL version...?
Same doubts by me...
We're working on updating the dependency and making a version of kr
available that doesn't depend on cargo-web at all. In the mean time, this should not be a worry though because cargo-web is used only for the Krypton Teams dashboard which runs locally in the browser and does not make any remote network requests. If you're not using it then there's even less to worry about. See @kcking's previous comment.
Though it's not necessarily a security risk it does mean kr is currently non-buildable, since not everyone keeps multiple version of OpenSSL around in their distros package repositories. Given there's a solution for Arch it would be lovely if someone updated the PKGBUILD in the meantime.
Could you perhaps do what Parity did and force a newer dependency: https://github.com/paritytech/substrate/pull/913/files ? That should fix the issue without needing to wait for anyone else.
Hello i have this error when compile project with cargo
help please
Compiling generic-array v0.9.0
error: failed to run custom build command for openssl v0.9.24
Caused by:
process didn't exit successfully: /usr/src/app/target/release/build/openssl-0d6c67a3035cbfcf/build-script-build
(exit code: 101)
--- stderr
thread 'main' panicked at 'Unable to detect OpenSSL version', /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/openssl-0.9.24/build.rs:16:14
note: run with RUST_BACKTRACE=1
environment variable to display a backtrace.
The command '/bin/sh -c cargo build --release' returned a non-zero code: 101 skipped
I can't seem to build 2.4.12 (using the PKGBUILD on AUR). I'm also weirded out by the fact it tries to link against OpenSSL 0.9.x?