On Fri, 2012-03-02 at 17:06 +0200, Luiz Augusto von Dentz wrote: > Hi Bastien > > On Fri, Mar 2, 2012 at 4:13 PM, Bastien Nocera <hadess@xxxxxxxxxx> wrote: > > On Fri, 2012-03-02 at 14:57 +0200, Luiz Augusto von Dentz wrote: > >> Hi Bastien, > >> > >> On Fri, Mar 2, 2012 at 2:43 PM, Bastien Nocera <hadess@xxxxxxxxxx> wrote: > >> > Heya, > >> > > >> > Trying to compile obexd 0.45 with bluez-4.98, I get: > >> > btio/btio.c: In function 'get_key_size': > >> > btio/btio.c:522:14: error: 'struct bt_security' has no member named 'key_size' > >> > > >> > Do you need to either up the bluez dependency, or is obexd lagging? > >> > > >> > Install log: > >> > http://koji.fedoraproject.org/koji/getfile?taskID=3846402&name=root.log > >> > Compile log: > >> > http://koji.fedoraproject.org/koji/getfile?taskID=3846402&name=build.log > >> > >> It is a known problem, until we are depending on a new release of > >> bluez (4.99) then we can add the build dependency properly, after that > >> we will probably have a new release for obexd as well. > > > > I don't understand. Are you telling me that obexd relies on an > > unreleased version of bluez? > > Not exactly obexd, but btio yes Given that btio is copy/pasted into obexd, it's obexd relying on an unreleased version of bluez. I could understand the idea if bluez hadn't had releases in ages, and you didn't have any control over it. But that's hardly helpful to the people downstream distributing your code. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
