From: Marcel Holtmann <marcel@holtmann.org>
To: Bastien Nocera <hadess@hadess.net>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: obexd 0.45 compilation problem
Date: Fri, 02 Mar 2012 10:11:19 -0800 [thread overview]
Message-ID: <1330711879.3392.128.camel@aeonflux> (raw)
In-Reply-To: <1330711749.20578.23.camel@novo.hadess.net>
Hi Bastien,
> > > 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?
> >
> > I screwed this one up. Hand me over the brown-paper-bag please.
> >
> > Seems I ended up installing non-released headers on my build/test
> > system. That should not have happened, but it did.
> >
> > Either we do an obexd 0.46 with this change reversed or BlueZ 4.99. I
> > going to check up on that and let everybody now.
>
> Either is fine by me, and not in much of a hurry. It's just that I got
> the impression from Luiz that it was done on purpose.
nope, just a big screw up on my part :(
Regards
Marcel
prev parent reply other threads:[~2012-03-02 18:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 12:43 obexd 0.45 compilation problem Bastien Nocera
2012-03-02 12:57 ` Luiz Augusto von Dentz
2012-03-02 14:13 ` Bastien Nocera
2012-03-02 15:06 ` Luiz Augusto von Dentz
2012-03-02 15:17 ` Bastien Nocera
2012-03-02 16:02 ` Johan Hedberg
2012-03-02 17:53 ` Marcel Holtmann
2012-03-02 18:09 ` Bastien Nocera
2012-03-02 18:11 ` Marcel Holtmann [this message]
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=1330711879.3392.128.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.