Date: Wed, 6 Feb 2002 08:21:07 -0500 (EST) From: Robert Watson <rwatson@FreeBSD.org> To: Terry Lambert <tlambert2@mindspring.com> Cc: Ruslan Ermilov <ru@FreeBSD.org>, Warner Losh <imp@FreeBSD.org>, Kris Kennaway <kris@FreeBSD.org>, "David O'Brien" <obrien@FreeBSD.org>, Mark Murray <markm@FreeBSD.org>, current@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: Not committing WARNS settings... Message-ID: <Pine.NEB.3.96L.1020206082002.67775D-100000@fledge.watson.org> In-Reply-To: <3C60EDC8.28844031@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 6 Feb 2002, Terry Lambert wrote: > Ruslan Ermilov wrote: > > Nope, what David was _actually_ trying to say is to hold off with WARNS > > fixes until GCC 3.1 becomes our compiler, because otherwise this is an > > almost 100% duplicate of efforts, as GCC 3.1 is so WARNS-different from > > GCC 2.95.3. And of course David should add NO_WERROR (but probably to > > Makefile.inc1) to avoid world breakage. > > A cynic would say that that means that there are two sets of things that > need to be fixed, and not just one. Well, I think that's true: no one is saying you can't fix the warnings you find by turning up the warning level. They're just asking that the warning level not be turned up in the default Makefile. Since these are entirely seperable activities... Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services 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?Pine.NEB.3.96L.1020206082002.67775D-100000>