From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Moving over to GCC 4.0
Date: Wed, 06 Jul 2005 09:24:22 -0600 [thread overview]
Message-ID: <42CBF7A6.7090708@xmission.com> (raw)
In-Reply-To: <1120649879.8836.5.camel@pegasus>
just FYI everybody... sourceforge seems to have broken anonymous cvs
(both bluez and bluetooth-alsa are affected)
$ cvs update -d
cvs [update aborted]: unrecognized auth response from cvs.bluez.org: cvs
pserver: cannot read /cvsroot/bluez/CVSROOT/config: Input/output error
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.
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> 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
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-07-06 15:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 11:37 [Bluez-devel] Moving over to GCC 4.0 Marcel Holtmann
2005-07-06 12:09 ` [Bluez-devel] Querying device information Dave Mielke
2005-07-06 12:26 ` Marcel Holtmann
2005-07-06 12:33 ` Dave Mielke
2005-07-06 12:43 ` Marcel Holtmann
2005-07-09 4:10 ` [Bluez-devel] hcid dies on socket connect attempt Dave Mielke
2005-07-09 7:43 ` Marcel Holtmann
2005-07-06 15:24 ` Brad Midgley [this message]
2005-07-06 16:57 ` [Bluez-devel] Moving over to GCC 4.0 Marcel Holtmann
2005-07-06 17:02 ` Peter Robinson
2005-07-06 17:09 ` Marcel Holtmann
2005-07-06 16:35 ` Luiz Fernando Capitulino
2005-07-06 17:48 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42CBF7A6.7090708@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox