From a90c5ef6e2223ecfb02932d9233403591e28aebc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jo=C3=A3o=20Valverde?= Date: Thu, 7 Apr 2016 19:00:19 +0100 Subject: Revert "Try to suppress a compiler feature that goes wrong." MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This reverts commit ec075789e31942008eb8ad7faf35b7012778dac8. Change-Id: I6f84f01f2027f32d3727dd9d7d097d6d90e063c2 Reviewed-on: https://code.wireshark.org/review/14851 Reviewed-by: João Valverde --- configure.ac | 16 ---------------- 1 file changed, 16 deletions(-) diff --git a/configure.ac b/configure.ac index 1dbe9fd6b9..87ea6e4632 100644 --- a/configure.ac +++ b/configure.ac @@ -882,22 +882,6 @@ AC_WIRESHARK_COMPILER_FLAGS_CHECK(-Wno-long-long) AC_WIRESHARK_COMPILER_FLAGS_CHECK(-Wheader-guard) AC_WIRESHARK_COMPILER_FLAGS_CHECK(-Wunused-const-variable) # -# Either the version of clang on the "clang code analysis" buildbot is -# horribly broken, or the header files on that buildbot are horribly -# broken, as the perfectly-legitimate statement -# -# if( strcmp(argv[i],"--")==0 ) dashdash = 1; -# -# is getting stoopid "array index 3 is past the end of the array (which -# contains 3 elements)" complaints from the compiler. -# -# The macro for strcmp() in glibc(?) really seems to give C compilers -# conniptions; I think I've seen crap from GCC as well with that macro. -# -# So, alas, suppress the compile-time array bounds checks. -# -AC_WIRESHARK_COMPILER_FLAGS_CHECK(-Wnoarray-bounds) -# # The following are C only, not C++ # AC_WIRESHARK_COMPILER_FLAGS_CHECK(-Wc++-compat, C) -- cgit v1.2.3