From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Fabien Chereau <fabien.chereau@intel.com>
Cc: Openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] libusb: add missing build dependency on udev
Date: Sun, 29 Jun 2014 10:05:32 +0100 [thread overview]
Message-ID: <1404032732.28648.30.camel@ted> (raw)
In-Reply-To: <1403778002-10155-1-git-send-email-fabien.chereau@intel.com>
On Thu, 2014-06-26 at 12:20 +0200, Fabien Chereau wrote:
> This fixes the ./configure error in case libusb is built before udev/systemd.
>
> Signed-off-by: Fabien Chereau <fabien.chereau@intel.com>
> ---
> meta/recipes-support/libusb/libusb1_1.0.19.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-support/libusb/libusb1_1.0.19.bb b/meta/recipes-support/libusb/libusb1_1.0.19.bb
> index a20e1fc..be2be9d 100644
> --- a/meta/recipes-support/libusb/libusb1_1.0.19.bb
> +++ b/meta/recipes-support/libusb/libusb1_1.0.19.bb
> @@ -6,6 +6,8 @@ SECTION = "libs"
> LICENSE = "LGPLv2.1+"
> LIC_FILES_CHKSUM = "file://COPYING;md5=fbc093901857fcd118f065f900982c24"
>
> +DEPENDS_append = " udev"
> +
> BBCLASSEXTEND = "native nativesdk"
>
> SRC_URI = "${SOURCEFORGE_MIRROR}/libusb/libusb-${PV}.tar.bz2 \
This causes the build to explode with circular dependency issues. How
did you test this?
https://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/builds/147/steps/BuildImages/logs/stdio
There is a second error about a missing nativesdk-udev dependency (to
build nativesdk-libusb1) too.
Cheers,
Richard
next prev parent reply other threads:[~2014-06-29 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 10:20 [PATCH] libusb: add missing build dependency on udev Fabien Chereau
2014-06-29 9:05 ` Richard Purdie [this message]
2014-06-30 14:10 ` Chereau, Fabien
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=1404032732.28648.30.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=Openembedded-core@lists.openembedded.org \
--cc=fabien.chereau@intel.com \
/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