All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexis Lothoré via buildroot" <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Luca Ceresoli" <luca.ceresoli@bootlin.com>,
	"Olivier Benjamin" <olivier.benjamin@bootlin.com>,
	"Alexis Lothoré" <alexis.lothore@bootlin.com>
Subject: [Buildroot] [PATCH v2 0/2] packages/linux-tools: perf: allow building perf with libtraceevent
Date: Wed, 09 Jul 2025 17:04:13 +0200	[thread overview]
Message-ID: <20250709-perf_libtraceevent-v2-0-3ea54fbe6b5b@bootlin.com> (raw)

Hello,
this series is the v2 aiming to allow building perf with libtraceevent
support, in order to be able for example to manipulate and record
uprobes with perf.

This new revision gets a new commit enforcing PKG_CONFIG_LIBDIR for the
perf makefile. I am not sure how I did not get the corresponding error
the first time (maybe it needed some full rebuild to trigger), but I now
see that I fail to build perf with multiple stable kernels if I do not
enforce this variable (if it is not defined, the perf makefile will set
it to a value that is wrong in a buildroot build, see [1]). I found a
similar thread and attempt (see [2]), this series proposes to implement
the second option mentioned in there.

Also, as mentioned in the previous revision, perf may fail to build on
some older kernels because the patch correctly setting pkg-config binary
name has not been backported. I have identified that only 6.6 needed it
(as perf builds start to fail from 6.3, and are fixed in 6.11). The
corresponding stable backport request as been sent (see [3])

@Luca: since all stable kernels should get the relevant fix and then
allow to build perf with libtraceevent support, I eventually chose _not_
to mention any issue in the Kconfig.

[1] https://elixir.bootlin.com/linux/v6.12.36/source/tools/perf/Makefile.perf#L211
[2] https://lore.kernel.org/buildroot/aBk4au4rQpZJMrTQ@vamoirid-laptop/
[3] https://lore.kernel.org/stable/2025070955-discover-tree-644c@gregkh/T/#m394f2c9392da7cfd3ca130af6a7ec8ff6ee4b6bf

To: buildroot@buildroot.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: Olivier Benjamin <olivier.benjamin@bootlin.com>

Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com>
---
Changes in v2:
- enforce PKG_CONFIG_LIBDIR
- Link to v1: https://lore.kernel.org/r/20250625-perf_libtraceevent-v1-1-0bf7620bc6c9@bootlin.com

---
Alexis Lothoré (2):
      package/linux-tools: perf: build with libtraceevent support when it is selected
      packages/linux-tools: perf: enforce PKG_CONFIG_LIBDIR

 package/linux-tools/linux-tool-perf.mk.in | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)
---
base-commit: f28f34e200bbadf0aea32110c72f7199e65fb0b9
change-id: 20250625-perf_libtraceevent-17e46ee28f90

Best regards,
-- 
Alexis Lothoré, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2025-07-09 15:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09 15:04 Alexis Lothoré via buildroot [this message]
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

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=20250709-perf_libtraceevent-v2-0-3ea54fbe6b5b@bootlin.com \
    --to=buildroot@buildroot.org \
    --cc=alexis.lothore@bootlin.com \
    --cc=luca.ceresoli@bootlin.com \
    --cc=olivier.benjamin@bootlin.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 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.