linux/poky.git/meta/recipes-kernel/systemtap, branch yocto-2.4.4

systemtap: Bump SRCREV for 4.12 Linux kernel support

2017-09-11T16:30:29+00:00

This SRCREV bump brings in support for the 4.12 Linux Kernel, this kernel also has some newer CONFIG settings. The newer DEBUG_INFO and DEBUG_INFO_DWARF4 settings can be used with systemtap to get the full information. We do not normally enabled these for a 'production' (standard) kernel, but can be enabled via menuconfig. When installing staprun and stapbpf on the target and native ensure we don't try to create a new group and chown it. There is no need since we will be running as root, so we add a patch to comment that code out. (From OE-Core rev: 026403cc7f995ecc32a99f269399a08abc221c77) Signed-off-by: Saul Wold Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

systemtap: Add HOMEPAGE info into recipe file.

2017-09-05T14:01:01+00:00

(From OE-Core rev: 492f43f1aa402a60902fafb2d524ae67007f59bd) Signed-off-by: Fan Xin Signed-off-by: Richard Purdie

rm_work: Improve handling for addto_recipe_sysroot

2017-07-31T14:13:31+00:00

Rather than requiring each user to handle this individually, handle addto_recipe_sysroot in the core class. As well as preserving the sysroot directory, this also ensures the stamp is preserved rather than rerunning the task every time as currently happens. (From OE-Core rev: bf8b9858d9ccce27173d13938a83d249294cc473) Signed-off-by: Richard Purdie

systemtap: ensure systemtap-native is available

2017-07-30T07:46:19+00:00

Since we are adding the addto_sysroot that that is specific to the native recipe, we must split this into a seperate -native .bb recipe. When systemtap-native is built, the intention is that it's usable from the native sysroot when done, ensure it's there with a forced addto_recipe_sysroot task, we also don't want to clean the sysroot when RM_WORK is enabled otherwise we loose the binaries. [YOCTO #11403] (From OE-Core rev: 98fba18e93abe8efce0a5b40d51e178c9de4d1e5) Signed-off-by: Saul Wold (cherry picked from commit 2fdb59741b4fdeaa4aee10812c4a409cdc11a02d) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

systemtap: Add patch to remove quotes

2017-03-08T11:52:56+00:00

This fixes the -I include lines that are getting passed to the kernel macros [YOCTO #10990] (From OE-Core rev: b4d2f41a474c111e5fc64cae635d851386d860ba) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

systemtap: update to 3.1

2017-03-01T23:27:09+00:00

Removed patches are in upstream. Rebase monitor-option.patch and no-msgfmt-check.patch Add support for python 3 probes (this necessitates the 0001-Do-not-let-configure-write-a-python-location-into-th.patch and the Add 0001-Install-python-modules-to-correct-library-dir.patch to install python modules to correct destination). Add perl to RDEPENDS to fix a QA warning about one of the installed files. (From OE-Core rev: e3bccfba499565ea13f154a11dadcab48ef5e0ab) Signed-off-by: Alexander Kanavin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

systemtap: fix native linking on recent Ubuntu

2016-11-15T15:19:54+00:00

The latest Ubuntu uses yet more aggressive hardening options, which causes the unconventional build order used by systemtap to fail. [ YOCTO #10521 ] (From OE-Core rev: 5ca6ac8739ea4a273df7b8e5c5f7d481619923d8) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

systemtap: remove explicit msgfmt check

2016-11-15T15:19:54+00:00

Passing --disable-nls should be enough to disable the requirement for a full gettext to be present, but the upstream configure explicitly checks for msgfmt even if it isn't going to be used. To avoid having to depend on gettext-native, patch this check out. (From OE-Core rev: 2f8d2a74f73490c1ae35131d3eb3592f7ee0a1e4) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

systemtap: rationalise dependencies

2016-10-05T09:10:10+00:00

Boost is an optional dependency but avoid build non-determinism by adding it as DEPENDS. It is only for the shared pointer types so can be disabled explicitly if required. Turn sqlite into a PACKAGECONFIG. Add a patch for the "monitor" feature to control the optional dependencies on ncurses and json-c. Previously this was enabled for target only but enable it everwhere now that json-c is available for native/nativesdk. Of course all of this was predicated about systemtap needing systemtap-native to be built, but it turns out that this dependency is due to oe-core 507bd2 which adds systemtap-native as DEPENDS for convenience. Remove this dependency, if the user wants systemtap-native then they can build it explicitly. (From OE-Core rev: fb9dc1cf7a2d6d5e22beb68f17b4c9c8d1136e37) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

systemtap: remove EXTRA_OEMAKE workaround

2016-09-03T08:58:40+00:00

The default of EXTRA_OEMAKE is already empty since commit: OE-Core rev: aeb653861a0ec39ea7a014c0622980edcbf653fa bitbake.conf: Remove unhelpful default value for EXTRA_OEMAKE (From OE-Core rev: 4c1d679a0fd601ba37ab37b11f660cc41d8507ff) Signed-off-by: Stefan Müller-Klieser Signed-off-by: Richard Purdie