Sorry, I used the wrong email format. I will be more careful next time. By the way, another person successfully compiled using GCC version 13 on Alpine. ------- Best regards, JINZE YANG
> 2025年5月14日 17:45，JINZE YANG <y...@r2wind.org> 写道： > > 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 > >> 2025年5月14日 17:24，Sergey A. Osokin <o...@freebsd.org.ru> 写道： >> >> Hi there, >> hope you're doing well. >> >> Thanks for the report! >> >> On Wed, May 14, 2025 at 10:34:05AM +0800, 杨金泽 wrote: >>> It seems that BoringSSL has updated some of its interfaces, causing the >>> following issues during the compilation of Nginx. Is there currently any >>> solution to resolve this problem? Or are there other libraries that can >>> perfectly replace BoringSSL? The commands and error messages are as >>> follows: >> >> I've just tried to build nginx on FreeBSD 14.2-RELEASE-p3 with a recent >> snapshot of boringssl, and that it just works, here's the proof link. >> https://people.freebsd.org/~osa/nginx-devel-1.28.0_2.log >> >> It's unclear from your email: >> - what is the nginx version you were trying to build; >> - what is the boringssl version/tag; >> >> Also, please follow the netiquette rules for mailing lists, >> https://www.openbsd.org/mail.html, and keep your emails in plain text >> with 72 characters per line. >> >> Thank you. >> >> -- >> Sergey A. Osokin >> _______________________________________________ >> nginx mailing list >> nginx@nginx.org >> https://mailman.nginx.org/mailman/listinfo/nginx >
_______________________________________________ nginx mailing list nginx@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx
