Philipp Kern <[email protected]> writes: > Checking "/lib/modules/2.6.32-5-s390x/build/.config" failed with error: No > such file or directory > > I did install the linux-image package from the s390 host within the > chroot with --force-architecture, but that doesn't give me its .config > in the right place. Should it be enough to place the .config there or > does it need to be a full kernel build tree?
Sorry for not mentioning all this in the initial email. As listed in README.Debian you need linux-headers*, linux-kbuild* and linux-image-*-dbg that match the running kernel so that systemtap can build kernel modules. I really wish systemtap could just depend on these but afaik it is not possible. I wrote http://lindi.iki.fi/lindi/systemtap/diagnose-error-cases.bash that should give you a list of packages that you need. Upstream has integrated similar functionality for redhat/fedora but I don't think my proof-of-concept is ready for upstream inclusion yet. My guess is that you need: linux-image-2.6.32-5-s390x linux-image-2.6.32-5-s390x-dbg linux-headers-2.6.32-5-s390x linux-kbuild-2.6.32 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
