]> git.ipfire.org Git - thirdparty/openvpn.git/commit
Enable stricter compiler warnings by default
authorSteffan Karger <steffan@karger.me>
Thu, 1 Feb 2018 15:45:21 +0000 (16:45 +0100)
committerGert Doering <gert@greenie.muc.de>
Tue, 20 Feb 2018 09:22:41 +0000 (10:22 +0100)
commitadbf68c00bf40089489c5e039138f855fc5e2392
treec92c765502a8dd39d375dd715777bea134353a8f
parentc215c58f2393e881e16f9805549316a1e257a682
Enable stricter compiler warnings by default

This by default enables the compiler warnings one could previously
enable using the --enable-strict configure option.  I think it is
okay to do so now, because we've taken care of many warnings in the
more standard builds.  (Most of those were totally harmless, but they
prevented us from spotting new more serious mistakes.)

The --enable-strict flag now enables two extra warning flags that I
think can be useful:

-Wsign-compare warns when the compiler promotes a signed type to
unsigned before comparing, which can lead to unexpected behaviour.

-Wuninitialized adds extra warnings about usage of uninitialized variables
or struct elements.

Signed-off-by: Steffan Karger <steffan@karger.me>
Acked-by: Selva Nair <selva.nair@gmail.com>
Message-Id: <20180201154521.7642-1-steffan@karger.me>
URL: https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg16426.html
Signed-off-by: Gert Doering <gert@greenie.muc.de>
configure.ac
m4/ax_check_compile_flag.m4 [new file with mode: 0644]