Return-Path: Message-ID: <42CC0841.9070301@conectiva.com.br> From: Luiz Fernando Capitulino MIME-Version: 1.0 To: bluez-devel@lists.sourceforge.net Subject: Re: [Bluez-devel] Moving over to GCC 4.0 References: <1120649879.8836.5.camel@pegasus> In-Reply-To: <1120649879.8836.5.camel@pegasus> Content-Type: text/plain; charset=us-ascii; format=flowed Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 06 Jul 2005 13:35:13 -0300 Hi Marcel, Marcel Holtmann wrote: > Hi Folks, > > since Debian Etch now also switched to GCC 4.0 as default compiler, it > is time to address all GCC 4.0 problems in the BlueZ source code. I > started two days ago with fixing most of its crazy compiler warnings. > The GCC 4.0 is really picky with the signedness and so I moved over to > explicit types like uint8_t, uint16_t and uint32_t where possible. I now > hope that I haven't introduced any signedness bugs. Please start testing > the CVS versions of libs and utils. Good news. :) I'd like to know if you're going to accept patches which fixes Linus sparse warnings, they seems to be trivial though. PS: I think CVS is back again, it's working here. Thanks, ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel