All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: McClintock Matthew-B29882 <B29882@freescale.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Phil Blundell <philb@gnu.org>,
	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, 04 Jan 2012 15:38:22 +0000	[thread overview]
Message-ID: <1325691502.20759.17.camel@ted> (raw)
In-Reply-To: <CAEsOVNdBy7uAtJnMmOBLMobXg=XHfpsrgTvmDOz9=pszh7hHLg@mail.gmail.com>

On Wed, 2012-01-04 at 04:39 +0000, McClintock Matthew-B29882 wrote:
> On Tue, Jan 3, 2012 at 10:31 PM, Garg Vakul-B16394 <B16394@freescale.com> wrote:
> > Hi Matthew
> >
> > I am not sure if I understood your point fully.
> >
> > I am suggesting to do below mentioned as suggested on valgrind page.
> > http://valgrind.org/docs/manual/dist.readme-packagers.html
> >
> >
> > "If you don't want to leave symbols on ld.so, alternatively you can
> have your distro install ld.so's debuginfo package by default, or make
> ld.so.debuginfo be a requirement of your Valgrind RPM/DEB/whatever."
> 
> This is what I am suggest. If we include valgrind in an image and the
> arch is powerpc or powerpc64, we need to include ld.so with debug
> symbols by default. Otherwise valgrind will not work at all. This
> seems like a reasonable thing to do for these two arches.

I think the RRECOMMENDS on ppc only is therefore the right solution for
now. 

There is perhaps a case here for splitting out the ld.so -dbg from the
rest of libc so the installation requirements aren't so large.

Cheers,

Richard




      parent reply	other threads:[~2012-01-04 15:45 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
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 [this message]

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=1325691502.20759.17.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=B16394@freescale.com \
    --cc=B19537@freescale.com \
    --cc=B29882@freescale.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=philb@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.