Date: Tue, 5 Feb 2002 22:32:46 -0800 From: Kris Kennaway <kris@obsecurity.org> To: John Hay <jhay@icomtek.csir.co.za> Cc: Kris Kennaway <kris@obsecurity.org>, current@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: Not committing WARNS settings... Message-ID: <20020205223246.A52122@xor.obsecurity.org> In-Reply-To: <200202060558.g165wrG54670@zibbi.icomtek.csir.co.za>; from jhay@icomtek.csir.co.za on Wed, Feb 06, 2002 at 07:58:53AM %2B0200 References: <20020205200812.A50411@xor.obsecurity.org> <200202060558.g165wrG54670@zibbi.icomtek.csir.co.za>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Wed, Feb 06, 2002 at 07:58:53AM +0200, John Hay wrote: > > > > All David has to do is set WARNS=0 or NO_WERROR=1 in <bsd.sys.mk> or > > /etc/defaults/make.conf temporarily when he tests and commits the > > changeover, and he'll sidestep all the problems. There's no need to > > impose restrictions on the activities of other committers. > > > > It's really not a big deal, IMO. > > > > Kris > > Let me hijack this a little. How many of you WARNS= adding people > consider different compile/code paths than the one your machine > exercise? For instance the one "make release" will exercise? The > WARNS=1 in libexec/Makefile.inc breaks "make release" because > telnetd is then compiled, but it isn't warning free. Yeah, I'm going to fix that tonight when I get home and can test it. I try and be careful to consider all code paths, but this one slipped me by. Sorry. Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8YM4OWry0BWjoQKURAopCAJsFhvN3jRPYfM7I1DkBuOcgEKnmFgCg9LhU VzMyGNiWKwrcyKSZt2AFU2c= =Dmc9 -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020205223246.A52122>