Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: yocto@yoctoproject.org,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [yocto] [PATCH 1/1] eglibc: remove runtime dependency of perl from eglibc-mtrace
Date: Mon, 11 Jun 2012 15:07:15 -0700	[thread overview]
Message-ID: <4FD66C13.8010603@linux.intel.com> (raw)
In-Reply-To: <4FD28477.9020201@linux.intel.com>

On 06/08/2012 04:02 PM, Darren Hart wrote:
>
>
> On 06/08/2012 03:23 PM, nitin.a.kamble@intel.com wrote:
>> From: Nitin A Kamble<nitin.a.kamble@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.kamble@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"
>



  reply	other threads:[~2012-06-11 22:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08 22:23 [PATCH 0/1] a fix for poky-tiny nitin.a.kamble
2012-06-08 22:23 ` [PATCH 1/1] eglibc: remove runtime dependency of perl from eglibc-mtrace nitin.a.kamble
2012-06-08 23:02   ` Darren Hart
2012-06-11 22:07     ` Saul Wold [this message]
2012-06-11 22:08       ` [yocto] " Darren Hart
2012-06-11 22:25       ` Khem Raj

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=4FD66C13.8010603@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yocto@yoctoproject.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