From: "srinivasa at in dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug testsuite/4500] New: Compilation of buildok/task_test.stp fails on ppc64
Date: Mon, 14 May 2007 09:17:00 -0000 [thread overview]
Message-ID: <20070514101657.4500.srinivasa@in.ibm.com> (raw)
In systemtap-snapshot 20070512, builok/task_test.stp fails with below reason.
==============================================
/tmp/stapoECuDX/stap_cc104d8cc3585fb32de7686d1744bee5_3066.c: In function
'function_task_cpu':
/tmp/stapoECuDX/stap_cc104d8cc3585fb32de7686d1744bee5_3066.c:531: error: 'struct
task_struct' has no member named 'thread_info'
/tmp/stapoECuDX/stap_cc104d8cc3585fb32de7686d1744bee5_3066.c:531: error: 'struct
task_struct' has no member named 'thread_info'
/tmp/stapoECuDX/stap_cc104d8cc3585fb32de7686d1744bee5_3066.c:531: error: 'struct
task_struct' has no member named 'thread_info'
/tmp/stapoECuDX/stap_cc104d8cc3585fb32de7686d1744bee5_3066.c:531: error: 'struct
task_struct' has no member named 'thread_info'
/tmp/stapoECuDX/stap_cc104d8cc3585fb32de7686d1744bee5_3066.c:531: error: 'struct
task_struct' has no member named 'thread_info'
/tmp/stapoECuDX/stap_cc104d8cc3585fb32de7686d1744bee5_3066.c:531: error: 'struct
task_struct' has no member named 'thread_info'
======================================================
--
Summary: Compilation of buildok/task_test.stp fails on ppc64
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: srinivasa at in dot ibm dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=4500
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-05-14 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 9:17 srinivasa at in dot ibm dot com [this message]
2007-05-14 9:51 ` [Bug testsuite/4500] " ananth at in dot ibm dot com
2007-05-14 11:56 ` srinivasa at in dot ibm dot com
2007-07-18 14:29 ` srinivasa at in dot ibm dot com
2007-07-18 17:13 ` fche at redhat dot com
2007-07-19 23:52 ` srinivasa at in dot ibm dot com
2007-09-04 3:24 ` 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=20070514101657.4500.srinivasa@in.ibm.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).