Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Achim Bohnet <ach@mpe.mpg.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] PF_BLUETOOTH AF_BLUETOOTH redefinitions
Date: Thu, 22 Jan 2004 14:04:33 +0100	[thread overview]
Message-ID: <1074776673.3071.4.camel@pegasus> (raw)
In-Reply-To: <200401221347.32481.ach@mpe.mpg.de>

Hi Achim,

> During compilation of some bluetooth apps I get lots of warings like this:
> 
> In file included from /usr/include/sys/socket.h:35,
>                  from connectiondlg.h:31,
>                  from connectiondlg.cpp:24:
> /usr/include/bits/socket.h:91: warning: `PF_BLUETOOTH' redefined
> /usr/include/bluetooth/bluetooth.h:43: warning: this is the location of the previous definition
> /usr/include/bits/socket.h:123: warning: `AF_BLUETOOTH' redefined
> /usr/include/bluetooth/bluetooth.h:42: warning: this is the location of the previous definition
> In file included from connectiondlg.h:35,
>                  from connectiondlg.cpp:24:
> /usr/include/bluetooth/hci.h:482: warning: ANSI C++ forbids zero-size array `condition'
> /usr/include/bluetooth/hci.h:909: warning: ANSI C++ forbids zero-size array `data'
> /usr/include/bluetooth/hci.h:1046: warning: ANSI C++ forbids zero-size array `dev_req'
> /usr/include/bluetooth/hci.h:1052: warning: ANSI C++ forbids zero-size array `conn_info'
> /usr/include/bluetooth/hci.h:1058: warning: ANSI C++ forbids zero-size array `conn_info'
> 
> Would be nice if bluetooth.h would not override stuff already defined
> 
> sys/socket.h:123:#define AF_BLUETOOTH    PF_BLUETOOTH
> 
> I would suggest that bluetooth.h includes itself sys/socket.h before checking if AF_BLUETOOTH
> is defined.   This removed the dependency on how headers are ordered in source files.
> Works for me ;)
> 
> hci.h may be due to old g++2.94.4 used on debian.  No idea about a workaround :(

include "sys/socket.h" before you include "bluetooth/bluetooth.h".

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-01-22 13:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22 12:47 [Bluez-devel] PF_BLUETOOTH AF_BLUETOOTH redefinitions Achim Bohnet
2004-01-22 13:04 ` Marcel Holtmann [this message]
2004-01-22 13:34   ` Achim Bohnet
2004-01-08 15:27     ` Marcel Holtmann
2004-01-22 18:09     ` Max Krasnyansky
2004-01-22 22:38       ` 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=1074776673.3071.4.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=ach@mpe.mpg.de \
    --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