From: Jiri Olsa <jolsa@redhat.com>
To: Julia Kartseva <hex@fb.com>, Yonghong Song <yhs@fb.com>
Cc: "debian-kernel@lists.debian.org" <debian-kernel@lists.debian.org>,
"md@linux.it" <md@linux.it>, "Alexei Starovoitov" <ast@fb.com>,
"Andrii Nakryiko" <andrii.nakryiko@gmail.com>,
"labbott@redhat.com" <labbott@redhat.com>,
"acme@kernel.org" <acme@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Andrey Ignatov" <rdna@fb.com>,
"jolsa@kernel.org" <jolsa@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Jesper Dangaard Brouer" <brouer@redhat.com>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
iovisor-dev@lists.iovisor.org
Subject: libbpf-devel rpm uapi headers
Date: Wed, 2 Oct 2019 19:43:31 +0200 [thread overview]
Message-ID: <20191002174331.GA13941@krava> (raw)
hi,
we'd like to have bcc linked with libbpf instead of the
github submodule, initial change is discussed in here:
https://github.com/iovisor/bcc/pull/2535
In order to do that, we need to have access to uapi headers
compatible with libbpf rpm, bcc is attaching and using them
during compilation.
I added them in the fedora spec below (not submitted yet),
so libbpf would carry those headers.
Thoughts? thanks,
jirka
---
Subject: [PATCH] Package uapi headers under /usr/include/bpf/uapi/linux
The full list of files for libbpf-devel is now:
/usr/include/bpf
/usr/include/bpf/bpf.h
/usr/include/bpf/btf.h
/usr/include/bpf/libbpf.h
/usr/include/bpf/libbpf_util.h
/usr/include/bpf/uapi
/usr/include/bpf/uapi/linux
/usr/include/bpf/uapi/linux/compiler.h
/usr/include/bpf/uapi/linux/err.h
/usr/include/bpf/uapi/linux/filter.h
/usr/include/bpf/uapi/linux/kernel.h
/usr/include/bpf/uapi/linux/list.h
/usr/include/bpf/uapi/linux/overflow.h
/usr/include/bpf/uapi/linux/ring_buffer.h
/usr/include/bpf/uapi/linux/types.h
/usr/include/bpf/xsk.h
/usr/lib64/libbpf.so
/usr/lib64/pkgconfig/libbpf.pc
---
libbpf.spec | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/libbpf.spec b/libbpf.spec
index 5d0f29718cac..681800c7f93e 100644
--- a/libbpf.spec
+++ b/libbpf.spec
@@ -4,7 +4,7 @@
Name: %{githubname}
Version: %{githubver}
-Release: 2%{?dist}
+Release: 3%{?dist}
Summary: Libbpf library
License: LGPLv2 or BSD
@@ -48,6 +48,8 @@ developing applications that use %{name}
%install
%make_install -C ./src %{make_flags}
+install -d -m 755 %{buildroot}/usr/include/bpf/uapi/linux
+cp include/linux/* %{buildroot}/usr/include/bpf/uapi/linux
%files
%{_libdir}/libbpf.so.%{version}
@@ -62,6 +64,9 @@ developing applications that use %{name}
%{_libdir}/libbpf.a
%changelog
+* Wed Oct 02 2019 Jiri Olsa <jolsa@redhat.com> - 0.0.3-3
+- Add uapi headers
+
* Wed Sep 25 2019 Jiri Olsa <jolsa@redhat.com> - 0.0.3-2
- Fix libelf linking (BZ#1755317)
--
2.21.0
next reply other threads:[~2019-10-02 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 17:43 Jiri Olsa [this message]
2019-10-02 18:43 ` libbpf-devel rpm uapi headers Alexei Starovoitov
2019-10-02 20:08 ` Jiri Olsa
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=20191002174331.GA13941@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@fb.com \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=debian-kernel@lists.debian.org \
--cc=hex@fb.com \
--cc=iovisor-dev@lists.iovisor.org \
--cc=jolsa@kernel.org \
--cc=labbott@redhat.com \
--cc=md@linux.it \
--cc=netdev@vger.kernel.org \
--cc=rdna@fb.com \
--cc=toke@redhat.com \
--cc=yhs@fb.com \
/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 NNTP newsgroup(s).