From owner-freebsd-current Mon Apr 17 17: 0:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from sr14.nsw-remote.bigpond.net.au (sr14.nsw-remote.bigpond.net.au [24.192.3.29]) by hub.freebsd.org (Postfix) with ESMTP id 9E1F737B844 for ; Mon, 17 Apr 2000 17:00:20 -0700 (PDT) (envelope-from areilly@nsw.bigpond.net.au) Received: from areilly.bpc-users.org (CPE-144-132-171-71.nsw.bigpond.net.au [144.132.171.71]) by sr14.nsw-remote.bigpond.net.au (Pro-8.9.3/8.9.3) with SMTP id KAA21628 for ; Tue, 18 Apr 2000 10:00:17 +1000 (EST) Received: (qmail 69247 invoked by uid 1000); 18 Apr 2000 00:00:16 -0000 From: "Andrew Reilly" Date: Tue, 18 Apr 2000 10:00:16 +1000 To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: FreeBSD Build status Message-ID: <20000418100016.A67726@gurney.reilly.home> References: <12411.956006235@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <12411.956006235@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 17, 2000 at 11:17:15PM +0200, Poul-Henning Kamp wrote: > Once per day the machine cvsups, checks out a virgin source tree, > tries to build GENERIC, GENERIC98, LINT and world. If any of these > builds fail it will send a report like this. > > On Sundays the report will always be sent. Are any of these warnings of the "helpful gcc" type, rather than actual dangers? It would be a shame if this resulted in obfuscation of the code base _just_ to shut gcc up. Of course if gcc is well-behaved on this point, and the warning flags are well sorted and agreed-upon, then there isn't a problem. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message