From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-opie][PATCH] opie-bluetoothd: fix compilation issues
Date: Tue, 13 Dec 2011 23:41:40 +0000 [thread overview]
Message-ID: <2795170.GPyksbkBvZ@helios> (raw)
In-Reply-To: <CALT56yNowfmEegV6OFQEdnk47YaaFOd9S_g0vdt3YKQf91DYHg@mail.gmail.com>
On Wednesday 14 December 2011 03:32:08 Dmitry Eremin-Solenikov wrote:
> <paul.eggleton@linux.intel.com> wrote:
> > On Wednesday 14 December 2011 01:25:50 Dmitry Eremin-Solenikov wrote:
> >> rfkill.cpp uses symbols from libsysfs. However opie-bluetoothd recipe
> >> lacks dependency on sysfsutils (package containing libsysfs) and
> >> project
> >> file also lacks -lsysfs in the LIBS rule. Fix those issues.
> >
> > Rather than apply this patch I've merged the change upstream and updated
> > the OPIE_SRCREV in meta-opie to
> > f5c8bd6272b5bee393736f401232ce0ccc984fec (which includes a few other
> > fixes as well.) Thanks!
>
> Thanks! I just didn't want to touch SRCREV, so I provided oe patch instead
> :)
I guess I prefer updating SRCREV to carrying around a bunch of patches given
that I'm the upstream in this case ;) I realise it forces a rebuild of
everything, but I'd imagine people building from git are prepared to put up
with a little pain for the benefit of getting the absolute latest code.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2011-12-13 23:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 21:25 [meta-opie][PATCH] opie-bluetoothd: fix compilation issues Dmitry Eremin-Solenikov
2011-12-13 22:58 ` Paul Eggleton
2011-12-13 23:32 ` Dmitry Eremin-Solenikov
2011-12-13 23:41 ` Paul Eggleton [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=2795170.GPyksbkBvZ@helios \
--to=paul.eggleton@linux.intel.com \
--cc=dbaryshkov@gmail.com \
--cc=openembedded-devel@lists.openembedded.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.