From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: tom.zanussi@intel.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] perf: add bison and flex to DEPENDS
Date: Sun, 26 Aug 2012 09:35:14 +0100 [thread overview]
Message-ID: <1345970114.7252.10.camel@ted> (raw)
In-Reply-To: <dc1953f169a835ec6b1dd04c78d61900f0fb53d5.1345935181.git.tom.zanussi@intel.com>
On Sat, 2012-08-25 at 17:57 -0500, tom.zanussi@intel.com wrote:
> From: Tom Zanussi <tom.zanussi@intel.com>
>
> perf depends on bison and flex for event parsing - add them as
> dependencies.
Does it need these at build time or runtime? I suspect you meant to add
these as RDEPENDS as it needs them at runtime?
Cheers,
Richard
>
> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
> ---
> meta/recipes-kernel/perf/perf_3.4.bb | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/meta/recipes-kernel/perf/perf_3.4.bb b/meta/recipes-kernel/perf/perf_3.4.bb
> index 5fb38e6..decc911 100644
> --- a/meta/recipes-kernel/perf/perf_3.4.bb
> +++ b/meta/recipes-kernel/perf/perf_3.4.bb
> @@ -9,7 +9,7 @@ as well."
> LICENSE = "GPLv2"
> LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
>
> -PR = "r4"
> +PR = "r5"
>
> require perf.inc
>
> @@ -24,6 +24,7 @@ DEPENDS = "virtual/kernel \
> ${MLPREFIX}binutils \
> ${TUI_DEPENDS} \
> ${SCRIPTING_DEPENDS} \
> + bison flex \
> "
>
> SCRIPTING_RDEPENDS = "${@perf_feature_enabled('perf-scripting', 'perl perl-modules python', '',d)}"
next prev parent reply other threads:[~2012-08-26 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-25 22:57 [PATCH 0/1] add flex/bison to perf DEPENDS tom.zanussi
2012-08-25 22:57 ` [PATCH 1/1] perf: add bison and flex to DEPENDS tom.zanussi
2012-08-26 8:35 ` Richard Purdie [this message]
2012-08-26 15:00 ` Tom Zanussi
2012-08-29 22:19 ` [PATCH 0/1] add flex/bison to perf DEPENDS Saul Wold
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=1345970114.7252.10.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=tom.zanussi@intel.com \
/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