On Wed, Sep 28, 2016 at 03:10:46PM +0100, Alessandro Ghedini wrote:
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.
: Ok, this looks like the real reason for the patch. This looks : like an API change in BoringSSL, and should be threated : accordingly.
: Given the number of various API changes BoringSSL introduces here : and there - we probably don't want to follow, at least till some : version is actually released.