summaryrefslogtreecommitdiffstats
path: root/share/mk/bsd.sys.mk
Commit message (Collapse)AuthorAgeFilesLines
* Be more strict with WARNS now -- the GCC 3.1 turmoil is behind us.obrien2002-07-071-0/+6
|
* Tweak the WARNS levels a tad.obrien2002-05-191-6/+0
|
* Gcc 3.1 has different -Wx flags.obrien2002-05-101-2/+5
|
* Add WARNS levels 5 and 6:obrien2002-04-101-1/+8
| | | | | 5 gives us -Wuninitialized rather than -Wno-uninitialized 6 gives us full BDECFLAGS
* FreeBSD prior to 4.5-RELEASE and older versions of 5.0-CURRENT do notru2002-04-071-0/+5
| | | | | | | | | have the __FBSDID() macro in <sys/cdefs.h>. Fix this once and for all for tools that need to be bootstrapped. PR: bin/36747 MFC after: 3 days Prodded by: obrien
* Put -Wno-uninitialized at the end of the warns flags as it may be enabeleddwmalone2002-01-051-3/+5
| | | | | | by several flags (in this case -W and -Wall). Reviewed by: bde
* Add some granularity to the WARNS levels.obrien2001-12-151-5/+10
| | | | | | | 1: add -Werror 2: -Wall [only], as this is the most used warnings setting by developers 3: our old `1' 4: our old `2'
* Only add -Werror if in fact we have set WARNS or WFORMAT to >0kris2001-05-191-4/+6
|
* Bring in the WARNS directive from NetBSD, localized in a new bsd.sys.mkkris2001-05-191-0/+37
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
OpenPOWER on IntegriCloud