From: thermal@o2.pl
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] inline keyword & ansi-C compilers
Date: Tue, 1 Aug 2006 18:23:37 +0200 [thread overview]
Message-ID: <200608011823.37945.thermal@o2.pl> (raw)
In-Reply-To: <1154385676.4982.39.camel@aeonflux.holtmann.net>
On wtorek, 1 sierpnia 2006 00:41, Marcel Holtmann wrote:
> 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.
>
Yes, this may look a bit weird but ktnef is a part of the kdepim source
bundle which contains addressbook, organizer, etc. and thus can make
use of Bluetooth.
>
> #ifdef __STRICT_ANSI__
> #define inline
> #endif
>
You`re right, that will be much better.
--
| ******* Maciek Grela RV409b *********
| JID: thermal@jabber.wroc.pl
| Linux user #319794 ++ There is no spoon ...
-------------------------------------------------------------------------
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-08-01 16:23 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
2006-08-01 16:23 ` thermal [this message]
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=200608011823.37945.thermal@o2.pl \
--to=thermal@o2.pl \
--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