On 03/21/2018 05:47 PM, Alan Martinovic wrote:
When you say "tagged as backports" are you referring to the Upstream-Status?
So this is a backport patch:
Upstream-Status: Accepted
[https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=76255f73
2d68aef2b90d36d9c7be51a9e1739ce7]
b
When you say "tagged as backports" are you referring to the Upstream-Status?
So this is a backport patch:
Upstream-Status: Accepted
[https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=76255f73
2d68aef2b90d36d9c7be51a9e1739ce7]
but these two aren't yet or never will be:
Upstr
If you look at the patch headers, you'll see that none of them are
tagged as backports.
Ross
On 21 March 2018 at 15:35, Alan Martinovic wrote:
> Hey Ross, thanks for the clarification.
>
> The issues reoccurred because I modified the recipe not to include any
> patches,
> falsely assuming that
Hey Ross, thanks for the clarification.
The issues reoccurred because I modified the recipe not to include any patches,
falsely assuming that all of them were BlueZ backports and none is actually
a Yocto specific change.
On Wed, Mar 21, 2018 at 4:23 PM, Burton, Ross wrote:
> On 21 March 2018 at
On 21 March 2018 at 15:15, Alan Martinovic
wrote:
>
> Building it with Yocto results in the mentioned error:
>
> | ../git/src/genbuiltin hostname wiimote autopair policy a2dp avrcp
> network input hog gap scanparam deviceinfo battery > src/builtin.h
> | ../git/obexd/src/genbuiltin filesystem
Started this issue a few days ago thinking it was a problem with
the bluez flags. I guess it might still be given it tries to build obex
even when it's been configured that is shouldn't...
The exact issue seems to point it's a Yocto related
or might be both (hence both lists). I have configured
Bl
