From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Anders Darander <anders@chargestorm.se>
Subject: Re: [meta-oe][PATCH 1/1] ktap: add configs for elfutils and ffi
Date: Tue, 7 Jan 2014 14:08:49 +0100 [thread overview]
Message-ID: <20140107130849.GP3709@jama> (raw)
In-Reply-To: <9df199bd032977929fa715af7710e4607a19f91e.1389098317.git.anders@chargestorm.se>
[-- Attachment #1: Type: text/plain, Size: 3220 bytes --]
On Tue, Jan 07, 2014 at 01:39:49PM +0100, Anders Darander wrote:
> libelf (elfutils) is required for resolving symbols in DSO and for sdt (taken
> from ktap docs). The earlier v0.4 recipe built ktap against libelf if it was
> found, thus enable it per default.
>
> FFI needs to be enabled for both userspace and kernel module. Currently, it is
> only supported for x86_64 (enforced when building ktap-module).
>
> Signed-off-by: Anders Darander <anders@chargestorm.se>
> ---
> meta-oe/recipes-kernel/ktap/ktap-module_0.4.bb | 5 ++++-
> meta-oe/recipes-kernel/ktap/ktap.inc | 2 ++
> meta-oe/recipes-kernel/ktap/ktap_0.4.bb | 12 +++++++++++-
> 3 files changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/meta-oe/recipes-kernel/ktap/ktap-module_0.4.bb b/meta-oe/recipes-kernel/ktap/ktap-module_0.4.bb
> index 12167ea..ce6885c 100644
> --- a/meta-oe/recipes-kernel/ktap/ktap-module_0.4.bb
> +++ b/meta-oe/recipes-kernel/ktap/ktap-module_0.4.bb
> @@ -6,8 +6,11 @@ DESCRIPTION = "KTAP is a scripting dynamic tracing tool for Linux"
>
> inherit module
>
> +# Available package configs: ffi (only supported on x86_64)
> +PACKAGECONFIG ?= ""
> +
> # Only build the module
> -MAKE_TARGETS = "mod"
> +MAKE_TARGETS = "${@base_contains('PACKAGECONFIG', 'ffi', 'FFI=1', '', d)} mod"
>
> # Kernel module packages MUST begin with 'kernel-module-', otherwise
> # multilib image generation can fail.
> diff --git a/meta-oe/recipes-kernel/ktap/ktap.inc b/meta-oe/recipes-kernel/ktap/ktap.inc
> index 7e60453..93a4e2c 100644
> --- a/meta-oe/recipes-kernel/ktap/ktap.inc
> +++ b/meta-oe/recipes-kernel/ktap/ktap.inc
> @@ -9,3 +9,5 @@ SRC_URI = "git://github.com/ktap/ktap.git"
>
> S = "${WORKDIR}/git"
>
> +# Package config is abused as a general compile time configuration tool.
> +PACKAGECONFIG[ffi] = ""
> diff --git a/meta-oe/recipes-kernel/ktap/ktap_0.4.bb b/meta-oe/recipes-kernel/ktap/ktap_0.4.bb
> index f5dd62f..a703aec 100644
> --- a/meta-oe/recipes-kernel/ktap/ktap_0.4.bb
> +++ b/meta-oe/recipes-kernel/ktap/ktap_0.4.bb
> @@ -5,8 +5,18 @@ require ktap.inc
> SUMMARY = "KTAP is a scripting dynamic tracing tool for Linux"
> DEPENDS = "ktap-module"
>
> +#Available package configs:
> +# libelf - needed to resolve symbols in DSO and for sdt
> +# ffi - only supports x86_64 for now!. Needs to be enabled for ktap-module too.
> +PACKAGECONFIG ?= "libelf"
> +
> +PACKAGECONFIG[libelf] = ",,elfutils"
> +PACKAGECONFIG[ffi] = ""
This line is already in ktap.inc
Otherwise looks good, I like deterministic shiny things.
> +
> # Only build the userspace app
> -EXTRA_OEMAKE = "ktap"
> +EXTRA_OEMAKE = "${@base_contains('PACKAGECONFIG', 'libelf', '', 'NO_LIBELF=1', d)} \
> + ${@base_contains('PACKAGECONFIG', 'ffi', 'FFI=1', '', d)} \
> + ktap"
>
> do_install() {
> install -d ${D}${bindir}
> --
> 1.8.5.2
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
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:[~2014-01-07 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 12:39 [meta-oe][PATCH 0/1] ktap: deterministic build Anders Darander
2014-01-07 12:39 ` [meta-oe][PATCH 1/1] ktap: add configs for elfutils and ffi Anders Darander
2014-01-07 13:08 ` Martin Jansa [this message]
2014-01-07 13:31 ` Anders Darander
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=20140107130849.GP3709@jama \
--to=martin.jansa@gmail.com \
--cc=anders@chargestorm.se \
--cc=openembedded-devel@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 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.