Date: Wed, 7 Feb 2001 06:19:44 +0100 From: Cliff Sarginson <cliff@raggedclown.net> To: Tim McMillen <timcm@umich.edu> Cc: Wyatt Banks <banksw@sunyit.edu>, questions@FreeBSD.ORG Subject: Re: kernel configuration question Message-ID: <20010207061944.C1167@raggedclown.net> In-Reply-To: <01020623040701.03509@tim.elnsng1.mi.home.com>; from timcm@umich.edu on Wed, Feb 07, 2001 at 12:02:34AM -0500 References: <Pine.GSO.4.21.0102061357320.2653-100000@demeter> <01020623040701.03509@tim.elnsng1.mi.home.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 07, 2001 at 12:02:34AM -0500, Tim McMillen wrote: > > They are just that, warnings. Messages to tell the coders to try to > clean things up, not errors really. As I heard it, gcc has been > raising the amount that it warns about things. As of the 3.0-Release > series, the FreeBSD kernel compile is much louder about them. > > On Tuesday February 06, 2001 14:00, Wyatt Banks wrote: > > Usually when I use a compiler, I treat all warnings like errors, Mmm, warnings are not errors, although they may point to mis-intentions ! Crank up the warnings enough and gcc will complain about the following comment: /* This is a comment /* that will make gcc bletch, if /* you set the right warnings on */ Cliff p.s. I will leave it to the reader to work out what the complaint is.. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010207061944.C1167>