From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20417 invoked by alias); 12 Jun 2010 01:52:17 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 20407 invoked by uid 22791); 12 Jun 2010 01:52:16 -0000 X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_20,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Date: Sat, 12 Jun 2010 01:52:00 -0000 Message-ID: Subject: Added branch for compiling with c++-compat From: Matt Rice To: Project Archer Content-Type: text/plain; charset=ISO-8859-1 X-SW-Source: 2010-q2/txt/msg00048.txt.bz2 Hi all, I added a branch for compiling gdb with c++-compat named: archer-ratmice-compile-Wc++-compat I've been doing: CFLAGS="-Wc++-compat" ./configure --disable-werror and then tackling things one type of warning at a time. in hopes that this will make the patches more easily reviewable. The downside to this I suppose is that I may temporarily introduce a warning and then subsequently miss it in the deluge... If this happens i'll fix these as I notice. I guess a balance between number of patches and patch length will be somewhat important.... I've just been commiting about at the point that I get the urge to hold down the space bar and see how much longer the dang patch is. so far everything has been fairly mechanical, there is one ada macro which looks like it may be remotely interesting.