Hi Jeff,
You are right, nginx does use different libraries when running, and
after I replaced the original library files, nginx returned to normal.
On Tue, Feb 20, 2024 at 10:19 PM Jinze YANG https://mailman.nginx.org/mailman/listinfo/nginx>> wrote:
>>* After I built libssl as a shared library, t
On Tue, Feb 20, 2024 at 10:19 PM Jinze YANG wrote:
>
> After I built libssl as a shared library, the compilation could be completed
> normally, but I encountered some problems after compilation. The details are
> as follows:
> root@VM-8-12-debian /www/server/nginx/sbin # ./nginx -t
> ./nginx: sy
Hello,
After I built libssl as a shared library, the compilation could be
completed normally, but I encountered some problems after compilation.
The details are as follows:root@VM-8-12-debian /www/server/nginx/sbin
# ./nginx -t
./nginx: symbol lookup error: ./nginx: undefined symbol: SSL_library_in
> On 20 Feb 2024, at 09:22, 杨金泽 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
Hi,
I have attached this file, please check it out.
---
> Hi,
>
> Your boringssl paths look ok.
>
> What's in objs/autoconf.err ?
>
> > On 20 Feb 2024, at 12:29, Jinze YANG wrote:
> >
> > Hello,
> > As you can see, boringssl's libcrypto.a and l
Hi,
Your boringssl paths look ok.
What's in objs/autoconf.err ?
> On 20 Feb 2024, at 12:29, Jinze YANG wrote:
>
> Hello,
> As you can see, boringssl's libcrypto.a and libssl.a are in two separate
> directories, as shown below:
> root@VM-8-12-debian ~/boringssl/build # ls
> bssl CMakeCache.txt
Hello,
As you can see, boringssl's libcrypto.a and libssl.a are in two separate
directories, as shown below:
root@VM-8-12-debian ~/boringssl/build # ls
bssl CMakeCache.txt cmake_install.cmake crypto_test decrepit
embed_test_data_args.txt libpki.a pki_test ssl_test urandom_test
build.ninja CMakeFile
