From: Martin Jansa <martin.jansa@gmail.com>
To: Felipe Tonello <eu@felipetonello.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] valgrind: added perl dependency
Date: Fri, 7 Jun 2013 20:37:30 +0200 [thread overview]
Message-ID: <20130607183730.GK22710@jama> (raw)
In-Reply-To: <CAGrhNMw_82j-RUx7gfdKMqawBQ=JhZ6cusRivSpv=aiU0mHW5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
On Fri, Jun 07, 2013 at 10:51:14AM -0700, Felipe Tonello wrote:
> I got this:
>
> valgrind/usr/bin/ms_print
> 1:#! /usr/bin/perl
>
> valgrind/usr/bin/cg_diff
> 1:#! /usr/bin/perl
>
> valgrind/usr/bin/cg_annotate
> 1:#! /usr/bin/perl
>
> valgrind/usr/bin/callgrind_annotate
> 1:#! /usr/bin/perl -w
>
> valgrind/usr/bin/callgrind_control
> 1:#! /usr/bin/perl -w
>
> valgrind-doc/usr/share/doc/valgrind/html/manual-core.html
> 165:<code class="filename">/usr/bin/perl</code>, or whatever interpreter
>
> valgrind-doc/usr/share/doc/valgrind/valgrind_manual.ps
> 55978:(/usr/bin/perl) 77.7083 Tj
>
> Do you know if these "binaries" are part of the main package or can be
> extra? I'm not that familiar with valgrind.
Neither am I, but from filenames I would guess they are not mandatory to
run valgrind binary, hopefully someone who is using valgrind daily will
respond soon...
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-06-07 18:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 17:35 [PATCH] valgrind: added perl dependency eu
2013-06-07 17:42 ` Martin Jansa
2013-06-07 17:43 ` Martin Jansa
2013-06-07 17:47 ` Felipe Tonello
2013-06-07 17:51 ` Felipe Tonello
2013-06-07 18:37 ` Martin Jansa [this message]
2013-06-11 7:36 ` Khem Raj
2013-06-26 18:39 ` Felipe Tonello
2013-06-26 20:35 ` Saul Wold
2013-06-28 22:35 ` Khem Raj
2013-07-16 22:16 ` [PATCH v2] " eu
2013-07-16 22:54 ` Saul Wold
2013-07-16 23:09 ` Felipe Tonello
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=20130607183730.GK22710@jama \
--to=martin.jansa@gmail.com \
--cc=eu@felipetonello.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