From: Francis Laniel <flaniel@linux.microsoft.com>
To: buildroot@buildroot.org
Cc: Francis Laniel <flaniel@linux.microsoft.com>,
Romain Naour <romain.naour@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: [Buildroot] [RFC PATCH v1 0/2] Use host-libbpf for host-pahole.
Date: Fri, 22 Apr 2022 19:16:10 +0100 [thread overview]
Message-ID: <20220422181612.51246-1-flaniel@linux.microsoft.com> (raw)
Hi.
Following a failed build involving libbpf, Thomas Pettazzoni suggested me to
remove git submodule from host-pahole to build it the "buildroot way".
So, in this contribution, I first added host recipe to libbpf.
Then, I removed git submobule used by host-pahole to get libbpf to instead use
host-libbpf.
I was able to build and run a qemu image:
Welcome to Buildroot
buildroot login: root
# zcat /proc/config.gz | grep BTF
CONFIG_DEBUG_INFO_BTF=y
CONFIG_PAHOLE_HAS_SPLIT_BTF=y
CONFIG_DEBUG_INFO_BTF_MODULES=y
Nonetheless, I am not really happy with this contribution as I had to add a bad
tweak removing a header file installed by host-libbpf to avoid a kernel build
error:
So, I marked this contribution as RFC to get your opinions about it.
Francis Laniel (2):
package/libbpf: build for host
package/pahole: use commit 73383b3a39af
linux/linux.mk | 11 +++++++++++
package/libbpf/libbpf.mk | 7 +++++++
package/pahole/pahole.hash | 2 +-
package/pahole/pahole.mk | 14 +++++++-------
4 files changed, 26 insertions(+), 8 deletions(-)
Best regards and thank you in advance.
--
2.25.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-04-22 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 18:16 Francis Laniel [this message]
2022-04-22 18:16 ` [Buildroot] [RFC PATCH v1 1/2] package/libbpf: build for host Francis Laniel
2022-04-30 15:46 ` Arnout Vandecappelle
2022-04-22 18:16 ` [Buildroot] [RFC PATCH v1 2/2] package/pahole: use commit 73383b3a39af Francis Laniel
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=20220422181612.51246-1-flaniel@linux.microsoft.com \
--to=flaniel@linux.microsoft.com \
--cc=buildroot@buildroot.org \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.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