Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: McClintock Matthew-B29882 <B29882@freescale.com>,
	Garg Vakul-B16394 <B16394@freescale.com>,
	Luo Zhenhua-B19537 <B19537@freescale.com>
Subject: Re: [PATCH oe-core] valgrind: add powerpc to the compatible host and add eglibc-dbg in rdepends
Date: Wed, 28 Dec 2011 10:18:40 +0000	[thread overview]
Message-ID: <2295923.3R0Nmqr59V@helios> (raw)
In-Reply-To: <CA452391058F6D4E9715FB2C29D9312A010BD589@039-SN2MPN1-023.039d.mgd.msft.net>

On Wednesday 28 December 2011 10:01:13 Luo Zhenhua-B19537 wrote:
> May I know what's the concern with eglibc instead of uclibc?

So my concern is, if you add a runtime dependency on eglibc-dbg to valgrind 
and you've selected uclibc instead, it will force installation of eglibc when 
you install valgrind (not to mention building it when you build valgrind); 
this is almost certainly not what you want.

If a dependency on the libc debug packages is really needed you could do 
something this instead:

RRECOMMENDS_${PN} += "${TCLIBC}-dbg"

(I suggest using RRECOMMENDS here rather than RDEPENDS in case here is no such 
debug package for the user's selected libc.)

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2011-12-28 10:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28  6:55 [PATCH oe-core] valgrind: add powerpc to the compatible host and add eglibc-dbg in rdepends b19537
2011-12-28  9:14 ` Paul Eggleton
2011-12-28 10:01   ` Luo Zhenhua-B19537
2011-12-28 10:18     ` Paul Eggleton [this message]
2011-12-28 10:32       ` Koen Kooi
2011-12-28 12:15         ` Martin Jansa
2011-12-28 19:16           ` McClintock Matthew-B29882
2011-12-29  2:20             ` Luo Zhenhua-B19537
2011-12-28 20:20   ` Phil Blundell
2011-12-29  2:19     ` Luo Zhenhua-B19537
2012-01-03 11:44       ` Phil Blundell
     [not found]         ` <065BBB7616BCE543832A2EF096986B94018AA0@039-SN2MPN1-011.039d.mgd.msft.net>
2012-01-04  4:07           ` McClintock Matthew-B29882
     [not found]             ` <065BBB7616BCE543832A2EF096986B94018AC3@039-SN2MPN1-011.039d.mgd.msft.net>
2012-01-04  4:26               ` McClintock Matthew-B29882
     [not found]                 ` <065BBB7616BCE543832A2EF096986B94018ADB@039-SN2MPN1-011.039d.mgd.msft.net>
2012-01-04  4:39                   ` McClintock Matthew-B29882
2012-01-04  5:25                     ` Khem Raj
2012-01-04 15:38                     ` Richard Purdie

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=2295923.3R0Nmqr59V@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=B16394@freescale.com \
    --cc=B19537@freescale.com \
    --cc=B29882@freescale.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