Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/usr.sbin/pf/Makefile.inc

15 lines
429 B
PHP
Raw Normal View History

add support for new GCC 9 warnings that may be too much to fix right now. new address-of-packed-member and format-overflow warnings have new GCC_NO_ADDR_OF_PACKED_MEMBER amd GCC_NO_FORMAT_OVERFLOW variables to remove these warnings. apply to a bunch of the tree. mostly, these are real bugs that should be fixed, but in many cases, only by removing the 'packed' attribute from some structure that doesn't really need it. (i looked at many different ones, and while perhaps 60-80% were already properly aligned, it wasn't clear to me that the uses were always coming from sane data vs network alignment, so it doesn't seem safe to remove packed without careful research for each affect struct.) clang already warned (and was not erroring) for many of these cases, but gcc picked up dozens more.
2020-09-06 10:20:26 +03:00
# $NetBSD: Makefile.inc,v 1.11 2020/09/06 07:20:32 mrg Exp $
WARNS=1 for pf
2009-04-23 09:25:06 +04:00
WARNS?= 1 # XXX -Wshadow -Wcast-qual -Wsign-compare
Default to -Wno-sign-compare -Wno-pointer-sign for clang. Push -Wno-array-bounds down to the cases that depend on it. Selectively disable warnings for 3rd party software or non-trivial issues to be reviewed later to get clang -Werror to build most of the tree.
2011-05-26 16:56:24 +04:00
CWARNFLAGS.clang+= -Wno-tautological-compare
Disable a couple of warnings until further investigation.
2017-01-11 15:19:43 +03:00
CWARNFLAGS.clang+= -Wno-error=address-of-packed-member
add support for new GCC 9 warnings that may be too much to fix right now. new address-of-packed-member and format-overflow warnings have new GCC_NO_ADDR_OF_PACKED_MEMBER amd GCC_NO_FORMAT_OVERFLOW variables to remove these warnings. apply to a bunch of the tree. mostly, these are real bugs that should be fixed, but in many cases, only by removing the 'packed' attribute from some structure that doesn't really need it. (i looked at many different ones, and while perhaps 60-80% were already properly aligned, it wasn't clear to me that the uses were always coming from sane data vs network alignment, so it doesn't seem safe to remove packed without careful research for each affect struct.) clang already warned (and was not erroring) for many of these cases, but gcc picked up dozens more.
2020-09-06 10:20:26 +03:00
CWARNFLAGS.gcc+= ${GCC_NO_ADDR_OF_PACKED_MEMBER}
move common fragments into Makefile.inc.
2004-11-11 15:03:53 +03:00
use strtonum from libc
2015-01-29 06:31:35 +03:00
CPPFLAGS+= -D_OPENBSD_SOURCE
move common fragments into Makefile.inc.
2004-11-11 15:03:53 +03:00
move pf reachover makefiles into usr.sbin/pf. ok'ed by itojun. before: sbin/pfctl usr.sbin/authpf usr.sbin/spamdb libexec/ftp-proxy libexec/spamd libexec/spamd-setup libexec/spamlogd after: usr.sbin/pf/pfctl usr.sbin/pf/authpf usr.sbin/pf/spamdb usr.sbin/pf/ftp-proxy usr.sbin/pf/spamd usr.sbin/pf/spamd-setup usr.sbin/pf/spamlogd
2004-11-11 14:54:51 +03:00
.if exists(${.CURDIR}/../../Makefile.inc)
.include "${.CURDIR}/../../Makefile.inc"
.endif
Add new Makefile knob, USE_FORT, which extends USE_SSP by turning on the FORTIFY_SOURCE feature of libssp, thus checking the size of arguments to various string and memory copy and set functions (as well as a few system calls and other miscellany) where known at function entry. RedHat has evidently built all "core system packages" with this option for some time. This option should be used at the top of Makefiles (or Makefile.inc where this is used for subdirectories) but after any setting of LIB. This is only useful for userland code, and cannot be used in libc or in any code which includes the libc internals, because it overrides certain libc functions with macros. Some effort has been made to make USE_FORT=yes work correctly for a full-system build by having the bsd.sys.mk logic disable the feature where it should not be used (libc, libssp iteself, the kernel) but no attempt has been made to build the entire system with USE_FORT and doing so will doubtless expose numerous bugs and misfeatures. Adjust the system build so that all programs and libraries that are setuid, directly handle network data (including serial comm data), perform authentication, or appear likely to have (or have a history of having) data-driven bugs (e.g. file(1)) are built with USE_FORT=yes by default, with the exception of libc, which cannot use USE_FORT and thus uses only USE_SSP by default. Tested on i386 with no ill results; USE_FORT=no per-directory or in a system build will disable if desired.
2007-05-28 16:06:17 +04:00
USE_FORT?=yes # network client *and* setuid