From: Mathieu Othacehe <othacehe@gnu.org>
To: John Soo <jsoo1@asu.edu>
Cc: 42227@debbugs.gnu.org
Subject: [bug#42227] BPF in linux-libre
Date: Thu, 30 Jul 2020 20:48:55 +0200 [thread overview]
Message-ID: <87d04cvnxk.fsf@gnu.org> (raw)
In-Reply-To: <87d0587p1o.fsf@gnu.org>
Hey John,
Thanks for your patience!
> I wrapped the PYTHONPATH around the various provided python tools.
> I also found a spare path that required patching.
> I am not sure this fixes every tool but I did get a few to work now.
Yes, I tested some of them, looks fine :).
> I also added debugfs as a requirement for a bpf system. To use it
> %bpf-file-systems can be used in place of %base-file-systems in the
> operating system definition.
Actually, I wonder if we could mount debugfs by default, by adding it to
%base-file-systems. Any objections?
In the meantime I pushed the bcc patch with a few edits. Regarding
bpftrace, I'd like to avoid the "-DHAVE_BFD_DISASM=OFF" patching, I
found this ticket which seems related:
https://github.com/iovisor/bpftrace/issues/1106, but didn't make any
significant progress yet.
Thanks,
Mathieu
next prev parent reply other threads:[~2020-07-30 18:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 3:21 BPF in linux-libre John Soo
2020-06-14 9:23 ` Mathieu Othacehe
2020-06-14 15:11 ` John Soo
2020-06-17 10:16 ` Mathieu Othacehe
2020-06-17 13:42 ` John Soo
2020-06-21 15:32 ` John Soo
2020-06-26 10:50 ` Mathieu Othacehe
2020-06-28 20:24 ` John Soo
2020-07-01 5:40 ` John Soo
2020-07-03 16:01 ` John Soo
2020-07-05 8:18 ` Mathieu Othacehe
2020-07-05 8:20 ` Mathieu Othacehe
2020-07-06 0:44 ` John Soo
2020-07-06 13:26 ` [bug#42227] " Mathieu Othacehe
2020-07-11 16:28 ` John Soo
2020-07-30 18:48 ` Mathieu Othacehe [this message]
2020-07-31 2:20 ` John Soo
2020-07-31 11:04 ` bug#42227: " Mathieu Othacehe
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=87d04cvnxk.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=42227@debbugs.gnu.org \
--cc=jsoo1@asu.edu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.