From: Wenji Huang <wenji.huang@oracle.com>
To: SystemTAP <systemtap@sources.redhat.com>
Subject: Compilation for tracepoint on 2.6.33-rc1
Date: Tue, 22 Dec 2009 03:26:00 -0000 [thread overview]
Message-ID: <4B303B64.8040003@oracle.com> (raw)
Hi,
There is compilation error for tracepoint on 2.6.33-rc1, see
$ sudo stap -we 'probe kernel.trace("kvm_mmio"),kernel.trace("sys*"){}'
In file included from
/tmp/stapOWxU0E/stap_978faaf75db7cd5c5160bd681e7d912e_688.c:271:
include/trace/events/syscalls.h:3:1: error: "TRACE_INCLUDE_FILE" redefined
In file included from
/tmp/stapOWxU0E/stap_978faaf75db7cd5c5160bd681e7d912e_688.c:151:
include/trace/events/kvm.h:8:1: error: this is the location of the
previous definition
make[1]: ***
[/tmp/stapOWxU0E/stap_978faaf75db7cd5c5160bd681e7d912e_688.o] Error 1
make: *** [_module_/tmp/stapOWxU0E] Error 2
Pass 4: compilation failed. Try again with another '--vp 0001' option.
On 2.6.33-rc1, TRACE_INCLUDE_FILE is defined both
include/trace/events/syscalls.h and include/trace/events/kvm.h without
leading #undef.
How to handle this, to push a patch of adding #undef before
#define TRACE_INCLUDE_FILE to LKML
or
emit "#undef TRACE_INCLUDE_FILE" before "#include <trace/events/*.h>"
to the generated C code?
Regards,
Wenji
next reply other threads:[~2009-12-22 3:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 3:26 Wenji Huang [this message]
2009-12-22 20:24 ` Josh Stone
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B303B64.8040003@oracle.com \
--to=wenji.huang@oracle.com \
--cc=systemtap@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).