From: "Michal Suchánek" <msuchanek@suse.de>
To: Luca Boccassi <bluca@debian.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
dwarves@vger.kernel.org, bpf@vger.kernel.org, kernel-team@fb.com,
Michael Petlan <mpetlan@redhat.com>
Subject: Re: [RFT] Testing 1.22
Date: Sat, 17 Jul 2021 18:36:26 +0200 [thread overview]
Message-ID: <20210717163626.GN24916@kitsune.suse.cz> (raw)
In-Reply-To: <b07015ebd7bbadb06a95a5105d9f6b4ed5817b2f.camel@debian.org>
On Sat, Jul 17, 2021 at 04:14:54PM +0100, Luca Boccassi wrote:
> On Sat, 2021-07-17 at 17:10 +0200, Michal Suchánek wrote:
> > Hello,
...
> >
> > So this libbpf comes from the kernel, and there is a separate github
> > repository for libbpf.
> >
> > Should the kernel ship its own copy of the library?
> >
> > Seeing that the one in the kernel is 0.3.0 and the required one for
> > dwarves is 0.4.0 maybe the one in the kernel needs updating if it needs
> > to be shipped there?
> >
> > I wil file a bug to build the libbpf from the git repo instead of the
> > kernel to make the openSUSE libbpf less baroque.
>
> They provide the same ABI, so there should be only one in the same
> distro, the kernel package shouldn't ship its own copy if there's a
> standalone package built from the standalone sources.
> If you are asking why the sources are still present in the upstream
> kernel, I don't know - maybe historical reasons, since that's where it
> came from? But AFAIK the majority of distros don't use that anymore.
FWIW the libbpf from github does not work for me with LTO (GCC 11).
Also there is a problem that LIBDIR is /usr/lib64 on arm64 ppc64(le) and
s390x but the library gets installed into /usr/lib by default. For some
reason x86_64 is the only 64bit arch that works out of the box.
Thanks
Michal
next prev parent reply other threads:[~2021-07-17 16:36 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 15:20 [RFT] Testing 1.22 Arnaldo Carvalho de Melo
2021-05-27 16:54 ` Andrii Nakryiko
2021-05-27 19:04 ` Arnaldo
2021-05-27 19:14 ` Andrii Nakryiko
2021-05-27 19:55 ` Arnaldo
2021-05-27 20:41 ` Andrii Nakryiko
2021-05-27 21:08 ` Jiri Olsa
2021-05-27 21:57 ` Arnaldo
2021-05-28 19:45 ` Arnaldo Carvalho de Melo
2021-05-29 2:36 ` Andrii Nakryiko
2021-06-01 18:31 ` Arnaldo Carvalho de Melo
2021-06-01 18:32 ` Arnaldo Carvalho de Melo
2021-05-30 0:40 ` Andrii Nakryiko
2021-06-01 18:24 ` Arnaldo Carvalho de Melo
2021-06-03 14:57 ` Arnaldo Carvalho de Melo
2021-06-05 2:55 ` Andrii Nakryiko
2021-06-07 13:20 ` Parallelizing vmlinux BTF encoding. was " Arnaldo Carvalho de Melo
2021-06-07 15:42 ` Yonghong Song
2021-06-08 0:53 ` Andrii Nakryiko
2021-06-08 12:59 ` Arnaldo Carvalho de Melo
2021-06-15 19:01 ` Arnaldo Carvalho de Melo
2021-06-15 19:13 ` Andrii Nakryiko
2021-06-15 19:38 ` Arnaldo Carvalho de Melo
2021-06-15 20:05 ` Andrii Nakryiko
2021-06-15 20:25 ` Arnaldo Carvalho de Melo
2021-06-15 21:26 ` Andrii Nakryiko
2021-05-30 21:45 ` Jiri Olsa
2021-06-01 19:07 ` Arnaldo Carvalho de Melo
2021-06-02 10:21 ` Michael Petlan
2021-07-15 21:31 ` Michal Suchánek
2021-07-16 13:25 ` Arnaldo Carvalho de Melo
2021-07-16 13:35 ` Luca Boccassi
2021-07-16 19:08 ` Luca Boccassi
[not found] ` <20210716201248.GL24916@kitsune.suse.cz>
2021-07-17 14:35 ` Luca Boccassi
2021-07-17 15:10 ` Michal Suchánek
2021-07-17 15:14 ` Luca Boccassi
2021-07-17 16:36 ` Michal Suchánek [this message]
2021-07-17 16:39 ` Luca Boccassi
2021-07-19 10:30 ` Michal Suchánek
2021-07-19 10:34 ` Luca Boccassi
2021-07-19 12:10 ` Luca Boccassi
2021-07-19 21:08 ` Arnaldo Carvalho de Melo
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=20210717163626.GN24916@kitsune.suse.cz \
--to=msuchanek@suse.de \
--cc=acme@kernel.org \
--cc=andrii@kernel.org \
--cc=bluca@debian.org \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=jolsa@kernel.org \
--cc=kernel-team@fb.com \
--cc=mpetlan@redhat.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).