Return-Path: Delivered-To: apmail-stdcxx-dev-archive@www.apache.org Received: (qmail 66457 invoked from network); 1 Apr 2008 16:06:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Apr 2008 16:06:47 -0000 Received: (qmail 52321 invoked by uid 500); 1 Apr 2008 16:06:47 -0000 Delivered-To: apmail-stdcxx-dev-archive@stdcxx.apache.org Received: (qmail 52258 invoked by uid 500); 1 Apr 2008 16:06:47 -0000 Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stdcxx.apache.org Delivered-To: mailing list dev@stdcxx.apache.org Received: (qmail 52249 invoked by uid 99); 1 Apr 2008 16:06:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Apr 2008 09:06:47 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [208.30.140.160] (HELO moroha.roguewave.com) (208.30.140.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Apr 2008 16:05:57 +0000 Received: from nebula.bco.roguewave.com ([10.70.3.27]) by moroha.roguewave.com (8.13.6/8.13.6) with ESMTP id m31G6GVj000610 for ; Tue, 1 Apr 2008 16:06:16 GMT Message-ID: <47F25D79.60606@roguewave.com> Date: Tue, 01 Apr 2008 10:06:17 -0600 From: Martin Sebor Organization: Rogue Wave Software, Inc. User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: dev@stdcxx.apache.org Subject: Re: [aCC 6.05] too many warnings References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Scott Zhong wrote: > In the debug build of aCC 6.05 for stdcxx trunk, there are too many > warnings that made the build log file to be larger than what the nightly > build infrastructure could handle. This is causing debug builds to show > up as DATA in the results page. Thanks for the heads up. Is there any way to get a partial log so we can tell which warnings are generating the most noise and silence them? Martin