Commit Graph

10 Commits

Author SHA1 Message Date
Moritz Bunkus
c78177e99b build system: use version number comparison for -Wshadow-compatible-local test
clang++ doesn't error out on unknown flags, it only spews
warnings. Therefore AC_TRY_COMPILE is useless for detecting support
for it.
2018-04-17 23:41:32 +02:00
Moritz Bunkus
9eaf235c76 build system: only use -Wshadow-compatible-local if compiler supports it 2018-04-17 23:28:50 +02:00
Moritz Bunkus
9de81581f2 configure: enable strong stack protection for clang >= 3.5.0 2017-11-18 10:46:36 +01:00
Moritz Bunkus
cd155df59b configure rework compiler type & version check 2017-11-18 10:46:36 +01:00
Moritz Bunkus
de093c2913 configure: get real version for clang(++)
`clang++ -dumpversion` always outputs 4.2.1 as it was designed to be
compatible with `g++` in that version. So parse `clang++ --version`
for `clang++` instead.
2017-11-17 21:49:36 +01:00
Moritz Bunkus
94eb9af366 build system: enable gcc's stack protection
Implements #1370.
2015-08-11 15:02:58 +02:00
Moritz Bunkus
3b8458f38d build system: compile without maybe-uninitialized warnings for gcc
See e.g.
http://stackoverflow.com/questions/21755206/how-to-get-around-gcc-void-b-4-may-be-used-uninitialized-in-this-funct
2015-05-23 19:45:35 +02:00
Moritz Bunkus
2fcc79b00c build system: check for and turn off some new warnings from clang++ 3.6
These warnings include -Winconsistent-missing-override and
-Wpotentially-evaluated-expression which are both triggered by code out
of my control (Qt and wxWidgets).
2015-03-25 17:51:30 +01:00
Moritz Bunkus
da654e7ea7 build system: add -Wlogical-op warning flag for gcc 4.8.x 2013-10-26 12:52:22 +02:00
Moritz Bunkus
5de88ec536 build system: move compiler warning flag checks to their own file 2013-10-26 12:52:22 +02:00