unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: John Soo <jsoo1@asu.edu>
Cc: 45633@debbugs.gnu.org
Subject: bug#45633: bcc and bpftrace require kernel headers from system
Date: Sun, 03 Jan 2021 22:40:17 +0100	[thread overview]
Message-ID: <87turxhf7i.fsf@nckx> (raw)
In-Reply-To: <875z4d3m83.fsf@asu.edu>

[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]

John,

This reminds me of <http://issues.guix.gnu.org/45592>.

John Soo 写道:
> Hi Guix,
>
> When I added bcc and bpftrace to guix I didn't think much of 
> which
> version of the kernel headers would be used.  After a few kernel
> updates, it has become clear that the current-system kernel 
> headers need

This should probably be booted-system.

> to match the kernel headers the packages are compiled with.  Can 
> they be
> provided with a variant property?  The ocaml packages that need
> different ocaml versions seem like a nice model on how to do the 
> kernel
> headers.

I know exact kernel headers are needed at toolchain run time, when 
building eBPF programmes.  Are they really needed at toolchain 
build time, too?  That sounds wrong (but there are more things 
fundamentally wrong with eBPF on Linux; ask me to rant about 
CONFIG_IKHEADERS).  Still, could pointing bcc/bpftrace to 
booted-system headers at run time not suffice?

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2021-01-03 21:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-03 18:32 bug#45633: bcc and bpftrace require kernel headers from system John Soo
2021-01-03 21:40 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2021-01-04 18:10   ` John Soo

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87turxhf7i.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=45633@debbugs.gnu.org \
    --cc=jsoo1@asu.edu \
    --cc=me@tobias.gr \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).