On Fri, 2012-10-12 at 10:44 -0700, Saul Wold wrote:
> On 09/25/2012 05:56 AM, Phil Blundell wrote:
> > This removes the dependency of eglibc.bb itself on perl and bash
> > which, in turn, eliminates the need to build those two recipes if the
> > scripts which need them are not going to be installed.
> >
> 
> I think you missed dealing with an RPOVIDES someplace as I am getting 
> the following error during build:
> 
> > ERROR: Nothing RPROVIDES 'libc-mtrace' (but 
> > /intel/poky/distro/meta/recipes-core/packagegroups/packagegroup-core-tools-debug.bb
> >  RDEPENDS on or otherwise requires it)
> > NOTE: Runtime target 'libc-mtrace' is unbuildable, removing...
> > Missing or unbuildable dependency chain was: ['libc-mtrace']
> > ERROR: Required build target 'packagegroup-core-tools-debug' has no 
> > buildable providers.
> > Missing or unbuildable dependency chain was: 
> > ['packagegroup-core-tools-debug', 'libc-mtrace']

Right, sorry about that.  The attached fixes this for me.

p.

>From 09acbe5c7b6c480400f7756f79cc13592416f4de Mon Sep 17 00:00:00 2001
From: Phil Blundell <[email protected]>
Date: Mon, 15 Oct 2012 10:45:11 +0100
Subject: [PATCH] eglibc-mtrace: Add libc-mtrace to PROVIDES

Signed-off-by: Phil Blundell <[email protected]>
---
 meta/recipes-core/eglibc/eglibc-mtrace.inc |    2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-core/eglibc/eglibc-mtrace.inc b/meta/recipes-core/eglibc/eglibc-mtrace.inc
index 321de7b..1ec93ac 100644
--- a/meta/recipes-core/eglibc/eglibc-mtrace.inc
+++ b/meta/recipes-core/eglibc/eglibc-mtrace.inc
@@ -1,8 +1,10 @@
 include eglibc-collateral.inc
 
+PR = "r1"
 SUMMARY = "mtrace utility provided by eglibc"
 DESCRIPTION = "mtrace utility provided by eglibc"
 RDEPENDS_${PN} = "perl"
+RPROVIDES_${PN} = "libc-mtrace"
 
 SRC = "${STAGING_INCDIR}/eglibc-scripts-internal-${MULTIMACH_TARGET_SYS}"
 
-- 
1.7.10.4

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Reply via email to