Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #65281
| From | Alexei Starovoitov <alexei.starovoitov@gmail.com> |
|---|---|
| Newsgroups | linux.debian.kernel |
| Subject | Re: libbpf-devel rpm uapi headers |
| Date | 2019-10-02 21:10 +0200 |
| Message-ID | <yMSaB-42n-5@gated-at.bofh.it> (permalink) |
| References | <yMRey-3t7-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Oct 02, 2019 at 07:43:31PM +0200, Jiri Olsa wrote: > 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, I think it may break a bunch of people who rely on bcc being a single library. What is the main motiviation to use libbpf as a shared library in libbcc? I think we can have both options. libbpf as git submodule and as shared. In practice git submodule is so much simpler to use and a lot less headaches.
Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
libbpf-devel rpm uapi headers Jiri Olsa <jolsa@redhat.com> - 2019-10-02 20:10 +0200
Re: libbpf-devel rpm uapi headers Alexei Starovoitov <alexei.starovoitov@gmail.com> - 2019-10-02 21:10 +0200
Re: libbpf-devel rpm uapi headers Jiri Olsa <jolsa@redhat.com> - 2019-10-02 22:30 +0200
csiph-web