From owner-cvs-all Fri Dec 14 13:34:52 2001 Delivered-To: cvs-all@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id C499937B405; Fri, 14 Dec 2001 13:34:44 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 14 Dec 2001 21:34:41 +0000 (GMT) To: obrien@FreeBSD.org Cc: Mark Murray , Ruslan Ermilov , Luigi Rizzo , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/bin/rm rm.c src/usr.sbin/chown chown.c src/usr.sbin/dev_mkdb dev_mkdb.c In-reply-to: Your message of "Fri, 14 Dec 2001 13:19:34 PST." <20011214131934.B33199@dragon.nuxi.com> X-Request-Do: Date: Fri, 14 Dec 2001 21:34:39 +0000 From: David Malone Message-ID: <200112142134.aa40078@salmon.maths.tcd.ie> Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > The issue is that gcc 3 produces more warnings. And things that pass > WARNS=2 probably won't pass WARNS=2 with GCC 3. So everyone will have to > have to turn on NO_WERROR=yes. Unless people want to see gcc3 delayed by > extra weeks so the person bringing it in can clean up all the errors that > prevent the tree from building. Thus any new WARNS=2 will just get in > the way more. I don't see the problem with turning on NO_WERROR=yes and then working through the new warnings when gcc3 is imported. Both gcc2 and gcc3 warnings will have to be resolved at some time and waiting for a month or two while gcc3 is imported just putting off fixing the gcc2 warnings. (I'll take responsibility for working through the bits of userland which give new warnings with gcc3, if it will take one problem off the mind of those doing the import). David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message