d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
34ae1bb65b
freebsd-dev/share/mk/bsd.sys.mk

95 lines
2.4 KiB
Makefile
Raw Normal View History

Bring in the WARNS directive from NetBSD, localized in a new bsd.sys.mk to avoid polluting sys.mk. This directive controls the addition of compiler warning flags to CFLAGS in a relatively compiler-neutral manner. The idea is that WARNS can be set in Makefile.inc or in individual Makefiles as they become clean, to prevent the introduction of new warnings in the code. -Werror is added by default
2001-05-19 23:18:21 +00:00
# $FreeBSD$
#
# This file contains common settings used for building FreeBSD
# sources.
# Enable various levels of compiler warning checks. These may be
# overridden (e.g. if using a non-gcc compiler) by defining NO_WARNS.
Gcc 3.1 has different -Wx flags.
2002-05-10 01:58:16 +00:00
# for GCC: http://gcc.gnu.org/onlinedocs/gcc-3.0.4/gcc_3.html#IDX143
Switch over to gnu99 compilation on default for userland. Tested by: make universe Tested by: ports exp build (done by pav) Reviewed by: ru Reviewed by: silence on arch Approved by: ed (mentor)
2009-03-14 17:55:16 +00:00
# the default is gnu99 for now
CSTD ?= gnu99
For every instance of '.if ${CC} == "foo"' or '.if ${CC} != "foo"' in Makefiles or *.mk files, use ${CC:T:Mfoo} instead, so only the basename of the compiler command (excluding any arguments) is considered. This allows you to use, for example, CC="/nondefault/path/clang -xxx", and still have the various tests in bsd.*.mk identify your compiler as clang correctly. ICC if cases were also changed. Submitted by: Dimitry Andric <dimitry at andric.com>
2010-08-17 20:39:28 +00:00
.if ${CC:T:Micc} != "icc"
Switch over to gnu99 compilation on default for userland. Tested by: make universe Tested by: ports exp build (done by pav) Reviewed by: ru Reviewed by: silence on arch Approved by: ed (mentor)
2009-03-14 17:55:16 +00:00
. if ${CSTD} == "k&r"
Reintroduce CSTD, which allows a Makefile to specify the precise dialect of C in which the program or library is written. Note that this is *not* intended to be used across the whole tree. It is intended to be used for individual libraries or programs which use specific language features which the compiler must know about in order to produce correct warnings at high WARNS levels. MFC after: 1 month
2006-08-11 17:28:59 +00:00
CFLAGS += -traditional
Switch over to gnu99 compilation on default for userland. Tested by: make universe Tested by: ports exp build (done by pav) Reviewed by: ru Reviewed by: silence on arch Approved by: ed (mentor)
2009-03-14 17:55:16 +00:00
. elif ${CSTD} == "c89" || ${CSTD} == "c90"
Reintroduce CSTD, which allows a Makefile to specify the precise dialect of C in which the program or library is written. Note that this is *not* intended to be used across the whole tree. It is intended to be used for individual libraries or programs which use specific language features which the compiler must know about in order to produce correct warnings at high WARNS levels. MFC after: 1 month
2006-08-11 17:28:59 +00:00
CFLAGS += -std=iso9899:1990
Switch over to gnu99 compilation on default for userland. Tested by: make universe Tested by: ports exp build (done by pav) Reviewed by: ru Reviewed by: silence on arch Approved by: ed (mentor)
2009-03-14 17:55:16 +00:00
. elif ${CSTD} == "c94" || ${CSTD} == "c95"
Reintroduce CSTD, which allows a Makefile to specify the precise dialect of C in which the program or library is written. Note that this is *not* intended to be used across the whole tree. It is intended to be used for individual libraries or programs which use specific language features which the compiler must know about in order to produce correct warnings at high WARNS levels. MFC after: 1 month
2006-08-11 17:28:59 +00:00
CFLAGS += -std=iso9899:199409
Switch over to gnu99 compilation on default for userland. Tested by: make universe Tested by: ports exp build (done by pav) Reviewed by: ru Reviewed by: silence on arch Approved by: ed (mentor)
2009-03-14 17:55:16 +00:00
. elif ${CSTD} == "c99"
Reintroduce CSTD, which allows a Makefile to specify the precise dialect of C in which the program or library is written. Note that this is *not* intended to be used across the whole tree. It is intended to be used for individual libraries or programs which use specific language features which the compiler must know about in order to produce correct warnings at high WARNS levels. MFC after: 1 month
2006-08-11 17:28:59 +00:00
CFLAGS += -std=iso9899:1999
Switch over to gnu99 compilation on default for userland. Tested by: make universe Tested by: ports exp build (done by pav) Reviewed by: ru Reviewed by: silence on arch Approved by: ed (mentor)
2009-03-14 17:55:16 +00:00
. else
Reintroduce CSTD, which allows a Makefile to specify the precise dialect of C in which the program or library is written. Note that this is *not* intended to be used across the whole tree. It is intended to be used for individual libraries or programs which use specific language features which the compiler must know about in order to produce correct warnings at high WARNS levels. MFC after: 1 month
2006-08-11 17:28:59 +00:00
CFLAGS += -std=${CSTD}
Switch over to gnu99 compilation on default for userland. Tested by: make universe Tested by: ports exp build (done by pav) Reviewed by: ru Reviewed by: silence on arch Approved by: ed (mentor)
2009-03-14 17:55:16 +00:00
. endif
Unbreak NO_WARNS, keeping CSTD effect on CFLAGS out of its control. Unbreak compiles with icc.
2009-10-22 11:45:35 +00:00
.endif
For every instance of '.if ${CC} == "foo"' or '.if ${CC} != "foo"' in Makefiles or *.mk files, use ${CC:T:Mfoo} instead, so only the basename of the compiler command (excluding any arguments) is considered. This allows you to use, for example, CC="/nondefault/path/clang -xxx", and still have the various tests in bsd.*.mk identify your compiler as clang correctly. ICC if cases were also changed. Submitted by: Dimitry Andric <dimitry at andric.com>
2010-08-17 20:39:28 +00:00
.if !defined(NO_WARNS) && ${CC:T:Micc} != "icc"
Reintroduce CSTD, which allows a Makefile to specify the precise dialect of C in which the program or library is written. Note that this is *not* intended to be used across the whole tree. It is intended to be used for individual libraries or programs which use specific language features which the compiler must know about in order to produce correct warnings at high WARNS levels. MFC after: 1 month
2006-08-11 17:28:59 +00:00
# -pedantic is problematic because it also imposes namespace restrictions
#CFLAGS += -pedantic
Bring in the WARNS directive from NetBSD, localized in a new bsd.sys.mk to avoid polluting sys.mk. This directive controls the addition of compiler warning flags to CFLAGS in a relatively compiler-neutral manner. The idea is that WARNS can be set in Makefile.inc or in individual Makefiles as they become clean, to prevent the introduction of new warnings in the code. -Werror is added by default
2001-05-19 23:18:21 +00:00
. if defined(WARNS)
Use >= so we can use the actual WARNS levels.
2005-01-16 21:08:31 +00:00
. if ${WARNS} >= 1
Put the warning flags to where they belong (into CWARNFLAGS). This allows us to easily override them when necessary, e.g., to selectively disable warnings in libc/ contributed sources.
2004-01-11 10:29:55 +00:00
CWARNFLAGS += -Wsystem-headers
Be more strict with WARNS now -- the GCC 3.1 turmoil is behind us.
2002-07-07 18:47:52 +00:00
. if !defined(NO_WERROR)
Put the warning flags to where they belong (into CWARNFLAGS). This allows us to easily override them when necessary, e.g., to selectively disable warnings in libc/ contributed sources.
2004-01-11 10:29:55 +00:00
CWARNFLAGS += -Werror
Be more strict with WARNS now -- the GCC 3.1 turmoil is behind us.
2002-07-07 18:47:52 +00:00
. endif
Bring in the WARNS directive from NetBSD, localized in a new bsd.sys.mk to avoid polluting sys.mk. This directive controls the addition of compiler warning flags to CFLAGS in a relatively compiler-neutral manner. The idea is that WARNS can be set in Makefile.inc or in individual Makefiles as they become clean, to prevent the introduction of new warnings in the code. -Werror is added by default
2001-05-19 23:18:21 +00:00
. endif
Use >= so we can use the actual WARNS levels.
2005-01-16 21:08:31 +00:00
. if ${WARNS} >= 2
Put the warning flags to where they belong (into CWARNFLAGS). This allows us to easily override them when necessary, e.g., to selectively disable warnings in libc/ contributed sources.
2004-01-11 10:29:55 +00:00
CWARNFLAGS += -Wall -Wno-format-y2k
Add some granularity to the WARNS levels. 1: add -Werror 2: -Wall [only], as this is the most used warnings setting by developers 3: our old `1' 4: our old `2'
2001-12-15 06:02:15 +00:00
. endif
Use >= so we can use the actual WARNS levels.
2005-01-16 21:08:31 +00:00
. if ${WARNS} >= 3
Move -Wunused-parameter from WARNS level 3 level 4. Also break long lines -- note that the '\' must be up against the last character of a line to keep command-line spacing proper. Requested by: rwatson
2005-01-16 21:18:16 +00:00
CWARNFLAGS += -W -Wno-unused-parameter -Wstrict-prototypes\
-Wmissing-prototypes -Wpointer-arith
Add some granularity to the WARNS levels. 1: add -Werror 2: -Wall [only], as this is the most used warnings setting by developers 3: our old `1' 4: our old `2'
2001-12-15 06:02:15 +00:00
. endif
Use >= so we can use the actual WARNS levels.
2005-01-16 21:08:31 +00:00
. if ${WARNS} >= 4
Move -Wunused-parameter from WARNS level 3 level 4. Also break long lines -- note that the '\' must be up against the last character of a line to keep command-line spacing proper. Requested by: rwatson
2005-01-16 21:18:16 +00:00
CWARNFLAGS += -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch\
Allow suppression of -Wcast-align for WARNS>=4 by defining NO_WCAST_ALIGN. The headers of the standard C++ library are not 64-bit clean and trigger the warning. This prevents use of WARNS>=4 on ia64 for example.
2010-02-18 02:06:57 +00:00
-Wshadow -Wunused-parameter
. if !defined(NO_WCAST_ALIGN)
CWARNFLAGS += -Wcast-align
. endif
Bring in the WARNS directive from NetBSD, localized in a new bsd.sys.mk to avoid polluting sys.mk. This directive controls the addition of compiler warning flags to CFLAGS in a relatively compiler-neutral manner. The idea is that WARNS can be set in Makefile.inc or in individual Makefiles as they become clean, to prevent the introduction of new warnings in the code. -Werror is added by default
2001-05-19 23:18:21 +00:00
. endif
Add WARNS levels 5 and 6: 5 gives us -Wuninitialized rather than -Wno-uninitialized 6 gives us full BDECFLAGS
2002-04-10 02:45:22 +00:00
# BDECFLAGS
Use >= so we can use the actual WARNS levels.
2005-01-16 21:08:31 +00:00
. if ${WARNS} >= 6
Disable K&R style function definitions for WARNS=6. Unfortunately there are two slight problems with that: - Yacc and lex might generate code that generates warnings because of this. Require yacc and lex to be rebuilt during bootstrap. I'm not incrementing __FreeBSD_version here, because I assume someone else will do this eventually. - When running `make buildkernel', it uses share/mk from the source treeo to build aicasm. Because aicasm also depends on lex, this would break. Lower WARNS to 5 for now. We should just increment it to 6 again somewhere in the very far future.
2009-12-31 00:07:26 +00:00
CWARNFLAGS += -Wchar-subscripts -Winline -Wnested-externs\
-Wredundant-decls -Wold-style-definition
Add WARNS levels 5 and 6: 5 gives us -Wuninitialized rather than -Wno-uninitialized 6 gives us full BDECFLAGS
2002-04-10 02:45:22 +00:00
. endif
Use >= so we can use the actual WARNS levels.
2005-01-16 21:08:31 +00:00
. if ${WARNS} >= 2 && ${WARNS} <= 4
Put -Wno-uninitialized at the end of the warns flags as it may be enabeled by several flags (in this case -W and -Wall). Reviewed by: bde
2002-01-05 20:17:50 +00:00
# XXX Delete -Wuninitialized by default for now -- the compiler doesn't
# XXX always get it right.
Put the warning flags to where they belong (into CWARNFLAGS). This allows us to easily override them when necessary, e.g., to selectively disable warnings in libc/ contributed sources.
2004-01-11 10:29:55 +00:00
CWARNFLAGS += -Wno-uninitialized
Put -Wno-uninitialized at the end of the warns flags as it may be enabeled by several flags (in this case -W and -Wall). Reviewed by: bde
2002-01-05 20:17:50 +00:00
. endif
Universally disable -Werror until src/ is in better shape for GCC 4.2. There are new warnings that kill the build otherwise. Disable pointer destination sign mismatch warning alltogether. Our tree is in no shape to have that enabled yet.
2007-05-19 04:41:05 +00:00
CWARNFLAGS += -Wno-pointer-sign
Bring in the WARNS directive from NetBSD, localized in a new bsd.sys.mk to avoid polluting sys.mk. This directive controls the addition of compiler warning flags to CFLAGS in a relatively compiler-neutral manner. The idea is that WARNS can be set in Makefile.inc or in individual Makefiles as they become clean, to prevent the introduction of new warnings in the code. -Werror is added by default
2001-05-19 23:18:21 +00:00
. endif
. if defined(FORMAT_AUDIT)
WFORMAT = 1
. endif
. if defined(WFORMAT)
. if ${WFORMAT} > 0
Put the warning flags to where they belong (into CWARNFLAGS). This allows us to easily override them when necessary, e.g., to selectively disable warnings in libc/ contributed sources.
2004-01-11 10:29:55 +00:00
#CWARNFLAGS += -Wformat-nonliteral -Wformat-security -Wno-format-extra-args
CWARNFLAGS += -Wformat=2 -Wno-format-extra-args
Be more strict with WARNS now -- the GCC 3.1 turmoil is behind us.
2002-07-07 18:47:52 +00:00
. if !defined(NO_WERROR)
Put the warning flags to where they belong (into CWARNFLAGS). This allows us to easily override them when necessary, e.g., to selectively disable warnings in libc/ contributed sources.
2004-01-11 10:29:55 +00:00
CWARNFLAGS += -Werror
Be more strict with WARNS now -- the GCC 3.1 turmoil is behind us.
2002-07-07 18:47:52 +00:00
. endif
Only add -Werror if in fact we have set WARNS or WFORMAT to >0
2001-05-19 23:32:19 +00:00
. endif
Bring in the WARNS directive from NetBSD, localized in a new bsd.sys.mk to avoid polluting sys.mk. This directive controls the addition of compiler warning flags to CFLAGS in a relatively compiler-neutral manner. The idea is that WARNS can be set in Makefile.inc or in individual Makefiles as they become clean, to prevent the introduction of new warnings in the code. -Werror is added by default
2001-05-19 23:18:21 +00:00
. endif
To be able to use printf extensions we need to turn off gcc format checking. Following the convention of NO_WERROR and NO_WCAST_ALIGN add NO_WFORMAT, which, when defined in Makefile, turns off compile-time format checking (by adding -Wno-format), but still allows to use high WARNS level. MFC after: 2 weeks
2011-03-07 09:28:21 +00:00
. if defined(NO_WFORMAT)
CWARNFLAGS += -Wno-format
. endif
Bring in the WARNS directive from NetBSD, localized in a new bsd.sys.mk to avoid polluting sys.mk. This directive controls the addition of compiler warning flags to CFLAGS in a relatively compiler-neutral manner. The idea is that WARNS can be set in Makefile.inc or in individual Makefiles as they become clean, to prevent the introduction of new warnings in the code. -Werror is added by default
2001-05-19 23:18:21 +00:00
.endif
Allow a makefile to set IGNORE_PRAGMA so that OpenSolaris code can be built with other gcc warnings enabled. Every Solaris source file has a #pragma ident in it. We can just ignore those definitions.
2006-11-04 04:39:05 +00:00
.if defined(IGNORE_PRAGMA)
CWARNFLAGS += -Wno-unknown-pragmas
.endif
MFtbemd: Prefer MACHNE_CPUARCH to MACHINE_ARCH in most contexts where you want to test of all the CPUs of a given family conform.
2010-08-23 22:24:11 +00:00
.if ${MK_SSP} != "no" && ${CC:T:Micc} != "icc" && \
${MACHINE_CPUARCH} != "ia64" && \
${MACHINE_CPUARCH} != "arm" && ${MACHINE_CPUARCH} != "mips"
Enable GCC stack protection (aka Propolice) for userland: - It is opt-out for now so as to give it maximum testing, but it may be turned opt-in for stable branches depending on the consensus. You can turn it off with WITHOUT_SSP. - WITHOUT_SSP was previously used to disable the build of GNU libssp. It is harmless to steal the knob as SSP symbols have been provided by libc for a long time, GNU libssp should not have been much used. - SSP is disabled in a few corners such as system bootstrap programs (sys/boot), process bootstrap code (rtld, csu) and SSP symbols themselves. - It should be safe to use -fstack-protector-all to build world, however libc will be automatically downgraded to -fstack-protector because it breaks rtld otherwise. - This option is unavailable on ia64. Enable GCC stack protection (aka Propolice) for kernel: - It is opt-out for now so as to give it maximum testing. - Do not compile your kernel with -fstack-protector-all, it won't work. Submitted by: Jeremie Le Hen <jeremie@le-hen.org>
2008-06-25 21:33:28 +00:00
# Don't use -Wstack-protector as it breaks world with -Werror.
SSP_CFLAGS ?= -fstack-protector
CFLAGS += ${SSP_CFLAGS}
.endif
Bring in the WARNS directive from NetBSD, localized in a new bsd.sys.mk to avoid polluting sys.mk. This directive controls the addition of compiler warning flags to CFLAGS in a relatively compiler-neutral manner. The idea is that WARNS can be set in Makefile.inc or in individual Makefiles as they become clean, to prevent the introduction of new warnings in the code. -Werror is added by default
2001-05-19 23:18:21 +00:00
# Allow user-specified additional warning flags
CFLAGS += ${CWARNFLAGS}
Reference in New Issue Copy Permalink