unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: John Soo <jsoo1@asu.edu>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 45633@debbugs.gnu.org
Subject: bug#45633: bcc and bpftrace require kernel headers from system
Date: Mon, 04 Jan 2021 10:10:10 -0800	[thread overview]
Message-ID: <8735zg375p.fsf@asu.edu> (raw)
In-Reply-To: <87turxhf7i.fsf@nckx> (Tobias Geerinckx-Rice's message of "Sun, 03 Jan 2021 22:40:17 +0100")

Hi Tobias,

Tobias Geerinckx-Rice <me@tobias.gr> writes:

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

Hm, maybe. How does it remind you of zfs? It seems like zfs needs the
libraries from util-linux, right? bcc and bpftrace need the kernel
headers. The following should illustrate there is nothing to load
dynamically, right?

find $(guix build linux-libre-headers) -name '*.\.so*'

> This should probably be booted-system.

Yes, definitely, thanks. s/current-system/booted-system/

> I know exact kernel headers are needed at toolchain run time, when
> building eBPF programmes.  Are they really needed at toolchain 
> build time, too?

I am not sure what the headers are used for but they are indeed the .h
files (tree $(guix build linux-libre-headers)).  I would assume they are
used by the gcc-toolchain when compiling the package as #includes.

What do you think?

- John




      reply	other threads:[~2021-01-04 18:15 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
2021-01-04 18:10   ` John Soo [this message]

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=8735zg375p.fsf@asu.edu \
    --to=jsoo1@asu.edu \
    --cc=45633@debbugs.gnu.org \
    --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).