From: "pmuller at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/6967] New: systemtap broken on s390x, compilation error
Date: Mon, 20 Oct 2008 13:53:00 -0000 [thread overview]
Message-ID: <20081020135234.6967.pmuller@redhat.com> (raw)
After this commit:
commit 52333a6929a036ba787593eb42acab81d11d91b1
Author: Jim Keniston <jkenisto@us.ibm.com>
Date: Fri Oct 17 14:43:40 2008 -0700
PR6923: Make on_each_cpu() autoconf test work on old kernels.
Things became severely broken on s390x, with 2.6.18-92.el5 / 2.6.18-118.el5
kernel. (RHEL5.2 kernels). The list of testsuite regressions is too long
here :)
Stap burns down with this error:
# /usr/local/bin/stap ../testsuite/systemtap.base/ctime.stp -vv
SystemTap translator/driver (version 0.7.1/0.137 git branch (no branch), commit
52333a69)
Copyright (C) 2005-2008 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
Session arch: s390x release: 2.6.18-118.el5
Created temporary directory "/tmp/stapMye1Be"
Searched '/usr/local/share/systemtap/tapset/s390x/*.stp', found 1
Searched '/usr/local/share/systemtap/tapset/*.stp', found 43
Pass 1: parsed user script and 44 library script(s) in 460usr/10sys/1220real ms.
Pass 2: analyzed script: 1 probe(s), 2 function(s), 0 embed(s), 0 global(s) in
10usr/0sys/8real ms.
Pass 3: translated to C into "/tmp/stapMye1Be/
stap_3a0a4fb7429a0207fe92ebdef2ddb987_4416.c" in 20usr/200sys/574real ms.
Running make -C "/lib/modules/2.6.18-118.el5/build" M="/tmp/stapMye1Be" modules
>/dev/null
In file included from /usr/local/share/systemtap/runtime/transport/
transport.c:20,
from /usr/local/share/systemtap/runtime/print.c:17,
from /usr/local/share/systemtap/runtime/runtime.h:84,
from /tmp/stapMye1Be/
stap_3a0a4fb7429a0207fe92ebdef2ddb987_4416.c:41:
/usr/local/share/systemtap/runtime/time.c: In function \u2018_stp_init_time
\u2019:
/usr/local/share/systemtap/runtime/time.c:243: error: too few arguments to
function \u2018on_each_cpu\u2019
make[1]: *** [/tmp/stapMye1Be/stap_3a0a4fb7429a0207fe92ebdef2ddb987_4416.o]
Error 1
make: *** [_module_/tmp/stapMye1Be] Error 2
Pass 4: compiled C into "stap_3a0a4fb7429a0207fe92ebdef2ddb987_4416.ko" in
1500usr/290sys/3739real ms.
Pass 4: compilation failed. Try again with more '-v' (verbose) options.
Running rm -rf /tmp/stapMye1Be
--
Summary: systemtap broken on s390x, compilation error
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: pmuller at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=6967
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2008-10-20 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 13:53 pmuller at redhat dot com [this message]
2008-10-20 18:24 ` [Bug runtime/6967] " jkenisto at us dot ibm dot com
2008-10-20 18:54 ` jkenisto at us dot ibm dot com
2008-10-21 12:56 ` pmuller at redhat dot com
2008-10-22 0:24 ` jkenisto at us dot ibm dot com
2008-10-22 0:30 ` jkenisto at us dot ibm dot com
2008-10-22 10:08 ` pmuller at redhat dot com
2008-10-24 19:08 ` jkenisto at us dot ibm dot com
2008-10-29 0:54 ` fche at redhat dot com
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=20081020135234.6967.pmuller@redhat.com \
--to=sourceware-bugzilla@sourceware.org \
--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).