From 366a548229890a94e37fdfc15619749b5f98e218 Mon Sep 17 00:00:00 2001 From: Alexander Traud Date: Fri, 12 Jan 2018 10:17:04 +0100 Subject: [PATCH] BuildSystem: Really do not pass unknown-warning options to the compiler. When an older GCC version is called with a too new warning option, GCC exited with an error and Asterisk was not built. Therefore, the configure script tests the installed compiler whether it supports that warning option. If not, Asterisk does not pass it to the installed compiler. However, some compilers (like clang) do not exit (error) but give just a warning in such a case. Because the compiler did not exit, Asterisk passed the unknown-warning option. ASTERISK-27560 Change-Id: Ia9d148e689c173df4e91699113605dab2de36038 --- third-party/pjproject/patches/user.mak | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/third-party/pjproject/patches/user.mak b/third-party/pjproject/patches/user.mak index dafb259198..b7eab52709 100644 --- a/third-party/pjproject/patches/user.mak +++ b/third-party/pjproject/patches/user.mak @@ -1,4 +1,4 @@ -NUBSV := $(shell gcc -Wno-unused-but-set-variable -o /dev/null -xc -c - /dev/null && echo -Wno-unused-but-set-variable) +NUBSV := $(shell ${CC} -Wno-unused-but-set-variable -Werror -o /dev/null -xc -c - /dev/null && echo -Wno-unused-but-set-variable) CFLAGS += -fPIC $(NUBSV) -Wno-unused-variable -Wno-unused-label -Wno-unused-function -Wno-strict-aliasing