From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libbpf: add BR2_PACKAGE_LIBBPF_ARCH_SUPPORTS
Date: Sat, 12 Jun 2021 16:17:14 +0200 [thread overview]
Message-ID: <20210612141714.520748-1-fontaine.fabrice@gmail.com> (raw)
libbpf does not support all architectures, for example ARM is not
supported resulting in the following build failure:
bpf.c:53:4: error: #error __NR_bpf not defined. libbpf does not support your arch.
# error __NR_bpf not defined. libbpf does not support your arch.
^
Fixes:
- http://autobuild.buildroot.org/results/288d54100a2e736195a3a04a9e2e035d02ea5c16
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
---
package/libbpf/Config.in | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/package/libbpf/Config.in b/package/libbpf/Config.in
index c5b24c5eb5..9eadf0254a 100644
--- a/package/libbpf/Config.in
+++ b/package/libbpf/Config.in
@@ -1,5 +1,15 @@
+config BR2_PACKAGE_LIBBPF_ARCH_SUPPORTS
+ bool
+ # see src/bpf.c
+ default y if BR2_arc
+ default y if BR2_aarch64 || BR2_aarch64_be
+ default y if BR2_i386 || BR2_x86_64
+ default y if BR2_sparc || BR2_sparc64
+ default y if BR2_s390x
+
config BR2_PACKAGE_LIBBPF
bool "libbpf"
+ depends on BR2_PACKAGE_LIBBPF_ARCH_SUPPORTS
depends on BR2_USE_WCHAR # elfutils
depends on !BR2_STATIC_LIBS # elfutils
depends on BR2_TOOLCHAIN_HAS_THREADS # elfutils
@@ -15,6 +25,7 @@ config BR2_PACKAGE_LIBBPF
https://github.com/libbpf/libbpf
comment "libbpf needs a uClibc or glibc toolchain w/ wchar, dynamic library, threads"
+ depends on BR2_PACKAGE_LIBBPF_ARCH_SUPPORTS
depends on !BR2_USE_WCHAR || BR2_STATIC_LIBS \
|| !BR2_TOOLCHAIN_HAS_THREADS \
|| !(BR2_TOOLCHAIN_USES_UCLIBC || BR2_TOOLCHAIN_USES_GLIBC)
--
2.30.2
next reply other threads:[~2021-06-12 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-12 14:17 Fabrice Fontaine [this message]
2021-07-13 19:29 ` [Buildroot] [PATCH 1/1] package/libbpf: add BR2_PACKAGE_LIBBPF_ARCH_SUPPORTS Arnout Vandecappelle
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=20210612141714.520748-1-fontaine.fabrice@gmail.com \
--to=fontaine.fabrice@gmail.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.