summaryrefslogtreecommitdiffstats
path: root/meta-oe/recipes-kernel/ktap/ktap_0.4.bb
Commit message (Collapse)AuthorAgeFilesLines
* ktap: add libelf PACKAGECONFIG also to ktap-moduleMartin Jansa2015-11-091-10/+1
| | | | | | | * building ktap-module without elfutils fails with: ktap-module/0.4-r0/git/Makefile:107: No libelf found, disables symbol resolving, please install elfutils-libelf-devel/libelf-dev Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* ktap: Set MACHINE_ARCH because of ktap-module runtime dependencyMartin Jansa2014-06-251-1/+1
| | | | | | | | | | | * it's possible to exclude ktap-module dependency from siggen, but then we would need to exclude virtual/kernel and that doesn't work we would need to list all posisble providers as ktap->linux-yocto ktap->linux-foo .... Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* ktap: add configs for elfutils and ffiAnders Darander2014-01-151-1/+10
| | | | | | | | | | | | 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> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* ktap: upgrade to 0.4Martin Jansa2014-01-011-0/+17
* tag v0.3 (and its SRCREV) doesn't exist in any branch so latest bitbake refuses to fetch it Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>