Support for the ARM 64 bit CPU architecture (aarch64) was introduced in autoconf 2.69. systemtap appears to use an earlier version of autoconf, preventing its being built. This can be fixed in of three ways (In order of preference): 1. Work with upstream to migrate the package to autoconf 2.69. 2. Rerun autoconf or autoreconf in %prep or %build prior to running configure. 3. Apply the patch at http://ausil.fedorapeople.org/aarch64/systemtap/systemtap-aarch64.patch which updates config.guess and config.sub to recognize aarch64.
Upstream migrated to autoconf 2.69 in commit 76df176fdceb33c14a07a74b2dc70e72b13fc1b7 Systemtap has been respun as needed in Fedora 19 (http://koji.fedoraproject.org/koji/taskinfo?taskID=5176066) We're just waiting on BZ927996 to get systemtap respun with the new autoconf version in rawhide
What needs additional work needs to be done for systemtap to function on aarch64: kernel kprobes support kernel uprobes support systemtap runtime: stack and stack unwind support regs.h systemtap translator need machine specific code fixed in: tapsets.cxx util.cxx dwflpp.cxx systemtap tapset: tapset/aarch64/registers.stp for no-debuginfo syscall probing
We also need an elfutil ARM64 libebl backend. To decode relocations in kernel modules and DWARF register mappings plus initial CFI values.
(In reply to Mark Wielaard from comment #3) > We also need an elfutil ARM64 libebl backend. To decode relocations in > kernel modules and DWARF register mappings plus initial CFI values. Most of that is there now on a branch. https://git.fedorahosted.org/cgit/elfutils.git/log/?h=pmachata/aarch64 Not yet integrated into upstream master.