From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19738 invoked by alias); 5 Dec 2006 19:02:50 -0000 Received: (qmail 19730 invoked by uid 22791); 5 Dec 2006 19:02:49 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 05 Dec 2006 19:02:43 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 3FF9748CDB6; Tue, 5 Dec 2006 14:02:41 -0500 (EST) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 07270-01-9; Tue, 5 Dec 2006 14:02:41 -0500 (EST) Received: from takamaka.act-europe.fr (unknown [70.71.0.212]) by nile.gnat.com (Postfix) with ESMTP id F20A148CC4D; Tue, 5 Dec 2006 14:02:40 -0500 (EST) Received: by takamaka.act-europe.fr (Postfix, from userid 1000) id 901EC34C099; Tue, 5 Dec 2006 11:03:10 -0800 (PST) Date: Tue, 05 Dec 2006 19:02:00 -0000 From: Joel Brobecker To: Markus Deuling Cc: gdb@sourceware.org Subject: Re: GDB 6.5.90 available for testing (GDB 6.6 pre-release) Message-ID: <20061205190310.GU15038@adacore.com> References: <20061202192351.GY3304@adacore.com> <4573EBCD.90505@de.ibm.com> <20061204182108.GA11343@adacore.com> <4575197F.7020602@de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4575197F.7020602@de.ibm.com> User-Agent: Mutt/1.4.2.2i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-12/txt/msg00043.txt.bz2 > 3) I switched the environment so you get the error msg in english. Sorry > for the german :-) So this is for x86 without --disable-werror (no worries about the German, thanks for reposting the messages in English :-) I must say I do not understand why it builds fine with head, because I saw the patch that Daniel refered to (from H.J Lu), and it should fix your warnings. However, it hasn't been checked in yet! But it doesn't really matter as far as I am concerned, because... I think all future releases will be provided so that -Werror is removed by default, so we don't need to take at the code level. The only thing I need to do is to set --disable-werror by default. Will do momentarily. Thanks for reporting this! -- Joel