From: Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
To: "Alexis Lothoré" <alexis.lothore@bootlin.com>
Cc: Arnout Vandecappelle <arnout@rnout.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 2/2] packages/linux-tools: perf: enforce PKG_CONFIG_LIBDIR
Date: Tue, 13 Jan 2026 20:45:14 +0100 [thread overview]
Message-ID: <20260113194515.97510-1-arnout@rnout.be> (raw)
In-Reply-To: <20250709-perf_libtraceevent-v2-2-3ea54fbe6b5b@bootlin.com>
In reply of:
> For kernel patched with 440cf77625e3 ("perf: build: Setup
> PKG_CONFIG_LIBDIR for cross compilation"), if neither PKG_CONFIG_LIBDIR,
> PKG_CONFIG_PATH nor PKG_CONFIG_SYSROOT_DIR are provided, the perf
> Makefile while try to set some default value for PKG_CONFIG_LIBDIR,
> which will not point correctly to buildroot staging directory. This
> issue will lead for example to a failure to find libtraceevent even
> if it is correctly enabled and installed in the staging dir, and so it
> will make perf fail to build.
>
> Make sure to call the perf make command with PKG_CONFIG_LIBDIR variable
> set and pointing to buildroot staging area to make sure to properly
> detect perf dependencies.
>
> Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com>
Applied to 2025.02.x and 2025.11.x. Thanks
> ---
> Changes in v2:
> - new patch
> ---
> package/linux-tools/linux-tool-perf.mk.in | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/linux-tools/linux-tool-perf.mk.in b/package/linux-tools/linux-tool-perf.mk.in
> index 1e19ee7f1c4e46d210c079d796f9461f2bfaae08..3238948d7608920d6c236e47fcdce8a31fb67545 100644
> --- a/package/linux-tools/linux-tool-perf.mk.in
> +++ b/package/linux-tools/linux-tool-perf.mk.in
> @@ -23,6 +23,7 @@ PERF_MAKE_FLAGS = \
> JOBS=$(PARALLEL_JOBS) \
> ARCH=$(PERF_ARCH) \
> DESTDIR=$(TARGET_DIR) \
> + PKG_CONFIG_LIBDIR="$(STAGING_DIR)/usr/lib/pkgconfig" \
> prefix=/usr \
> NO_GTK2=1 \
> NO_LIBPERL=1 \
>
> --
> 2.50.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-01-13 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 15:04 [Buildroot] [PATCH v2 0/2] packages/linux-tools: perf: allow building perf with libtraceevent Alexis Lothoré via buildroot
2025-07-09 15:04 ` [Buildroot] [PATCH v2 1/2] package/linux-tools: perf: build with libtraceevent support when it is selected Alexis Lothoré via buildroot
2025-07-21 8:19 ` Luca Ceresoli via buildroot
2025-12-29 17:55 ` Julien Olivain via buildroot
2026-01-13 19:45 ` Arnout Vandecappelle via buildroot
2025-07-09 15:04 ` [Buildroot] [PATCH v2 2/2] packages/linux-tools: perf: enforce PKG_CONFIG_LIBDIR Alexis Lothoré via buildroot
2025-07-21 8:20 ` Luca Ceresoli via buildroot
2026-01-13 19:45 ` Arnout Vandecappelle 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=20260113194515.97510-1-arnout@rnout.be \
--to=buildroot@buildroot.org \
--cc=alexis.lothore@bootlin.com \
--cc=arnout@rnout.be \
/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.