From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/23829] Bug introduced in bpf -base.cxx in git master
Date: Mon, 29 Oct 2018 17:54:00 -0000 [thread overview]
Message-ID: <bug-23829-6586-GV6k9AFivU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23829-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23829
Serhei Makarov <me at serhei dot io> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-10-29
CC| |me at serhei dot io
Ever confirmed|0 |1
--- Comment #2 from Serhei Makarov <me at serhei dot io> ---
__BPF_FUNC_MAPPER is included from the Linux kernel's bpf.h header, via a
directive in bpf-internal.h:
extern "C" {
#include <linux/bpf.h>
}
Some of the other errors also seem to relate to symbols not in bpf.h e.g.
BPF_JLT. I will need to work out a good fallback for when bpf.h is unavailable
/ lacks those symbols. Which version of the kernel headers were you compiling
against?
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2018-10-29 17:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 5:38 [Bug bpf/23829] New: " gmoreira at gmail dot com
2018-10-26 5:47 ` [Bug bpf/23829] " gmoreira at gmail dot com
2018-10-29 17:54 ` me at serhei dot io [this message]
2018-10-29 17:54 ` me at serhei dot io
2018-10-31 1:02 ` gmoreira at gmail dot com
2018-10-31 1:03 ` gmoreira at gmail dot com
2018-11-02 20:51 ` me at serhei dot io
2019-03-22 19:09 ` me at serhei dot io
2019-03-27 14:48 ` me at serhei dot io
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-23829-6586-GV6k9AFivU@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).