This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: error to run systemtap in an ARM platform
Da Zheng <zhengda1936@gmail.com> writes:
> I tried to compile my script with
> $ stap -v syscalls_by_pid.stp -a arm -r
> /build/tegra2_seaboard/tmp/portage/sys-kernel/chromeos-kernel-9999/work/chromeos-kernel-9999/build/tegra2_seaboard -p 4 -k
> [...]
> Pass 3: translated to C into "/tmp/stapsWo8wq/stap_23913.c" using
> 159984virt/87692res/5400shr kb, in 240usr/0sys/237real ms.
> cc1: error: unrecognized command line option "-mlittle-endian"
> cc1: error: unrecognized command line option "-mapcs"
> cc1: error: unrecognized command line option "-mno-sched-prolog"
> cc1: error: unrecognized command line option "-mabi=aapcs-linux"
> cc1: error: unrecognized command line option "-mno-thumb-interwork"
> /tmp/stapsWo8wq/stap_23913.c:1: error: bad value (armv5t) for -march= switch
> /tmp/stapsWo8wq/stap_23913.c:1: error: bad value (armv5t) for -mtune= switch
> [...]
> I use armv7a-cros-linux-gnueabi-gcc to cross compile the kernel and
> other software. How can I specify the compiler for cross compile? I
> tried to set the environment variable CC, but it doesn't work.
How did you tell kbuild to use that compiler? Environment variables,
or some kernel Makefile edit? Have you ever built an out-of-tree
kernel module via cross compilation?
- FChE