From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] inline keyword & ansi-C compilers
Date: Tue, 01 Aug 2006 00:41:16 +0200 [thread overview]
Message-ID: <1154385676.4982.39.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <200607312232.58278.thermal@o2.pl>
Hi,
> Recently when I`ve tried to compile KDE (ktnef to be exact) I came upon
> an error in your include files:
no idea what ktnef has to do with BlueZ. This seems to be the main
problem here.
> So I wrote a tiny patch to fix this:
>
> --- bluez-libs-3.2/include/bluetooth.h 2006-07-31 20:57:08.000000000
> +0200
> +++ /usr/include/bluetooth/bluetooth.h 2006-07-31 20:55:55.000000000
> +0200
> @@ -109,12 +109,19 @@
> #define BDADDR_ALL (&(bdaddr_t) {{0xff, 0xff, 0xff, 0xff, 0xff,
> 0xff}})
> #define BDADDR_LOCAL (&(bdaddr_t) {{0, 0, 0, 0xff, 0xff, 0xff}})
>
> +/* No inline keyword in the iso8988:1990 standard */
> +#ifdef __STRICT_ANSI__
> + #define __INLINE
> +#else
> + #define __INLINE inline
> +#endif
> +
I don't like to provide any workarounds for any crazy standard that
forcing it makes no real sense to me. However what about this:
#ifdef __STRICT_ANSI__
#define inline
#endif
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-07-31 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 20:32 [Bluez-devel] [PATCH] inline keyword & ansi-C compilers thermal
2006-07-31 22:41 ` Marcel Holtmann [this message]
2006-08-01 16:23 ` thermal
2006-08-02 1:13 ` 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=1154385676.4982.39.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--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