> On 20 Feb 2024, at 09:22, 杨金泽 <rttw...@gmail.com> wrote: > > Hello, > I encountered the following error when using boringssl to build Nginx: > checking for OpenSSL library ... not found > checking for OpenSSL library in /usr/local/ ... not found > checking for OpenSSL library in /usr/pkg/ ... not found > checking for OpenSSL library in /opt/local/ ... not found > ./auto/configure: error: SSL modules require the OpenSSL library. > You can either do not enable the modules, or install the OpenSSL library > into the system, or build the OpenSSL library statically from the source > with nginx by using --with-openssl=<path> option.
Regardless of a pilot error (trimmed), there is indeed a breaking change in BoringSSL, which now expects C++ runtime environment in libssl, see git revision c52806157c97105da7fdc2b021d0a0fcd5186bf3, which basically means it can no longer be used in pure C programs. Someday they will hopefully fix that, meanwhile you may want to: - switch to C++ linker as described in the revision; - build libssl as a shared library (see BUILDING.md in sources); - use some other workarounds when linking with BoringSSL statically, such as explicit linking with libstdc++/libc++. -- Sergey Kandaurov _______________________________________________ nginx mailing list nginx@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx
