On 06/08/2012 04:02 PM, Darren Hart wrote:


On 06/08/2012 03:23 PM, nitin.a.kam...@intel.com wrote:
From: Nitin A Kamble<nitin.a.kam...@intel.com>

perl needs eglibc to build.
The presence of runtime dependency of
perl for eglibc-mtrace caused bitbake to build perl before eglibc,
which causes build failure of perl with poky-tiny distro


So is this a circular dependency chain?

perl DEPENDS on eglibc
eglibc (because of eglibc-mtrace) RDEPENDS on perl?

If so, doesn't this solution leave eglibc-mtrace with an incomplete set
of dependencies in it's final package meta-data?

Would the correct solution be to break eglibc-mtrace out into a separate
recipe.

I am not sure if this would be more correct or have the PACKAGES contain something like ${EGLIBC_PACKAGE_MTRACE}, which could the be over-ridden by the yocto-tiny distro.

EGLIBC_PACKAGE_MTRACE ?= "${PN}-mtrace"

and then change ${PN}-mtrace in the PACKAGES list to ${EGLIBC_PACKAGE_MTRACE}.

This exposes another "global", so I am not sure which is better.

Sau!


eglibc-mtrace.bb could then DEPENDS=eglibc and RDEPENDS=perl and
poky-tiny would need to be able to exclude eglibc-mtrace.


   This fixes bug: [YOCTO #2523]

Signed-off-by: Nitin A Kamble<nitin.a.kam...@intel.com>
---
  meta/recipes-core/eglibc/eglibc-package.inc |    1 -
  1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/meta/recipes-core/eglibc/eglibc-package.inc 
b/meta/recipes-core/eglibc/eglibc-package.inc
index ce37155..423729a 100644
--- a/meta/recipes-core/eglibc/eglibc-package.inc
+++ b/meta/recipes-core/eglibc/eglibc-package.inc
@@ -55,7 +55,6 @@ FILES_${PN}-dbg += "${libexecdir}/*/.debug 
${libdir}/audit/.debug"
  FILES_catchsegv${PKGSUFFIX} = "${bindir}/catchsegv"
  RDEPENDS_catchsegv${PKGSUFFIX} = "libsegfault"
  RDEPENDS_${PN}-utils += "bash"
-RDEPENDS_${PN}-mtrace += "perl"
  FILES_${PN}-pcprofile = "${base_libdir}/libpcprofile.so"
  FILES_eglibc-thread-db${PKGSUFFIX} = "${base_libdir}/libthread_db.so.* 
${base_libdir}/libthread_db-*.so"
  RPROVIDES_${PN}-dev += "libc-dev"

_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to