From: "gmoreira at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/23829] New: Bug introduced in bpf -base.cxx in git master
Date: Fri, 26 Oct 2018 05:38:00 -0000 [thread overview]
Message-ID: <bug-23829-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=23829
Bug ID: 23829
Summary: Bug introduced in bpf -base.cxx in git master
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bpf
Assignee: systemtap at sourceware dot org
Reporter: gmoreira at gmail dot com
Target Milestone: ---
Created attachment 11366
--> https://sourceware.org/bugzilla/attachment.cgi?id=11366&action=edit
Patch for bpf-base.cxx
Compiling SystemTap from git master:
...
bpf-base.cxx: In function ‘void bpf::init_bpf_helper_tables()’:
bpf-base.cxx:148:21: error: ‘__BPF_SET_FUNC_NAME’ was not declared in this
scope
__BPF_FUNC_MAPPER(__BPF_SET_FUNC_NAME)
^~~~~~~~~~~~~~~~~~~
bpf-base.cxx:148:40: error: ‘__BPF_FUNC_MAPPER’ was not declared in this scope
__BPF_FUNC_MAPPER(__BPF_SET_FUNC_NAME)
^
Makefile:1669: recipe for target 'stap-bpf-base.o' failed
The bug was introduced here:
https://sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commitdiff;h=c009fe88de8a91b11a19e36c332bd096cb72b8b0
Patch attached.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2018-10-26 5:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 5:38 gmoreira at gmail dot com [this message]
2018-10-26 5:47 ` [Bug bpf/23829] " gmoreira at gmail dot com
2018-10-29 17:54 ` me at serhei dot io
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@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).