On Wed, May 14, 2025 at 05:45:42PM +0800, JINZE YANG via nginx wrote: > Hello, > Today, I pulled the latest branch from GitHub. Below > are the corresponding commits: > boringssl: 89973806bc2ef652189e157f2736a7d32229c404 > nginx: f3542500b6d74e3e88fc84b88144afe67882d1fa > Someone mentioned that this might be related to the GCC version. It > seems GCC 13 does not have issues, but I have not yet had the chance > to verify this. > Best regards, > JINZE YANG
I want to let you know, that I've just successfully built: - version 1.28.0 - boringssl with google-boringssl-0.0.0.0.2025.05.13.01-8997380_GH0.tar.gz (recent version on GH, https://github.com/google/boringssl/commits/main/) - Alpine Linux v3.21 - gcc version 14.2.0 (Alpine 14.2.0) Here's the proof: % LD_LIBRARY_PATH=../boringssl/build objs/nginx -V nginx version: nginx/1.28.0 built by gcc 14.2.0 (Alpine 14.2.0) built with OpenSSL 1.1.1 (compatible; BoringSSL) (running with BoringSSL) TLS SNI support enabled configure arguments: --with-debug --with-http_v3_module --with-cc-opt=-I../boringssl/include --with-ld-opt='-L../boringssl/build -lstdc++' Please follow these instructions, https://nginx.org/en/docs/quic.html. Note that boringssl needs to be built with shared libraries. Thank you. -- Sergey A. Osokin _______________________________________________ nginx mailing list nginx@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx
