Closed sghazagh closed 7 years ago
I am trying to compile the latest OpenELEC 8.0 release. Compile stops at "libressl" and here is the error message?
GET libressl --2017-04-14 08:44:37-- http://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-2.4.5.tar.gz Resolving ftp.openbsd.org (ftp.openbsd.org)... 129.128.5.191 Connecting to ftp.openbsd.org (ftp.openbsd.org)|129.128.5.191|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 3016462 (2.9M) [text/plain] Saving to: 'sources/libressl/libressl-2.4.5.tar.gz' libressl-2.4.5.tar.gz 100%[===================================================================================================================================================================>] 2.88M 345KB/s in 10s 2017-04-14 08:44:48 (282 KB/s) - 'sources/libressl/libressl-2.4.5.tar.gz' saved [3016462/3016462] UNPACK libressl APPLY PATCH (common) /OpenElec/OpenELEC-8.0/packages/security/libressl/patches/libressl-add_trusted-first_option.patch patching file apps/openssl/apps.c Hunk #1 succeeded at 1943 (offset -415 lines). patching file crypto/x509/x509_vfy.c Hunk #1 succeeded at 208 with fuzz 2 (offset 2 lines). patching file include/openssl/x509_vfy.h patch unexpectedly ends in middle of line APPLY PATCH (common) /OpenElec/OpenELEC-8.0/packages/security/libressl/patches/libressl-cmake-pkgconfig.patch patching file CMakeLists.txt APPLY PATCH (common) /OpenElec/OpenELEC-8.0/packages/security/libressl/patches/libressl-dont-check-and-use-getentropy.patch patching file CMakeLists.txt FIXCONFIG build.OpenELEC-RPi2.arm-8.0.0/libressl-2.4.5/ FIXCONFIG build.OpenELEC-RPi2.arm-8.0.0/libressl-2.4.5/scripts/ BUILD libressl (host) scripts/build: line 213: cmake: command not found Makefile:10: recipe for target 'image' failed make: *** [image] Error 127
Any fix for that?
I found it!!! Don't know why I didn't have "cmake" installed. Anyway, I have installed "cmake" and it is continuing for compilation...
I am trying to compile the latest OpenELEC 8.0 release. Compile stops at "libressl" and here is the error message?
Any fix for that?