14:03 <NebuK_work> heho

14:04 <NebuK_work> i’m currently trying to build systemtap into openwrt/lede. their build-process works by first compiling their own cross toolchain and a set of host-sided tools, then building the target-architecture/platform kernel, packages, etc

14:06 <NebuK_work> did i get it right that on the target, i *only* need the systemtap-runtime? and on the host-side, i’d want a host-arch-build of all the other tools … which grab-their-information-from / write-code-and-modules-for the target-arch kernel, which i pointed them to?

14:07 <NebuK_work> (stap-runtime + instrumentation module on the target, i mean)

14:12 <fche> you are correct

14:12 <NebuK_work> ah

14:12 <NebuK_work> and i just found this: http://omappedia.org/wiki/Systemtap

14:12 <NebuK_work> thanks ^_^

14:12 <fche> and see also general systemtap cross-compilation

14:12 <fche> e.g.

14:13 <fche> https://sourceware.org/systemtap/SystemTap_Beginners_Guide/cross-compiling.html

14:13 <fche> or https://sourceware.org/systemtap/wiki/SystemtapOnFedoraArm

14:14 <NebuK_work> yeah, the first one i’ve already found, but it only deals with different kernel but same arch/platform, right?

14:14 <NebuK_work> which confused me in the beginning

14:25 <NebuK_work> http://nopaste.ghostdub.de/view/a78c1a3a

14:25 <NebuK_work> hmm, i’m doing something wrong here i guess?

14:27 <fche> did you do a make-install first for the host-side systemtap tooling?

14:27 <fche> (asking because you're running ./stap ... if that's a build tree stap without a make-install, then it may not find its standard tapset)

14:27 <NebuK_work> it’s from build-tree, i fear

14:27 <fche> can still use it there if you must (run-stap.sh or something nearby)

14:28 <fche> but best if you make-install

14:28 <fche> just %configure it to some private directory if you don't want /usr/local or /usr

14:28 <NebuK_work> ah, i overlooked that script

14:40 <NebuK_work> hm, what does this actually mean? WARNING: kernel release/architecture mismatch with host forces last-pass 4.

14:42 <fche> stap FOO.stp means to run the script

14:42 <fche> if the current host doesn't match the target host, it can't possibly run it here

14:43 <fche> so it will only compile the script to a .ko (i.e., stop at pass 4)

14:50 <NebuK_work> ah, that it means

14:50 <NebuK_work> thx ^_^

15:19 <irker882> systemtap: mcermak systemtap.git:refs/heads/master * release-3.0-298-gb3b87c6 / : Fix PR14924 by warning when not using @entry($var) in a return probe. http://tinyurl.com/h58pcj5

17:36 <irker882> systemtap: fche systemtap.git:refs/heads/master * release-3.0-299-ga372ac4 / rpm_finder.cxx: rpm_finder: colorize "missing kernel-devel" or "-debuginfo" messages http://tinyurl.com/h7ownso

17:36 <irker882> systemtap: fche systemtap.git:refs/heads/master * release-3.0-300-g09dd8f0 / elaborate.cxx main.cxx staptree.cxx tapsets.cxx testsuite/buildok/fortyfour.stp: PR20821/PR14924: further gradual deprecation of .return { $var } use http://tinyurl.com/glfcefu

18:54 <irker882> systemtap: dsmith systemtap.git:refs/heads/dsmith/python * release-3.0-291-ga003a31 / tapset-python.cxx tapset/python2.stp tapset/python3.stp: Add support for '$$parms', '$$locals', and '$$vars' in python 3 probes. http://tinyurl.com/hnkffyx