From: Tino Keitel <tino.keitel@tikei.de>
To: Patrick Ohly <patrick.ohly@intel.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
linux-bluetooth@vger.kernel.org, Milan Crha <mcrha@redhat.com>,
ying.an.deng@intel.com, ulf.hofemeier@intel.com,
ning.w.wang@intel.com, Rohan Garg <rohan16garg@gmail.com>
Subject: Re: bluez 4.97: build failure when used in C++ apps
Date: Sun, 5 Feb 2012 15:29:58 +0100 [thread overview]
Message-ID: <20120205142958.GA13091@x61.home> (raw)
In-Reply-To: <1328439363.32199.20.camel@pohly-mobl1.fritz.box>
On Sun, Feb 05, 2012 at 11:56:03 +0100, Patrick Ohly wrote:
[...]
> How do we move forward with this? More and more distros are picking up
> the broken header file.
>
> In MeeGo and Tizen we applied the patch that I had suggested.
FYI, Debian also applied a patch and syncevolution builds fine.
Regards,
Tino
next prev parent reply other threads:[~2012-02-05 14:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 8:25 bluez 4.97: build failure when used in C++ apps Patrick Ohly
2012-01-16 8:48 ` Deng, Ying An
2012-01-16 9:24 ` Marcel Holtmann
2012-01-16 10:09 ` Patrick Ohly
2012-02-05 10:56 ` Patrick Ohly
2012-02-05 10:57 ` [PATCH] bluetooth.h: fix compile issue in C++ with ifdef Patrick Ohly
2012-02-05 11:07 ` Rohan Garg
2012-02-05 11:33 ` Patrick Ohly
2012-02-05 11:33 ` Rohan Garg
2012-02-05 12:23 ` Rohan Garg
2012-02-05 12:28 ` Rohan Garg
2012-02-05 10:59 ` bluez 4.97: build failure when used in C++ apps Rohan Garg
2012-02-05 12:02 ` Rohan Garg
2012-02-06 8:46 ` Milan Crha
2012-02-06 9:29 ` Patrick Ohly
2012-02-06 9:51 ` Milan Crha
2012-02-05 14:29 ` Tino Keitel [this message]
2012-02-05 14:50 ` Rohan Garg
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=20120205142958.GA13091@x61.home \
--to=tino.keitel@tikei.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mcrha@redhat.com \
--cc=ning.w.wang@intel.com \
--cc=patrick.ohly@intel.com \
--cc=rohan16garg@gmail.com \
--cc=ulf.hofemeier@intel.com \
--cc=ying.an.deng@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).