I get the following error when I try to build nginx 1.7.10 against
boringssl
latest revision :
cc -c -pipe -O -W -Wall -Wpointer-arith -Wno-unused-parameter -Werror
-g -I
/usr/local/boringssl/include -I/usr/include -I src/core -I src/event -I
src/event/modules -I src/os/unix -I objs
-o objs/src/event/ngx_event_openssl.o
src/event/ngx_event_openssl.c
src/event/ngx_event_openssl.c: In function ‘ngx_ssl_connection_error’:
src/event/ngx_event_openssl.c:1896:21: error:
‘SSL_R_BLOCK_CIPHER_PAD_IS_WRONG’ undeclared (first use in this
function)
src/event/ngx_event_openssl.c:1896:21: note: each undeclared identifier
is
reported only once for each function it appears in
I’ve fixed the build by removing l:1896 from ngx_event_openssl.c but I
don’t know if it’s recommended …
They didn’t release yet so I just cloned the repo !
Sorry, I was thinking about libressl instead.
BoringSSL removed SSL_R_BLOCK_CIPHER_PAD_IS_WRONG return
errors in commits 1e52ecac4d and 29b186736c, and the definition was
finally removed in commit 689be0f4b7, which is what breaks the build
here.
You can workaround this by &ifdef’ing the line in ngx_event_openssl.c
out, nothing bad will happen because of this.
Not sure if it still makes sense to workaround every single build
breakage
caused by upstream boringssl changes in nginx, seems like a never
ending cat and mouse game.
Lukas
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.