From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2 3/3] systemtap: build and install uprobes.ko
Date: Fri, 27 Jan 2012 10:05:59 +0000 [thread overview]
Message-ID: <1327658759.19643.446.camel@ted> (raw)
In-Reply-To: <4F21AA4B.607@mentor.com>
On Thu, 2012-01-26 at 12:32 -0700, Wade Farnsworth wrote:
> SystemTap needs to provide uprobes.ko in order to support user space
> probing. Build and install the module on systems that support it.
>
> Additionally, split off common bits into systemtap_git.inc.
>
> Signed-off-by: Wade Farnsworth <wade_farnsworth@mentor.com>
> ---
> .../systemtap/systemtap-uprobes_git.bb | 42 ++++++++++++++++++++
> meta/recipes-kernel/systemtap/systemtap_git.bb | 18 +-------
> meta/recipes-kernel/systemtap/systemtap_git.inc | 16 +++++++
> 3 files changed, 61 insertions(+), 15 deletions(-)
> create mode 100644 meta/recipes-kernel/systemtap/systemtap-uprobes_git.bb
> create mode 100644 meta/recipes-kernel/systemtap/systemtap_git.inc
>
> diff --git a/meta/recipes-kernel/systemtap/systemtap-uprobes_git.bb b/meta/recipes-kernel/systemtap/systemtap-uprobes_git.bb
> new file mode 100644
> index 0000000..7ae9cb8
> --- /dev/null
> +++ b/meta/recipes-kernel/systemtap/systemtap-uprobes_git.bb
> @@ -0,0 +1,42 @@
> +DESCRIPTION = "UProbes kernel module for SystemTap"
> +
> +require systemtap_git.inc
> +
> +DEPENDS = "virtual/gettext systemtap virtual/kernel"
> +
> +PR = "r0"
> +
> +# On systems without CONFIG_UTRACE, this package is empty.
> +ALLOW_EMPTY = 1
This should really be:
ALLOW_EMPTY_${PN} = "1"
Cheers,
Richard
next prev parent reply other threads:[~2012-01-27 10:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 21:46 [PATCH 0/3] systemtap enhancements Wade Farnsworth
2012-01-24 21:47 ` [PATCH 1/3] Bump systemtap SRCREV Wade Farnsworth
2012-01-24 21:48 ` [PATCH 2/3] systemtap: extend the recipe to build the native package Wade Farnsworth
2012-01-24 21:49 ` [PATCH 3/3] systemtap: build and install uprobes.ko Wade Farnsworth
2012-01-24 23:38 ` Khem Raj
2012-01-26 19:30 ` [PATCH v2 0/3] systemtap enhancements Wade Farnsworth
2012-01-26 19:31 ` [PATCH v2 1/3] Bump systemtap SRCREV Wade Farnsworth
2012-01-26 19:31 ` [PATCH v2 2/3] systemtap: extend the recipe to build the native package Wade Farnsworth
2012-01-27 10:03 ` Richard Purdie
2012-01-26 19:32 ` [PATCH v2 3/3] systemtap: build and install uprobes.ko Wade Farnsworth
2012-01-27 10:05 ` Richard Purdie [this message]
2012-02-03 19:28 ` [PATCH v3 0/3] systemtap enhancements Wade Farnsworth
2012-02-03 19:28 ` [PATCH v3 1/3] systemtap: bump SRCREV to grab version 1.7 Wade Farnsworth
2012-02-03 20:31 ` Khem Raj
2012-02-03 19:29 ` [PATCH v3 2/3] systemtap: extend the recipe to build the native package Wade Farnsworth
2012-02-03 19:30 ` [PATCH v3 3/3] systemtap: build and install uprobes.ko Wade Farnsworth
2012-02-03 20:55 ` Khem Raj
2012-02-06 14:47 ` [PATCH v4 0/3] systemtap enhancements Wade Farnsworth
2012-02-06 14:47 ` [PATCH v4 1/3] systemtap: bump SRCREV to grab version 1.7 Wade Farnsworth
2012-02-08 4:05 ` Saul Wold
2012-02-06 14:48 ` [PATCH v4 2/3] systemtap: extend the recipe to build the native package Wade Farnsworth
2012-02-06 14:49 ` [PATCH v4 3/3] systemtap: build and install uprobes.ko Wade Farnsworth
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=1327658759.19643.446.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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