From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] libusb1/libusb-compat keep *.la in base_libdir
Date: Wed, 11 Jan 2012 22:38:25 -0800 [thread overview]
Message-ID: <4F0E7FE1.8020409@linux.intel.com> (raw)
In-Reply-To: <1326045849-21938-1-git-send-email-schnitzeltony@gmx.de>
On 01/08/2012 10:04 AM, Andreas Müller wrote:
> libusb-compat did not yet cause a build error but it is motivated by the
> experience with libusb1.
>
> I will be out until 12. and can not respond on comments until then.
>
> Andreas Müller (2):
> libusb1: keep *.la in base_libdir
> libusb-compat: keep *.la in base_libdir
>
> meta/recipes-support/libusb/libusb-compat_0.1.3.bb | 3 +--
> meta/recipes-support/libusb/libusb1_1.0.8.bb | 3 +--
> 2 files changed, 2 insertions(+), 4 deletions(-)
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-01-12 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 18:04 [PATCH 0/2] libusb1/libusb-compat keep *.la in base_libdir Andreas Müller
2012-01-08 18:04 ` [PATCH 1/2] libusb1: " Andreas Müller
2012-01-08 18:04 ` [PATCH 2/2] libusb-compat: " Andreas Müller
2012-01-12 6:38 ` Saul Wold [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=4F0E7FE1.8020409@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox