Date: Wed, 9 Jan 2002 21:13:37 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Daniel Eischen <eischen@pcnet1.pcnet.com>, Will Andrews <will@csociety.org> Cc: David Malone <dwmalone@maths.tcd.ie>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/syslogd syslogd.c Message-ID: <p05101004b862a889f34a@[128.113.24.47]> In-Reply-To: <Pine.SUN.3.91.1020109195800.2811A-100000@pcnet1.pcnet.com> References: <Pine.SUN.3.91.1020109195800.2811A-100000@pcnet1.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 8:09 PM -0500 1/9/02, Daniel Eischen wrote: >On Wed, 9 Jan 2002, Will Andrews wrote: >> On Wed, Jan 09, 2002 at 05:26:40PM -0500, Daniel Eischen wrote: >> > Doesn't everyone add -Wall to (and enable) CFLAGS in /etc/make.conf, >> > or am I one of the few? >> >> Do you ever compile ports? > >Sure, not a whole lot, but I do use the ports tree. I've never >had -Wall abort a port build. I consider our ports tree a separate >thing anyways. We should have higher standards for the code in >our own source tree. I think everyone making changes in src should >be compiling with -Wall. I think "we" (he says vaguely) are trying to use the NOWARNS setting to indicate what level of warnings we want, and let *it* put things like -Wall into CFLAGS. There's also some environment/MAKE variable to use so compiles don't die if they get a compile-time warning. In my case, I tend to compile with BDECFLAGS (skipping NOWARN :-) on anything where I am making changes to the source, but I leave the global settings the way "the project" uses them. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05101004b862a889f34a>