Lines Matching +full:debian +full:- +full:archive
2 …<source media="(prefers-color-scheme: dark)" srcset="assets/libbpf-logo-sideways-darkbg.png" width…
3 <img src="assets/libbpf-logo-sideways.png" width="40%">
10 [](https://…
19 Libbpf *authoritative source code* is developed as part of [bpf-next Linux source
20 tree](https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next) under
22 libbpf changes should be sent to [BPF mailing list](http://vger.kernel.org/vger-lists.html#bpf),
23 please don't open PRs here unless you are changing Github-specific parts of libbpf
24 (e.g., Github-specific Makefile).
32 Please check out [libbpf-bootstrap](https://github.com/libbpf/libbpf-bootstrap)
33 and [the companion blog post](https://nakryiko.com/posts/libbpf-bootstrap/) for
35 [libbpf-tools](https://github.com/iovisor/bcc/tree/master/libbpf-tools) are also
36 a good source of the real-world libbpf-based tracing tools.
38 See also ["BPF CO-RE reference guide"](https://nakryiko.com/posts/bpf-core-reference-guide/)
39 for the coverage of practical aspects of building BPF CO-RE applications and
40 ["BPF CO-RE"](https://nakryiko.com/posts/bpf-portability-and-co-re/) for
41 general introduction into BPF portability issues and BPF CO-RE origins.
45 subscribe to it [here](http://vger.kernel.org/vger-lists.html#bpf) and search
46 its archive [here](https://lore.kernel.org/bpf/). Please search the archive
59 pkg-config is used by default to find libelf, and the program called can be
62 If using `pkg-config` at build time is not desired, it can be disabled by
88 BPF CO-RE (Compile Once – Run Everywhere)
91 Libbpf supports building BPF CO-RE-enabled applications, which, in contrast to
93 being deployed to target servers and doesn't rely on kernel-devel headers
99 - Fedora 31+
100 - RHEL 8.2+
101 - OpenSUSE Tumbleweed (in the next release, as of 2020-06-04)
102 - Arch Linux (from kernel 5.7.1.arch1-1)
103 - Manjaro (from kernel 5.4 if compiled after 2021-06-18)
104 - Ubuntu 20.10
105 - Debian 11 (amd64/arm64)
107 If your kernel doesn't come with BTF built-in, you'll need to build custom
109 - `pahole` 1.16+ tool (part of `dwarves` package), which performs DWARF to
111 - kernel built with `CONFIG_DEBUG_INFO_BTF=y` option;
112 - you can check if your kernel has BTF built-in by looking for
116 $ ls -la /sys/kernel/btf/vmlinux
117 -r--r--r--. 1 root root 3541561 Jun 2 18:16 /sys/kernel/btf/vmlinux
122 - Fedora 32+
123 - Ubuntu 20.04+
124 - Arch Linux
125 - Ubuntu 20.10 (LLVM 11)
126 - Debian 11 (LLVM 11)
127 - Alpine 3.13+
131 The following resources are useful to understand what BPF CO-RE is and how to
133 - [BPF CO-RE reference guide](https://nakryiko.com/posts/bpf-core-reference-guide/)
134 - [BPF Portability and CO-RE](https://nakryiko.com/posts/bpf-portability-and-co-re/)
135 - [HOWTO: BCC to libbpf conversion](https://nakryiko.com/posts/bcc-to-libbpf-howto-guide/)
136 - [libbpf-tools in BCC repo](https://github.com/iovisor/bcc/tree/master/libbpf-tools)
137 contain lots of real-world tools converted from BCC to BPF CO-RE. Consider
145 - [Fedora](https://src.fedoraproject.org/rpms/libbpf)
146 - [Gentoo](https://packages.gentoo.org/packages/dev-libs/libbpf)
147 - [Debian](https://packages.debian.org/source/sid/libbpf)
148 - [Arch](https://archlinux.org/packages/core/x86_64/libbpf/)
149 - [Ubuntu](https://packages.ubuntu.com/source/jammy/libbpf)
150 - [Alpine](https://pkgs.alpinelinux.org/packages?name=libbpf)
153 - Consistent versioning across distributions.
154 - No ties to any specific kernel, transparent handling of older kernels.
155 Libbpf is designed to be kernel-agnostic and work across multitude of
156 kernel versions. It has built-in mechanisms to gracefully handle older
160 - Continuous integration testing via
162 - Static code analysis via [LGTM](https://lgtm.com/projects/g/libbpf/libbpf)
166 - zlib
167 - libelf
169 [](https:…
172 bpf-next to Github sync
175 All the gory details of syncing can be found in `scripts/sync-kernel.sh`
180 [bpf-next](https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/)'s
186 This work is dual-licensed under BSD 2-clause license and GNU LGPL v2.1 license.
189 `SPDX-License-Identifier: BSD-2-Clause OR LGPL-2.1`