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 17:34:00 -0000 [thread overview]
Message-ID: <bug-16914-6586-i1ipMHGQ1b@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 #11 from David Smith <dsmith at redhat dot com> ---
(In reply to Aram Hăvărneanu from comment #10)
> I am having the same problem as the one describe in comment 7.
>
> In file included from ./arch/arm64/include/asm/dma-mapping.h:27:0,
> from include/linux/dma-mapping.h:82,
> from include/linux/skbuff.h:34,
> from include/linux/netlink.h:6,
> from
> /tmp/stap85zy5C/stap_6c1847e871322a4ef474645ee4b86ee9_606063_src.c:184:
> ./arch/arm64/include/asm/xen/hypervisor.h:1:50: fatal error:
> ../../arm/include/asm/xen/hypervisor.h: No such file or directory
> #include <../../arm/include/asm/xen/hypervisor.h>
> ^
> compilation terminated.
>
> I am running the upstream 3.19.0 kernel.
As mentioned in comment #8 this is a kernel problem, not a systemtap problem.
This is rhbz1094366 <https://bugzilla.redhat.com/show_bug.cgi?id=1094366>. It
was fixed at one point, perhaps it has gotten broken again.
It isn't systemtap's fault that when you include a kernel header, one of the
other kernel headers it includes is a file that doesn't exist.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2015-02-12 17:34 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 [this message]
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-i1ipMHGQ1b@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).