Hello,

I don't now what your current plans for supporting BoringSSL are, but its
API has been fairly stable for a while and this is the only change required
to make NGINX build with it again (the other issue with error definitions was
fixed in BoringSSL itself).

I don't think BoringSSL is going to change the API back, so NGINX migh want
to fix this if support for BoringSSL is desired (again, don't know your
opinion on this).

Please have a look and let me know what you think.

Cheers

_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel