osmocom
/
wireshark
14
0
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity

Revert "Try to suppress a compiler feature that goes wrong." 

This reverts commit ec075789e3.

Change-Id: I6f84f01f2027f32d3727dd9d7d097d6d90e063c2
Reviewed-on: https://code.wireshark.org/review/14851
Reviewed-by: João Valverde <j@v6e.pt>
This commit is contained in:
João Valverde 2016-04-07 19:00:19 +01:00 committed by João Valverde
parent 08e01a6aeb
commit a90c5ef6e2
1 changed files with 0 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
configure.ac
View File

@ -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)