From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Tobias Waldekranz <tobias@waldekranz.com>
Cc: Romain Naour <romain.naour@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/4] package/libbpf: remove architecture restrictions
Date: Wed, 26 Oct 2022 22:10:28 +0200 [thread overview]
Message-ID: <20221026221028.7e11ea80@windsurf> (raw)
In-Reply-To: <20221020141412.346992-3-tobias@waldekranz.com>
Hello Tobias,
On Thu, 20 Oct 2022 16:14:10 +0200
Tobias Waldekranz <tobias@waldekranz.com> wrote:
> Since 3145adfb69ba, libbpf depends on Linux headers >= 4.13. This
> requirement renders the explicit list of supported architectures,
> previously added in f693354c30bd overly restrictive, as the syscall
> number for bpf(2) has been defined since Linux 3.18.
>
> f693354c30bd was introduced to fix a build issue where a toolchain
> using very old kernel headers (3.13) failed to build libbpf for ARM.
>
> Signed-off-by: Tobias Waldekranz <tobias@waldekranz.com>
> ---
> package/libbpf/Config.in | 11 -----------
> 1 file changed, 11 deletions(-)
It is not easy to check if the bpf syscall was indeed wired up in all
architectures we support, but let's assume it's the case as of 4.13 :-)
I have applied, with a slightly improved commit log:
package/libbpf: remove architecture restrictions
Since Buildroot commit 3145adfb69ba ("package/libbpf: needs headers >=
4.13"), libbpf depends on Linux headers >= 4.13. This requirement
renders the explicit list of supported architectures, previously added
in f693354c30bd overly restrictive, as the syscall number for bpf(2)
has been defined since Linux 3.18.
Commit f693354c30bd ("package/libbpf: add
BR2_PACKAGE_LIBBPF_ARCH_SUPPORTS") was introduced to fix a build issue
where a toolchain using very old kernel headers (3.13) failed to build
libbpf for ARM, but these architecture dependencies are no longer
needed due to the bump on the kernel headers version requirement.
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-10-26 20:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 14:14 [Buildroot] [PATCH 0/4] package/kmemd: new package Tobias Waldekranz
2022-10-20 14:14 ` [Buildroot] [PATCH 1/4] package/libbpf: fix cross compilation for 32-bit targets Tobias Waldekranz
2022-10-26 20:00 ` Thomas Petazzoni via buildroot
2022-10-26 20:59 ` Tobias Waldekranz
2022-10-26 21:28 ` Thomas Petazzoni via buildroot
2022-10-27 6:46 ` Thomas Petazzoni via buildroot
2022-10-20 14:14 ` [Buildroot] [PATCH 2/4] package/libbpf: remove architecture restrictions Tobias Waldekranz
2022-10-26 20:10 ` Thomas Petazzoni via buildroot [this message]
2022-10-20 14:14 ` [Buildroot] [PATCH 3/4] package/libbpf: extract dependencies to separate kconfig symbol Tobias Waldekranz
2022-10-26 20:15 ` Thomas Petazzoni via buildroot
2022-10-26 21:14 ` Tobias Waldekranz
2022-10-26 22:19 ` Thomas Petazzoni via buildroot
2022-10-20 14:14 ` [Buildroot] [PATCH 4/4] package/kmemd: new package Tobias Waldekranz
2022-10-27 6:49 ` Thomas Petazzoni via buildroot
2022-10-27 20:27 ` Tobias Waldekranz
2022-10-27 21:32 ` Thomas Petazzoni via buildroot
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=20221026221028.7e11ea80@windsurf \
--to=buildroot@buildroot.org \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=tobias@waldekranz.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