Date: Wed, 6 Feb 2002 07:58:53 +0200 (SAT) From: John Hay <jhay@icomtek.csir.co.za> To: kris@obsecurity.org (Kris Kennaway) Cc: current@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: Not committing WARNS settings... Message-ID: <200202060558.g165wrG54670@zibbi.icomtek.csir.co.za> In-Reply-To: <20020205200812.A50411@xor.obsecurity.org> from Kris Kennaway at "Feb 5, 2002 08:08:12 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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. John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200202060558.g165wrG54670>