From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Francis Laniel <flaniel@linux.microsoft.com>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-04-14
Date: Tue, 19 Apr 2022 20:43:41 +0200 [thread overview]
Message-ID: <20220419204341.0adf3f55@windsurf> (raw)
In-Reply-To: <12997361.uLZWGnKmhe@pwmachine>
On Tue, 19 Apr 2022 18:41:44 +0100
Francis Laniel <flaniel@linux.microsoft.com> wrote:
> I think upstream code has actually a problem buildroot test infrastructure
> highlighted.
> So, from my understanding, the best solution would be to patch upstream
> libbpf.
> Indeed, I do not think adding a buildroot package will solve this problem.
>
> Were you suggesting than by adding a buildroot package we could add a local
> patch to fix this behavior?
What I meant is that pahole bundles libbpf as a git submodule, but can
also use an external libbpf. In the context of Buildroot, we would very
much prefer to have a separate host-libbpf package, with host-pahole
depending on it (and not using its own copy of libbpf).
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-04-19 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2098999.irdbgypaU6@pwmachine>
2022-04-17 8:42 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-04-14 Thomas Petazzoni via buildroot
2022-04-19 17:41 ` Francis Laniel
2022-04-19 18:43 ` Thomas Petazzoni via buildroot [this message]
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=20220419204341.0adf3f55@windsurf \
--to=buildroot@buildroot.org \
--cc=flaniel@linux.microsoft.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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