public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/16914] probe syscall.* fails with compilation error
Date: Thu, 12 Feb 2015 19:07:00 -0000	[thread overview]
Message-ID: <bug-16914-6586-zLfLqNrbmj@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 #13 from David Smith <dsmith at redhat dot com> ---
(In reply to Aram Hăvărneanu from comment #12)
> Yes, of course it is not SystemTap's fault that the kernel is broken. I
> can't see https://bugzilla.redhat.com/show_bug.cgi?id=1094366 though (access
> denied), so I can't patch my upstream kernel locally.

Sorry, I didn't realize that was an internal bug. I'm not sure why it is. I'll
see if it can be made public. Long story short, the bug adds the following text
to the spec file:

+%ifarch aarch64
+ cp -a --parents arch/arm/include/asm/xen
$RPM_BUILD_ROOT/lib/modules/$KernelVer/build/
+%endif

> In short, it's not SystemTap's fault, but you can't run SystemTap on arm64
> today (except, perhaps, on RedHat kernel; who knows, I can't read that bug).
> So I posted so other people who hit this know what to expect.

Hopefully that above command should do the trick for you (after making it fit
your environment).

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

  parent reply	other threads:[~2015-02-12 19:07 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
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 [this message]
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-zLfLqNrbmj@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).