From owner-freebsd-current Mon Feb 11 18:49:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from newman2.bestweb.net (newman2.bestweb.net [209.94.102.67]) by hub.freebsd.org (Postfix) with ESMTP id F3D2C37B477; Mon, 11 Feb 2002 18:16:52 -0800 (PST) Received: from okeeffe.bestweb.net (okeefe.bestweb.net [209.94.100.110]) by newman2.bestweb.net (Postfix) with ESMTP id 23F8E230EE; Mon, 11 Feb 2002 21:16:44 -0500 (EST) Received: by okeeffe.bestweb.net (Postfix, from userid 0) id A84E69EEF7; Mon, 11 Feb 2002 21:11:48 -0500 (EST) To: Dag-Erling Smorgrav Cc: current@FreeBSD.org, cvs-committers@FreeBSD.org, Subject: Re: Not committing WARNS settings... Date: Wed, 06 Feb 2002 11:12:38 +0000 From: Mark Murray Message-Id: <20020212021148.A84E69EEF7@okeeffe.bestweb.net> 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 > John Hay writes: > > 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. > > This is a good reason why non-zero WARNS should only be set in leaf > Makefiles. IMO, this is a good reason to not have WARNS contain -Werror at this time. NO_WERROR is a good way to fix this (again IMO). I see a great need to let warnings "hang out", and in an ideal world I see an need for (new) warnings to break things. I see no need for warnings to hold back a project as important as GCC3, and NO_WERROR is the cleanest solution. I do not expect others to agree with (or like) this. M -- o Mark Murray \_ FreeBSD Services Limited O.\_ Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message