Hello,

it's shame, we got BoringSSL broken for some time for no reason.

Ilya
From 8aa0885f38147572974e434518f1e4f3ab44398d Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin <[email protected]>
Date: Sun, 11 Oct 2020 23:42:51 +0500
Subject: [PATCH] CI: travis-ci: replace not defined SSL_LIB, SSL_INC for
 BotringSSL builds

after 73b520b958be4ee79b4f09a32d6718a13dc2d1fd variables SSL_LIB, SSL_INC
are not set, but still used by BoringSSL builds. That leads to error
(I wish we could stop on such errors) and using stock openssl instead
of boringssl
---
 scripts/build-ssl.sh | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/scripts/build-ssl.sh b/scripts/build-ssl.sh
index 34eee9bb9..9a6a2b241 100755
--- a/scripts/build-ssl.sh
+++ b/scripts/build-ssl.sh
@@ -103,14 +103,14 @@ if [ ! -z ${BORINGSSL+x} ]; then
 	cmake  -GNinja -DCMAKE_BUILD_TYPE=release -DBUILD_SHARED_LIBS=1 ..
 	ninja
 
-	rm -rf ${SSL_LIB} || exit 0
-	rm -rf ${SSL_INC} || exit 0
+	rm -rf ${HOME}/opt/lib || exit 0
+	rm -rf ${HOME}/opt/include || exit 0
 
-	mkdir -p ${SSL_LIB}
-	cp crypto/libcrypto.so ssl/libssl.so ${SSL_LIB}
+	mkdir -p ${HOME}/opt/lib
+	cp crypto/libcrypto.so ssl/libssl.so ${HOME}/opt/lib
 
-	mkdir -p ${SSL_INC}
-	cp -r ../include/* ${SSL_INC}
+	mkdir -p ${HOME}/opt/include
+	cp -r ../include/* ${HOME}/opt/include
 	)
 fi
 
-- 
2.26.2

Reply via email to