public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/16914] probe syscall.* fails with compilation error
Date: Tue, 06 May 2014 19:42:00 -0000	[thread overview]
Message-ID: <bug-16914-6586-28RDauLb6e@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16914-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=16914

--- Comment #6 from Martin Cermak <mcermak at redhat dot com> ---
Hi David, now, with current upstream head, I'm getting: 

--------------------8<----------------------------------------------

S aarch64 # stap -e 'probe syscall.* { log("hey!"); exit() }'
In file included from
/tmp/stapnP5rLb/stap_1c56b4d79e886a846bcb2bcb2c11d0e9_143230_src.c:28:0:
/tmp/stapnP5rLb/stap_1c56b4d79e886a846bcb2bcb2c11d0e9_143230_src.c: In function
‘probe_2357’:
/usr/share/systemtap/runtime/linux/compat_unistd.h:116:32: error:
‘__NR_futimesat’ undeclared (first use in this function)
 #define __NR_compat_futimesat  __NR_futimesat
                                ^
/tmp/stapnP5rLb/stap_1c56b4d79e886a846bcb2bcb2c11d0e9_143230_src.c:12038:43:
note: in expansion of macro ‘__NR_compat_futimesat’
       if ((((l->l___nr) != ((((int64_t) ( __NR_compat_futimesat ))))))) {
                                           ^
/usr/share/systemtap/runtime/linux/compat_unistd.h:116:32: note: each
undeclared identifier is reported only once for each function it appears in
 #define __NR_compat_futimesat  __NR_futimesat
                                ^
/tmp/stapnP5rLb/stap_1c56b4d79e886a846bcb2bcb2c11d0e9_143230_src.c:12038:43:
note: in expansion of macro ‘__NR_compat_futimesat’
       if ((((l->l___nr) != ((((int64_t) ( __NR_compat_futimesat ))))))) {
                                           ^
/tmp/stapnP5rLb/stap_1c56b4d79e886a846bcb2bcb2c11d0e9_143230_src.c: In function
‘probe_2496’:
/tmp/stapnP5rLb/stap_1c56b4d79e886a846bcb2bcb2c11d0e9_143230_src.c:13332:33:
error: ‘__NR_futimesat’ undeclared (first use in this function)
           })) != ((((int64_t) ( __NR_futimesat ))))))) {
                                 ^
In file included from
/tmp/stapnP5rLb/stap_1c56b4d79e886a846bcb2bcb2c11d0e9_143230_src.c:28:0:
/tmp/stapnP5rLb/stap_1c56b4d79e886a846bcb2bcb2c11d0e9_143230_src.c: In function
‘probe_2700’:
/usr/share/systemtap/runtime/linux/compat_unistd.h:121:27: error: ‘__NR_open’
undeclared (first use in this function)
 #define __NR_compat_open  __NR_open
                           ^
/tmp/stapnP5rLb/stap_1c56b4d79e886a846bcb2bcb2c11d0e9_143230_src.c:14433:43:
note: in expansion of macro ‘__NR_compat_open’
       if ((((l->l___nr) != ((((int64_t) ( __NR_compat_open ))))))) {
                                           ^
/tmp/stapnP5rLb/stap_1c56b4d79e886a846bcb2bcb2c11d0e9_143230_src.c: At top
level:
/tmp/stapnP5rLb/stap_1c56b4d79e886a846bcb2bcb2c11d0e9_143230_src.c:17973:2:
error: #error "Need CONFIG_KPROBES!"
 #error "Need CONFIG_KPROBES!"
  ^
make[1]: ***
[/tmp/stapnP5rLb/stap_1c56b4d79e886a846bcb2bcb2c11d0e9_143230_src.o] Error 1
make: *** [_module_/tmp/stapnP5rLb] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compilation failed.  [man error::pass4]
S aarch64 #

--------------------8<----------------------------------------------

which, although apparently we're not yet there, looks much better!

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2014-05-06 19:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 14:00 [Bug translator/16914] New: " mcermak at redhat dot com
2014-05-06 14:00 ` [Bug translator/16914] " mcermak at redhat dot com
2014-05-06 14:30 ` dsmith at redhat dot com
2014-05-06 17:46 ` mcermak at redhat dot com
2014-05-06 18:17 ` jistone at redhat dot com
2014-05-06 18:36 ` dsmith at redhat dot com
2014-05-06 19:42 ` mcermak at redhat dot com [this message]
2014-05-06 20:05 ` dsmith at redhat dot com
2014-05-06 20:23 ` mcermak at redhat dot com
2014-05-06 20:44 ` dsmith at redhat dot com
2015-02-12 16:36 ` aram.h at mgk dot ro
2015-02-12 17:34 ` dsmith at redhat dot com
2015-02-12 18:18 ` aram.h at mgk dot ro
2015-02-12 19:07 ` dsmith at redhat dot com
2015-02-12 21:10 ` aram.h at mgk dot ro

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=bug-16914-6586-28RDauLb6e@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.org \
    /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).