Hello,
After testing, when compiling BoringSSL, on the test machine with GCC 12,
you need to execute the command `sed -i 's/-Werror/-Werror -Wno-array-bounds/'
CMakeLists.txt`
for it to compile successfully. However, no issues were encountered during
compilation with GCC 13.
--
Best regard
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 thi
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
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 写道：
>
> Hello,
> Today, I pulled the latest branch from GitHub. Below
> are the
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
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:
ro
