From owner-freebsd-current Tue Feb 5 21:59:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 6B41837B426; Tue, 5 Feb 2002 21:59:25 -0800 (PST) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.6/8.11.6) id g165wrG54670; Wed, 6 Feb 2002 07:58:53 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200202060558.g165wrG54670@zibbi.icomtek.csir.co.za> Subject: Re: Not committing WARNS settings... In-Reply-To: <20020205200812.A50411@xor.obsecurity.org> from Kris Kennaway at "Feb 5, 2002 08:08:12 pm" To: kris@obsecurity.org (Kris Kennaway) Date: Wed, 6 Feb 2002 07:58:53 +0200 (SAT) Cc: current@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > All David has to do is set WARNS=0 or NO_WERROR=1 in 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